Real patients. Real money. Real consequences.
Most architects draw boxes and arrows, hand off a doc, and move on to the next diagram. That's not this job.
At Techdome, you design the system and you're still in the code six months later when it's live, handling real PHI and real transactions, at 2am if something breaks. You'll set the technical bar for an 80+ engineer studio — and you'll defend that bar in design reviews, in PRs, in incident retros, and in front of the clients whose businesses run on what you build.
If "architecture" to you means influence earned through judgment, not a title on a slide, keep reading.
-
Own platform architecture, start to finish — system design, service boundaries, data modeling, API contracts, and the unglamorous NFRs (security, scalability, observability, cost) that determine whether it survives contact with production.
-
Build for the stakes that matter — HIPAA-grade PHI handling, audit logging, access controls, encryption at rest and in transit, tokenization, and airtight segregation of payment data.
-
Architect on MERN (MongoDB, Express, React, Node.js) plus the cloud stack underneath it — containers, Kubernetes, CI/CD, infrastructure-as-code, secrets management.
-
Make the calls nobody else wants to make — build vs. buy, monolith vs. microservices, sync vs. event-driven — and back them up with evidence, not vibes.
-
Set the studio's technical direction — code review standards, reference architectures, and reusable patterns that outlive any one project, and that other architects and tech leads will build on.
-
Build AI-native, from day one — our engineers ship daily with Claude Code, GitHub Copilot, and Cursor. We want architects who have real opinions on how that changes system design, not just how it speeds up typing.
-
Mentor and grow senior engineers into tech leads — through influence and demonstrated judgment, not org-chart authority.
-
Act as a trusted technical counterpart to clients — someone they'll take an unpopular recommendation from because you've earned it.
-
7+ years shipping production software with end-to-end ownership of system design, at architect, principal engineer, or staff engineer level — including at least 2-3 years where you were the final technical authority on a platform, not just a contributor to one.
-
Real, hands-on Node.js and React chops — you architect and you code, no handoff required. MERN preferred; strong Node.js full-stack backgrounds welcome too.
-
Deep cloud architecture fluency on AWS, GCP, or Azure — networking, security, scaling, cost optimization — gained from actually operating systems in production, not just designing them on paper.
-
Battle scars from a regulated or high-stakes domain — healthcare (HIPAA/PHI), payments (PCI-DSS), fintech, banking, insurance — or comparably deep security-critical system design experience.
-
A track record of making and owning hard architectural trade-offs, and living with the consequences of those calls in production.
-
The ability to hold a room — you can defend an architectural decision with evidence and bring skeptical engineers and clients along with you.
-
HIPAA / healthcare compliance in production — audit trails, BAA-covered infrastructure, PHI access controls.
-
Payment systems experience — Stripe, Braintree, tokenization, reconciliation, PCI-DSS environments.
-
Event-driven architecture, microservices, high-availability design at scale.
-
Multi-product, consulting, or venture-studio experience.
-
Prior experience setting technical standards across multiple teams or products, not just one.
-
A real AI-assisted development practice — and opinions worth arguing about on how AI is reshaping architecture.
We're bootstrapped, profitable, and allergic to slideware. 80+ engineers across Hyderabad, Indore, Mumbai, Dubai, and the US — co-building products and taking equity in them. That means we live with our architecture long after launch, not just until the invoice clears
