Backend engineering notes from building real systems Go, concurrency, and distributed backends.
About
I'm a backend developer who likes systems where getting it wrong costs money or breaks trust auctions, payments, anything with real concurrency and state to protect.
My stack is Go, gRPC, PostgreSQL, and Redis, with Docker for everything I ship. I'm currently a Full Stack Developer Intern at Bridgeon Solutions, building backend services in Go and Gin with PostgreSQL and Redis.
Outside of work, I'm building PriceFlow, a multi-service auction marketplace: an in-memory bid engine that survives a crash and rebuilds itself from persisted events, a wallet and escrow system where every money movement is idempotent, and Razorpay payment integration behind JWT auth and role-based access. I also built IronForge, a full-stack e-commerce platform, where PostgreSQL indexing cut product search time significantly.
I'd rather deeply understand one hard system than skim ten easy ones.
I'm currently looking for my first full-time backend engineering role at a product company ideally one where I'll be pushed by senior engineers and get to work on problems with real technical depth.