Job Responsibilities

- Design an API, not only implement one.

- Reason about indexes, query plans, transactions, migrations on live tables.

- Handle vendor and third-party integrations, done well: authentication, retries, idempotency, webhooks, rate limits, sandbox-to-production rollout, and reconciliation when the other side fails mid-flow.

- Work directly with a vendor's technical team to get an integration over the line.

- Manage Queues, background jobs and scheduled work, including what happens when a job runs twice.

- Perform React with TypeScript.

- Execute Component design, state management, forms that hold up under real user behaviour.

- Build a clean screen without a pixel-perfect design handed to you using enough CSS and layout sense.

- Ensure Performance and correctness on the browser side: loading states, error states, the ugly edge cases.

- Write Tests you actually write.

- Maintain Git discipline, CI/CD, and enough DevOps grounding to be self-sufficient: containers, workplace configuration, pipelines, deployments and rollbacks.

- Understand AWS fundamentals: how your service runs, scales and fails.

- Instrument what you build logs, metrics, alerts so problems surface on a dashboard rather than in a customer complaint.

- Read monitoring output and act on it: triaging an alert, finding the root cause, and closing the loop with a fix or a tuned threshold rather than muting it.

- Keep an eye on infrastructure cost.

- Know roughly what your service costs to run, spotting the query, log stream or API call pattern that is quietly expensive, and factoring that into design decisions.

- Understand the problem first-hand.

- Spend time with the product owner or the ops team that has the problem, and see how the work happens today rather than working from a requirements document alone.

- Design, build and ship end to end.

- Take it to production and keep it healthy.

- Deploy it, monitor it, and act on what the monitoring tells you.

- Watch for Errors,



latency, failed jobs and data quality and ideally spot the issue before someone reports it.

- Be mindful of what it costs to run.

- Think about instance sizing, storage, query patterns, log volume and the cost of third-party API calls before you ship, and raise it early when something is likely to get expensive.

- Integrate cleanly with vendors and partners.

- Work well with vendor teams, reading their documentation carefully and handling their failure modes gracefully.

- Be accountable for what you commit to.

- Give estimates you believe in, flag slippage early, and keep the status visible.

- Leave it documented.

- Build securely by default.

Skills Required

JavaScript , TypeScript , Node.js , API Design , Relational Data Modelling , SQL , Indexing , Query Optimization , Transactions , Database Migrations , Vendor Integration , Authentication , Retries , Idempotency , Webhooks , Rate Limiting , Queues , Background Jobs , Scheduled Work , React , Component Design , State Management , Forms , CSS , Layout Design , Performance Optimization , Error Handling , Testing , Git , CI/CD , DevOps , Containers , Environment Configuration , Pipelines , Deployments , Rollbacks , AWS , Monitoring , Logging , Metrics , Alerting , Cost Awareness , Problem Solving , Communication , Accountability , Documentation , Security , Risk Management , Architecture Design , Trade-off Analysis

Candidate Attributes

- Passion and hunger to make a dent in the MSME ecosystem.

- Comfortable with ambiguity and will go and resolve it, often by asking the ops or product team directly.

- Share status without being prompted, including when the news is not good.

- Care whether the change worked for the business, not only whether the story was closed.

- Own outcomes, not tickets.

- Sets the plan; trusted with the hardest and riskiest work.

- Owns architecture and the trade-offs behind it.

- Partners with function heads; helps decide what not to build.

Skills

- Javascript, TypeScript and NodeJS (Node.js)

📌 Fullstack Engineer- SDE IV (Mumbai)
🏢 Cutshort
📍 Mumbai