WORK WITH ME

Consulting and contract engineering

I take on consulting and contract work in backend and cloud engineering, and at the hardware and low level end of things. I am based in New Delhi and work remotely.

What I take on

  • Backend and APIs Node, TypeScript, Go and Postgres. The services themselves, and the parts around them that decide whether you sleep at night: migrations, observability, and the failure paths nobody wrote down.
  • Cloud architecture AWS and GCP. CDK, Lambda, ECS Fargate, Cloud Run, BigQuery. The interesting question is rarely which service to pick, it is what the system does when one of them is unavailable.
  • Engineering leadership Architecture review, code review, and working with a team rather than around it. I have led delivery across web, mobile and cloud, and I still write enough code to be honest about estimates.
  • AI in real products LLM integration and generative features. Most of the difficulty is in the plumbing, the evaluation and the cost, not in the prompt.
  • Embedded and hardware Firmware, board bring-up, PCB layout and display or sensor drivers. Useful when a product has a physical half and the team is all software.
  • Reverse engineering Ghidra, IDA Pro and x64dbg. Working out what a binary does when there is no source and no documentation, including code that arrived somewhere it should not have.

How I work

Remote, from New Delhi. Most of the teams I have worked with sit in other timezones, so I keep a few hours of overlap and put decisions in writing.

I would rather work inside your team than beside it. Your developers have to live with this after I am gone, so I review and pair as I go instead of dropping a handover document at the end.

If a problem needs something I am not good at, I will say so. I would rather lose the work than learn on your budget.

Work I can show publicly

Most of what I build belongs to other people and sits behind an NDA. These are the pieces I can point at, so you can read the actual work instead of taking my word for it.

Getting in touch

For the work I cannot publish, a call is easier than anything I can write here. I am happy to walk you through what I built, what went wrong on the way, and whether any of it is close enough to your problem to be useful.

Send me a rough description of the problem and what you have already tried. That is usually enough for me to say whether I am the right person, and to point you somewhere better if I am not.