Full Stack Engineer

About the job

You will join our product engineering team on a live consumer app for a North American client. The stack is Node and PostgreSQL on the backend, React Native on mobile, a managed cloud platform for deployments, payments, the web tooling around it, and the AI agents and LLM-powered features now coming into the product. Our clients are in North America and our engineering team is in Gurugram.

You are the backend and agents owner on the team. You own delivery of your workstreams end to end, API through to the screen, and ship to production. The first agents on the roadmap are yours to build. A DawerOne senior lead holds architecture, priorities, and the critical engineering decisions, including mobile architecture. A second developer works alongside you on the React Native surface, a test automation engineer covers regression, payments, and notifications, and the client's product owner and QA lead are part of the day-to-day team.

About half your time goes to a second product in the same client portfolio: a Python and Flask backend on AWS with an AI layer, under the same senior lead. You do not need deep Flask or AWS expertise, but you need to be comfortable reading and changing that codebase from the start.

This is a contract-to-hire role: a full-time, six-month contract with DawerOne, converting to a permanent role on mutual fit. For a strong candidate with clear long-term alignment, we are open to full time from day one. It is hybrid: you work from home most of the month and from our Indore or Gurugram office 2–4 days a month. Indore and Gurugram are preferred, but we will consider strong candidates elsewhere in India within travelling distance of either office. Compensation is benchmarked to seniority and we share a number in the first conversation. The top of our range goes to someone who has shipped a production agent and can show it.

Responsibilities

First 30 days

• Ship a first feature end to end, API through to the screen, within the first sprint.
• Get the automated iOS and Android build and release pipeline working.
• Fix the highest-impact production issues: payments, media handling, and performance across the API and database.
• Scope the first agent with the senior lead and the product owner: knowledge base, guardrails, cost model, and how it is evaluated.

Backend and payments

• Build and maintain the Node and PostgreSQL backend and APIs, including schema design and migrations.
• Own the payment flows: checkout, fees, onboarding, and payouts.
• Integrate third-party services: push notifications, media storage, and partner APIs.
• Build web tooling where the product needs it: admin portals and operational dashboards.

AI agents

• Build and deploy AI agents and LLM-powered features: agentic workflows against the backend, media analysis, and assisted content flows, using LLM APIs, tool use, and MCP.
• Run them properly in production: hosting, monitoring, cost control, and evals that tell you whether the agent is actually good.

Features and mobile

• Deliver new features end to end: scoping with the product owner, API design with the senior lead, the mobile build, and the release.
• Ship React Native features and bug fixes alongside the mobile developer, to patterns set by the senior lead.

Builds, infrastructure, and operations

• Own builds, release management, and production deployments on managed platforms such as Railway, Render, or AWS, with CI/CD for mobile and services.
• Run the operations: environments and secrets, monitoring, alerting and logging, backups and restore, and infrastructure cost, with infrastructure as code where it pays for itself.
• Debug production issues across backend, database, deployments, payments, and mobile.
• Do performance work with measurements before and after.

Quality and delivery

• Support QA with the automation engineer and the client's QA lead: regression, release validation, and bug fixing.
• Keep Jira current: blockers surfaced early, status up to date, and clear written updates.
• Build with AI coding agents as a matter of course. That is how we work.

Minimum qualifications

What matters most

For us, these matter most.

• You have built and deployed at least one LLM-powered feature or agent to production: prompt and tool design, structured outputs, handling failures, hosting and monitoring, controlling cost, and measuring quality. You can talk honestly about what did not work.
• Daily, fluent use of AI coding agents such as Claude Code, MCP servers, or similar. This is a hard requirement. You are productive with them from day one, with no ramp-up period.
• You can debug a production issue independently across layers before escalating.

Experience

• 4 to 6 years building software, with strong backend experience: Node with Express or NestJS, REST API design, and PostgreSQL schema design and migrations.
• Working Python and comfort reading and changing a Flask codebase, plus basic AWS familiarity: EC2 or ECS, RDS, S3, and IAM. Deep Flask or AWS expertise is not required.
• Production React Native experience: shipped features and fixed bugs in a live app on iOS and Android, and able to work to an architecture someone else has set.
• Hands-on with builds, CI/CD, and deployments: GitHub Actions or similar for services, and you have owned environments, secrets, monitoring and alerting, and backups for a production service. Fastlane or EAS for mobile is a plus.

Ways of working

• You take ownership of outcomes, ask the right questions early, and keep delivery moving without follow-up.
• Clear written English and Jira discipline. You work directly with a North American product owner and QA lead.
• Able to work roughly 11 AM to 9 PM IST consistently, Monday to Friday, and flexible if the window needs to move. This is a shift, not an occasional late call.
• Able to be in the Indore or Gurugram office 2–4 days a month.

Preferred qualifications

• Deeper AWS operations, Terraform or another infrastructure-as-code tool, Docker in production, or Flask at scale.
• Stripe or another payment provider in production.
• Consumer commerce or payments-heavy products.
• Store releases, deep links, and push providers such as OneSignal or Firebase.
• Image or media processing flows.
• Experience working in an inherited codebase while still shipping features.

Engagement details

• Engagement: contract-to-hire. A six-month, full-time contract with DawerOne, converting to a permanent role on mutual fit. For a strong candidate with clear long-term alignment, we are open to full time from day one.
• Time commitment: full time, split roughly half and half between the primary consumer app (Node, PostgreSQL, React Native) and backend work on a second product in the same client portfolio (Python, Flask, AWS).
• Exclusivity: this is a full-time, exclusive engagement. You cannot hold another job or contract alongside it.
• Location: hybrid, with 2–4 days a month in our Indore or Gurugram office. Indore and Gurugram preferred; strong candidates elsewhere in India are considered if they are within travelling distance of either office and can travel for office days.
• Working hours: roughly 11 AM to 9 PM IST, Monday to Friday, for daily overlap with the client's North American morning. The window may shift if the engagement demands it.
• Start: immediate joiners preferred. We do not buy out notice periods.
• Reports to: the DawerOne senior lead on the engagement.
• Process: a 30-minute screen with the hiring manager, a technical deep dive of 60 minutes or more, a 60-minute live assessment spanning a Node API, the React Native screen in front of it, and a small agentic workflow using your own AI tooling, and a 30-minute final conversation. The technical and live rounds may be combined. You hear back within two working days of applying, and we make an offer within a week of the live assessment for the right candidate.

Who should apply

Someone who has shipped a backend, a mobile feature, and an agent on products that mattered, and wants to own all three on one team with a senior lead who engages with the hard decisions rather than handing over a ticket list.

If you have not yet put an LLM-powered feature in front of real users, or you want to write application code and hand the deployments to someone else, this is probably not the right role yet.