Associate Product Engineer

Docyt (pronounced "docket") builds an AI-native ERP for hotels, restaurants, retail, and franchises. One platform runs accounting, payments, and business intelligence on one ledger. Bookkeeping happens every day, so month-end becomes a review.

Docyt has processed more than $1.3 billion in invoice volume and connects with 30+ POS and PMS systems. The platform is SOC 2 Type 2 certified.

Docyt is venture funded and headquartered in Mountain View, California. This role is in our Noida Sector 62 office.

You take a piece of work all the way: understand the customer's problem, find the root cause, build the fix, prove it works, ship it, and confirm it is fixed in production. This is not a ticket-in, pull-request-out job. The engineer who does this well here investigates before coding, tests their own work on our QA environment, records a short Loom walkthrough so product can accept without a meeting, and stays with the change through staging and deploy until the customer's issue is closed. That is the bar.

Read the support escalation, reproduce it on QA, and trace the root cause in code and in production data. Say clearly whether it is a product defect, a data gap, or working as designed, and bring the evidence.

In Java (Spring Boot) or Ruby on Rails, with tests. A React change when the fix needs one.

Open the pull request, answer review comments, keep CI green.

The main user flow plus the edge cases from the ticket. Screenshots and the resulting database state go on the ticket.

Before and after, in under five minutes. Product accepts from the recording.

Take the change through staging to production, watch the deploy, verify it in production, and update the original support ticket.

Customer escalations and product features across accounts payable and bill pay, month-end close, AI transaction categorization, financial reporting and ledger migration. Some weeks it is a two-line fix with a long investigation behind it. Some weeks it is a new feature from a product spec to a working screen.

We move fast, and you will ship from your first week. A senior engineer reviews your work and helps you learn the codebase. Within your first month, you take a customer issue from start to finish.

• 1 to 3 years of software engineering, or a new graduate who has shipped at least one project.
• Java and Ruby on Rails. Strong in at least one, with clear evidence you can pick up the other quickly. You will work in both.
• SQL you can use to prove a point. You can read production data to confirm or reject a theory before you write code.
• Root cause before fix. You are uncomfortable patching a symptom.
• You write clearly. Tickets, pull request descriptions, Loom narration. People should be able to follow your work without a call.
• Genuine appetite for AI tooling. You have already used Claude Code, Cursor, Copilot or similar seriously, and you want to get much better at it.
• Intent and ownership. You want to be the person a delivery depends on, and you follow through.
• This role requires some overlap with US time zones.

• React and TypeScript in a production codebase.
• Kubernetes, CI pipelines, or a deploy you have managed yourself.
• Basic accounting literacy: chart of accounts, journal entries, bank reconciliation.
• Experience on a product team that talks to customers directly.

When you apply, include a link to a project you shipped. A short Loom walkthrough of it is a plus.