Amit SapkotaSenior backend engineer
Thirteen years at RBS, Goldman Sachs and ServiceNow, keeping financial and enterprise data correct at scale. Since June 2026 I’ve been designing and shipping my own products end to end, from the data model to the App Store.
Experience
2013 → now
Thirteen years where a wrong number was a real problem: market risk, regulatory reporting, and the configuration data large companies run on.
2013–2015
Application support analyst
Kept four market-risk applications running, automated their monitoring, and fed root causes back to engineering.
2015–2020
Software engineer
Built a shared persistence layer that many applications came to rely on, and automated the regulatory-reporting workflow between risk and reporting teams.
2020–2026
Senior software engineer
Owned core CMDB features from design to production, and was an escalation point for critical customer incidents.
2026–
Product engineer
Agent-native systems on Cloudflare and apps on the App Store, each designed, built and shipped by me.
B.S. Electrical Engineering, Brigham Young University, 2012Full résumé (PDF)
Work
Systems · Apps
Production repositories stay private. Where an entry links to code, it is a public, versioned snapshot you can read.
An agent-native job-search system. Claude researches companies and runs interview drills; the application keeps every fact.
How it’s built. One Cloudflare Worker serves a board for me and an OAuth 2.1 MCP server for the agent, over a single D1 database. Atomic multi-record writes, relational history, optimistic concurrency on prep notes, and guarded deletion. The app itself makes no AI calls.
Code In production, privately
Shared expenses for family events. Guests open a link; nobody installs an app or makes an account.
How it’s built. React and Hono on Workers with D1. Money is whole cents, and one rounding routine runs on client and server, so every split adds up to the cent. A retried request can’t record an expense twice. Settlement locks atomically to one payer of record. Organizers sign in with passkeys.
Private pilot, used at a real family event
Nepal’s favourite card game on iPhone: solo, at the same table, or over Game Center.
A 156-card rules engine with regional variants. In multiplayer the host decides every move and sends each player only their own cards.
I first shipped Call Break in 2013. It spent five months in the top 10 card games in several countries and was delisted in 2018. In 2026 I rebuilt it from scratch, on the same App Store listing.
A headless engine owns bidding, legal moves and scoring. Injected randomness makes every game replayable; the hardest bot tracks every card played.
Strength training that knows when to push and when to rest.
Readiness is scored against your own rolling baseline. A missing signal’s weight is spread over the others, and when it rescores past days it never looks ahead.
An atlas you can use right now: 255 countries, 7,294 cities, shaded relief and guided journeys. No sign-in.
Relief reprojected into map tiles at build time, labels that never collide, and the place you’re looking at kept in the URL.
Open the atlas In the browser
Index
日本語 · नेपाली
I grew up in Nepal and am learning Japanese, slowly and stubbornly. Nearly everything I build starts as a corner of my own life, and the names give it away.
Process
One engineer, a written process, and AI agents doing most of the typing. Every change goes through its own branch, a build and the tests. Anything touching money, user data, auth or migrations gets an adversarial review before it merges. Specs, decisions and handoffs live in the repository, never only in a chat.
Always glad to connect, whether it’s engineering, apps, or a good book.