Architecture direction
Clarify boundaries, risks, data flow, and an implementation path before a team commits deeply.
Collaboration
Bring the difficult part of the system into focus.
I work best where the backend carries real consequences: identity, money, operational data, time-sensitive events, or a team’s ability to keep shipping.
Begin with an emailWays to work together
A small number of useful shapes.
Remote from Kathmandu, with overlap arranged around the work.
Backend delivery
Own a consequential service or integration from technical design through production handover.
Systems review
A focused second opinion on reliability, scale, security, or a migration that has become difficult.
A good beginning
What to include in the first note.
- 01The outcome the system must create.
- 02The constraint currently shaping the work.
- 03The team, timeline, and stage you are in.
Correspondence