Official portfolio · Akash Reddy Vanga (Akash Reddy, Akash) · same engineer as Vanga Akash Reddy
Backend Engineer with 2.5+ years at JaaGa.AI, building revenue-critical services on Node.js, MongoDB and AWS. I work on payment integrations, queue-driven workers, document automation and internal platforms — and I own them end-to-end, from API contract and data model through to deployment, monitoring and on-call.
Pulled from the dependency manifests of the production codebases I work in every day — not an aspirational list. Highlighted pills are what I reach for most.
Systems I’ve built before and can build again from a blank repo — described as Build · Harden · Operate, because shipping the happy path is the easy third of the job.
These are capability areas, not a client list. My employer’s product details stay confidential — but the engineering below is mine, and I’m happy to go as deep as you like on any of it in an interview.
How I actually operate day to day — the habits that keep revenue-critical services boring, and make my work easy for the next engineer to pick up.
Spec before code. I write the API contract and data model first and agree it with whoever depends on it — finance, ops, product or legal. Most of the expensive bugs I’ve seen were disagreements about meaning, not broken syntax.
Never test in production. I run changes locally against a local database or a staging stack before they touch a live system, and I clean up after myself when a test does leave a trace. Payments and customer-facing messages don’t get a “let’s see what happens”.
Security is part of the definition of done. I review my own work for injection and auth gaps, verify webhook signatures, keep secrets out of source control and rotate credentials as part of a migration — not as a follow-up ticket someone files later.
Small, readable commits. Scoped conventional commits (feat(scope): …), one logical change each, so history stays reviewable and a bad change is one revert away instead of an archaeology project.
Write it down. Every codebase I own carries its own README, architecture notes, deployment guide and changelog. If I disappeared for a month the team could still ship — that’s the bar I hold myself to.
AI as leverage, not autopilot. I use AI for the boring 70% — scaffolds, boilerplate, test cases, log spelunking. I keep the parts that don’t delegate well: API contracts, data modeling, idempotency, threat modeling and incident response. Every AI-assisted change clears the same review bar as code I write by hand.
The six things that should close a hiring decision.
Promoted in 2 yrs
Intern → Backend Developer → Software Engineer at JaaGa.AI. Track record of growth, not just tenure.
Full-stack scope
Backend-led, but ships the React/TypeScript front ends too — plus Docker, Nginx and the deploy scripts. Not a single-service engineer.
Handles real money
Payment gateway and UPI integrations built for correctness: idempotent retries, signed-webhook verification, daily reconciliation.
On-call ready
First-line on-call. Runbooks for 3 services. Blameless post-mortems with closed-loop follow-ups.
Owns the whole path
API contract → data model → deployment → monitoring → on-call. Comfortable running the AWS and Cloudflare infra behind his own services.
Ships whole products
Takes a vague business problem to a spec, a schema, a UI and a rollout — not just assigned tickets. Uses AI for the boring parts, owns the judgement calls.
2.5+ years designing and operating revenue-critical services on AWS, MongoDB and Node.js — from architecture to on-call.
I’m a Backend Engineer with 2.5+ years at JaaGa.AI, where I own the design and delivery of payment, automation and notification systems used by real customers every day. (Specifics of my employer’s products stay with my employer — happy to talk through the engineering in an interview.) I’ve grown from contributing to existing services to architecting new ones end-to-end — from API contract and data model to deployment, monitoring and on-call.
My core stack is Node.js, Express, MongoDB and AWS, with React + TypeScript on the front end and Cloudflare Workers at the edge. The work spans payment-gateway and UPI integrations, queue-driven background workers, OCR and AI document processing, notification and messaging platforms, and internal tooling for the teams that run the business day to day. I think a lot about idempotency, retry semantics, observability and zero-downtime rollouts — the unglamorous work that keeps production calm.
I work across the full surface: a Node.js service and worker layer on AWS, several React / TypeScript front ends, and edge services on Cloudflare Workers, D1 and R2. I also handle Docker, Nginx and deployment scripts across dev, staging and prod — so I’m comfortable moving from API contract to a live, monitored rollout without hand-offs.
Beyond shipping code, I write runbooks, collaborate in reviews when my domain comes up, and partner directly with finance, ops and product to turn ambiguous business problems into specs the team can ship. I lean on AI tooling for boilerplate so I can spend more time on system design, debugging and lifting the team around me.
Looking for Backend, Platform or DevOps roles where I can own services from spec to scale — and grow into a tech-lead seat.
2.5+ years of hands-on backend development, progressive responsibility, and production-grade system delivery.
Leadership for me means taking responsibility, helping teammates succeed with pairing and clear guidance, and communicating openly across engineering and stakeholders—so outcomes ship reliably, not just individual tickets.
Work closely with teammates on tough bugs and design trade-offs; document decisions and edge cases so context spreads without me being a bottleneck.
Ship with the same patterns I want in production: idempotency, retry semantics, observability and tests — so services stay predictable under load and easy for others to change safely.
Took a payment flow from frequent failures to boringly reliable — wrote the spec, drove stakeholder buy-in, shipped the rewrite, set up the monitoring, took first-line on-call.
Daily collaborator with finance, ops, product and legal on revenue and document workflows. Translate ambiguous business asks into precise specs the team can ship against.
First-line on-call for backend services. Lead blameless post-mortems, write up RCAs and own follow-up actions to closure — not just “we’ll be more careful next time”.
Wrote runbooks for 3 production services and run monthly internal sessions on Node.js performance, MongoDB indexing and AWS cost-tuning. Lift the floor for everyone.
Honest leveling — not a wall of logos. The stack I use to ship and operate services in production.
Formal education and certifications in core computer science and emerging technologies.
The questions hiring managers usually ask first — answered in plain English so you don’t have to dig.
Open to Backend, Platform or DevOps roles — full-time, hybrid in Hyderabad or remote. 2.5+ years shipping production systems on AWS, MongoDB and Node.js. I usually reply within a few hours.