SDE-1 (Full Stack Engineer)

Experience Level: 1–3 years

Core Focus: Full-stack feature development across NodeJS and React, with strong fundamentals

Tech Stack: Node.js, TypeScript, MySQL, React, TailwindCSS

Bonus: Docker, Firebase, Redis, TanStack Query

Context: Build features across the backend and frontend of a fast-moving Saleshandy product. You'll ship real work early, pick up system design hands-on, and grow fast. We build with AI tools like Claude Code and Cursor every day.

Don't tick every box? Apply anyway. We care more about curiosity and strong fundamentals than a perfect checklist.
 

What's the Role About

Build backend services in Node.js, model data in MySQL, and craft clean React UIs with TailwindCSS. You'll learn how high-throughput systems work, write code the team can build on, and own more as you grow. Fundamentals and curiosity matter most.
 

Why Join Us

1. Purpose: Your features ship to thousands of users from day one.

2. Growth: Learn system design and full-stack craft by building real things, alongside senior engineers.

3. Motivation: If you want to build real products and grow into a senior engineer by doing, this is it.
 

Your Main Goals
 

1. Ship Your First Features (within 30–45 days)

 Learn the codebase and ship your first full-stack features with guidance.

 Outcome: First features live in production.

2. Build Independently (within 60 days)

 Deliver features end-to-end with less hand-holding.

 Outcome: Features shipped on your own, with good quality.

3. Strengthen Reliability (within 60–90 days)

 Handle errors and edge cases, and lift code quality through testing.

 Outcome: A measurably more reliable system.

4. Own a Component (within 90–120 days)

 Take ownership of a feature area and join design discussions.

 Outcome: Clear ownership of one component.
 

Culture Fit – Are You One of Us

1. You're hungry to learn and grow fast

2. You care about fundamentals and clean code

3. You take feedback well

4. You move fast and ask questions

5. You use AI tools as a multiplier, not a crutch

Important: Please read the instructions thoroughly before answering the pre-screening questions.
Answer from real, specific experience. Where we ask for an exact error message, log line, or prompt, paste the real text don't paraphrase or clean it up. Short and specific beats long and polished. Always include the detail of the feature you were working on (we DO NOT want to hear generic answers like In one of my React projects, I worked on improving a component system for a dashboard).