Backend Engineer · Spring Boot · Microservices · AWS
Currently SDE @ Brahmin Solutions (Miami, FL · US) · Dec 2024 – Present
Your startup's backend
should scale with you,
not slow you down.
I help startups ship reliable, production-grade backends using Spring Boot, Microservices, and AWS — so your team can focus on growth instead of firefighting outages.
Sound familiar?
Your backend is costing you more than you think.
Scaling a startup is hard enough. Your backend shouldn't be the thing that holds your business back — or keeps you up at night.
Your backend can't handle growth
Traffic spikes crash your servers. What worked at 1,000 users falls apart at 50,000 — costing you customers and credibility.
Unreliable APIs blocking your product
Flaky endpoints, silent failures, and inconsistent data are slowing down your frontend team and frustrating your users.
Every new feature takes too long
A tangled backend means even simple changes require weeks of work, risk breaking something else, and drain your team's energy.
What I do
What I can do for your team
Each engagement is scoped to your specific bottleneck — not a retainer for work you don't need.
01
A backend your team can actually ship on
Your product moves fast. I build the server-side foundation underneath it — REST APIs, third-party integrations (QuickBooks, Xero, payment systems), and the reliability layer that keeps your data consistent across every system.
02
Go from one big system to many small ones
When everything is tangled together, a small change risks breaking everything else. I split it apart cleanly so each piece can be worked on and released on its own.
03
Keep your app fast as your user base grows
Slow load times and timeouts push users away. I find what's causing the slowdown and fix it — so your product feels snappy whether you have a hundred users or a hundred thousand.
04
Ship to production without holding your breath
Move from manual, error-prone releases to an automated setup on AWS. Your team deploys with confidence, fewer things break in production, and incidents become rare.
Proof of work
Case Studies
Dec 2024 – Present · Cloud MRP & inventory SaaS for manufacturers · US-based · 19 microservices in production
Built the backend foundation 19 microservices run on today
Problem
A Java monolith was becoming a bottleneck. As the platform grew to support warehouse management, sales, and accounting workflows, every change risked breaking something else. Multi-tenant client onboarding was also unreliable — a critical domain routing issue was blocking multiple client environments from going live.
What I built
Designed and built the core microservices architecture from scratch: 19 services spanning inventory, sales, accounting, auth, and configuration. Implemented multi-tenant support with per-client domain routing and JWT authentication. Built a shared common library used across all services to standardize auth, config, and base logic. Diagnosed and fixed the critical domain routing bug that was blocking production onboarding of new clients. Contributed to AWS infrastructure across EC2, API Gateway, Route53, CloudFront, S3, and Secrets Manager.
Impact
The architecture built here is what the current team develops on every day. Multi-tenant client onboarding works reliably. A critical production-blocking bug was resolved before launch. The system now supports ongoing feature development across multiple domains — at a pace and stability the original monolith couldn't sustain.
Dec 2024 – Present · Cloud MRP & inventory SaaS for manufacturers · US-based · QuickBooks + Xero sync
Reliable accounting sync across QuickBooks and Xero in production
Problem
The platform needed to keep invoices, payments, and orders in sync with QuickBooks and Xero in real time. Without a reliable integration layer, the finance team was manually reconciling records — and any failure meant client data was silently out of sync, sometimes for days before anyone noticed.
What I built
Built an event-driven integration layer connecting the platform to both QuickBooks and Xero. Syncs run asynchronously with retry logic, error handling, and structured logging — so a failed job is caught, logged, and retried instead of silently dropped. Added real-time WebSocket updates for bulk operations and email automation via Mailchimp for workflow notifications.
Impact
Accounting data stays consistent across systems without manual intervention. Finance teams no longer reconcile records by hand. Integration failures surface immediately through alerting rather than being discovered days later by a client — a direct improvement in platform trust and support overhead.
Let's solve it together
Need help building or scaling
your backend?
Let's discuss your project. In 30 minutes I can tell you exactly what's slowing you down and what it would take to fix it.
Schedule a CallGet in touch
Let's talk about your project
Book a free 30-minute call. No pitch — just a straight conversation about what's slowing you down and whether I can help.
Typical engagements run 2–6 weeks. Scoped and priced per project after the call.
Here's how it works:We spend 30 minutes on a call where I ask about your system and you tell me what's breaking. If it's something I can fix, I'll send a short proposal — scope, timeline, and cost — within 24 hours. I work alongside your existing team, document everything I build, and make sure the knowledge stays with you. No commitment until you've seen the proposal.
Takes 30 seconds to book • No back-and-forth emails
Available for calls in evenings (IST). Production emergency? Email me directly and I'll respond within 2 hours.