Why This Role Exists

Our client needs a senior engineer who can own features end to end. The roadmap is moving, the team is small, and the gap is not frontend polish. It is someone who can build the service, design the data layer and ship the whole thing to production.

Your job is feature throughput. You pick up well defined work, build it across the stack, and hand the team finished, reviewable code. The measure of a good week is not hours logged, it is how much working, tested software is ready to ship.

The Focus of This Seat

This is a fullstack seat weighted toward the web, but read the requirements carefully: the depth we are screening for is backend, data and infrastructure.

The existing team is well covered on frontend. What is thin is engineers who can own a service, design a schema, reason about a queue, and understand the infrastructure their code runs on. You will ship web features in React and TypeScript, and you will be expected to build the API, the data layer and the deployment path behind them yourself.

If you are a React engineer who consumes APIs, this is not the right seat. If you are a backend engineer who ships confidently on the front end, it likely is.

What You'll Bring

Backend and data (the core of this role)

1. 4 to 7+ years building production software, with substantial backend ownership.
2. Node.js and TypeScript in production. Services you designed, built and operated, not endpoints you called. NestJS, Express or Fastify.
3. SQL and Postgres at a real level. Schema design, migrations, indexing, query optimization, and the judgment to know when the data model is the actual problem.
4. API design. REST at minimum, GraphQL or gRPC welcome.
5. Asynchronous and event driven patterns. Queues, workers, background jobs, retries and idempotency. SQS, RabbitMQ, Kafka or equivalents.
6. Caching in production. Redis or comparable, including invalidation strategy and what happens under concurrent load.

Infrastructure

1. AWS in day to day use: Lambda, SQS, RDS, S3, CloudWatch, IAM.
2. Docker, and comfort operating in a containerized environment.
3. CI/CD you have configured yourself, not just consumed.
4. Observability. Logs, metrics, traces, and the ability to diagnose a production issue from them.

Frontend

1. React and TypeScript. State management, rendering performance and component architecture, with the judgment to know which of those a given problem actually needs.
2. Next.js or comparable, and a working understanding of what happens server side.
3. Comfort picking up React Native work when the mobile surface needs it.

Working style

1. Testing discipline. Integration and end to end coverage as a habit, not an afterthought.
2. Exceptional professional English, written and verbal. Communication here is largely asynchronous and directly with US stakeholders.
3. Self direction. You prioritize, decide and finish work without a lead standing over you.

How Your Work Needs to Land

This matters as much as the technical bar, so we are stating it plainly. Work only creates value if it is reviewable by someone who was not there when you wrote it. That means:

• Tests ship with the feature, not in a follow up
• Pull requests are small and self contained; large features arrive as a reviewable sequence
• PR descriptions explain the what and the why well enough to review cold
• Anything you could not finish is documented clearly enough for someone else to pick up
• Production risk is never taken unilaterally

If your instinct is to hand off a large unexplained branch, this is not the right seat.

What Sets You Apart

1. Infrastructure as code: Terraform, Helm, Argo CD, Kubernetes.
2. Experience with low latency or performance sensitive systems, especially anything with sharp traffic peaks.
3. Payment or third party integration work, including webhooks, idempotency and reconciliation.
4. Data engineering exposure: ETL or ELT pipelines, warehousing, search infrastructure.
5. Microservices, distributed systems and multi tenant architecture.
6. Monorepo and shared package experience.
7. Analytics tooling such as Amplitude or Segment.
8. Prior consulting or staff augmentation experience, comfortable embedded inside a client team.

Why You'll Love Working With Us

Remote first, working with a top tier US client on a product real users touch every day. The stack is modern end to end, the team is small enough that your decisions stick, and you will finish most weeks with something concrete to show for it.