We are a recruiting firm hiring a Product Engineer for one of our clients: a funded startup moving fast, with a small team and zero bureaucracy. Company details will be shared with shortlisted candidates.

About the roleWhether your last title was Product Engineer, Full Stack Engineer, Software Engineer, or Founding Engineer, the job here is the same: you own outcomes, not a narrow technical lane. You will write production-grade code across backend and frontend, work across the broader ecosystem of modern infrastructure and SaaS tools, and move fluidly between them. The current stack includes Python, TypeScript, React, Postgres, Supabase, AWS, Vercel, Lovable, and a range of external REST APIs.

You do not need deep expertise in every tool. What you need is the ability to read documentation, ask the right questions early, and execute quickly with minimal hand-holding. This is a fast-paced startup: iteration speed, clarity, and adaptability matter as much as raw technical skill.

What you'll do

- Work across backend, frontend, API integrations, and data cleaning pipelines
- Consume and implement third-party APIs and SDKs from documentation alone
- Work with up-to-date cloud infrastructure: AWS, containers, Postgres, CI/CD
- Pick up new tools quickly as the stack evolves (Lovable, Vercel, Supabase, and whatever comes next)
- Scope your own tasks accurately, ask questions before committing to an assumption, and deliver on time
- Iterate quickly and pragmatically, no over-engineering, no technical debt left for someone else to clean up

Tech stack
- Python, JavaScript, TypeScript, React
- Postgres, Supabase
- AWS, Docker/containers, CI/CD
- Vercel, Lovable, external REST APIs

Who this is for




- A strong generalist engineer who thinks about product outcomes, not just code across the stack
- Someone who figures things out from documentation, or asks sharp, targeted questions fast when stuck
- Someone who communicates early and often: you flag blockers and check assumptions rather than disappearing until "done"
- Pragmatic by default: you iterate quickly without over-engineering, and without leaving technical debt behind
- Self-directed: you scope ambiguous problems and run with them, no PM-level specs or step-by-step instructions needed

Working hoursThis is a remote role. You do not need full overlap with US hours, but blockers must be resolved within the 9am to 9pm Pacific Time window, not the next day. Deadlines are honored in PT. If a full-day delay due to timezones is how you currently operate, this role is not a fit.

Who this is not forBeing direct here saves everyone time. This will not work if:

- Your style is exploratory "just trying things" coding that leaves messy repos and unclear logic for others to clean up
- You need rigid specs, detailed design docs, or continuous supervision to make progress
- You go quiet for days and surface only when work is "done," having built on unchecked assumptions
- You are resistant to unfamiliar tools: if there is documentation for a standard API, SDK, or SaaS product, you are expected to figure it out

What's on offer
- A high-ownership product engineering seat at a funded startup, working directly with the founding team
- Real breadth: backend, frontend, infrastructure, integrations, and data, not a narrow lane
- Fast shipping cycles with visible impact
- Competitive compensation

📌 Product Engineer (India)
🏢 Magma Holding
📍 India