About TorQiTorQi is building a fully managed AI voice platform for the automotive service industry.

Our product is already in production with paying customers and handles real customer conversations, appointment booking, routing, customer intake, and integrations with automotive systems.

We already have a production voice-AI product.

We are not looking for someone to build another AI voice agent.

Our next engineering priority is strengthening the core platform and backend architecture behind the product.

The MissionWe are looking for a senior architect to help us design and evolve TorQi Core — the platform layer responsible for:

- Core business logic
- Multi-tenant architecture
- Data architecture
- Workflow orchestration
- APIs and webhooks
- Third-party integrations
- Queues and asynchronous processing
- Reliability and failure recovery
- Observability and monitoring
- Scalability

Our current platform is already serving production customers. The challenge is ensuring the architecture can reliably grow from tens of customers to hundreds and eventually thousands of customer locations without accumulating fragile dependencies, operational bottlenecks, or unnecessary complexity.

First Mission: Architecture AuditWe are not looking for someone to immediately rewrite the platform.

Your first engagement will be to understand what exists today and determine what actually needs to change.

You will

- Map the existing architecture and critical workflows
- Review backend and service boundaries
- Evaluate data architecture and multi-tenancy
- Review APIs, webhooks, queues, retries, and idempotency
- Evaluate workflow/orchestration dependencies
- Identify single points of failure
- Review observability, logging, monitoring, and alerting
- Evaluate third-party integration architecture
- Identify reliability and scalability risks
- Recommend what to Keep / Improve / Replace
- Design the target-state TorQi Core architecture
- Produce a practical 30/60/90-day implementation roadmap





A Particularly Significant ProblemTorQi integrates with multiple third-party automotive systems. We don’t want our core product architecture tightly coupled to any single external provider.

We need an architecture where external systems can be connected, replaced, degraded, or fail without unnecessarily compromising the rest of the TorQi platform.

Experience designing integration abstraction layers, canonical domain models, adapters/connectors, resilient APIs, and failure handling is highly valuable.

What We’re Looking ForStrong experience with:

- Production SaaS backend architecture
- Multi-tenant SaaS platforms
- PostgreSQL or equivalent relational database architecture
- Node.js/TypeScript and/or Python
- Distributed systems
- API and webhook architecture
- Queues and asynchronous processing
- Idempotency and failure recovery
- Integration-heavy platforms
- Observability and monitoring
- Cloud infrastructure
- High-availability production systems
- Scaling real production applications

Bonus, but not required: Experience with voice AI, telephony, real-time systems, communications platforms, automotive software, or workflow/orchestration platforms.

What We’re NOT Looking ForThis is not primarily a:

- Prompt engineering role
- RAG/chatbot role
- Frontend role
- LLM integration role
- MVP development role

We’re looking for someone who has dealt with real production architecture after customers, traffic, integrations, failures, and operational complexity entered the picture. How We Think About ArchitectureWe don’t want someone who recommends a particular database, cloud provider, microservices, Kubernetes, or a complete rewrite simply because that’s what they know.





We’re looking for someone capable of looking at an existing production system and saying:

“Keep this. Improve this. Move this into the core platform. Don’t touch this yet. This becomes a problem at 10× scale, and here’s why.”

Architectural judgment matters more to us than technology preferences.

Potential Long-Term OpportunityIf the initial architecture audit is successful, this can develop into a longer-term relationship involving:

- Guiding implementation of TorQi Core
- Reviewing critical engineering decisions
- Mentoring backend engineers
- Establishing engineering standards
- Helping recruit additional engineers
- Periodic architecture reviews as TorQi scales

Experience: 8+ years of professional software engineering experience, including 3+ years owning or leading backend/platform architecture for production SaaS systems.

Must have experience designing or scaling real production systems with meaningful customer traffic, multi-tenancy, third-party integrations, reliability requirements, and operational complexity.

A cover letter is mandatory for this role.

Please send your resume and cover letter to [email protected]

Applications without a cover letter will not be considered.



Please keep it concise and address the following:

1. Briefly describe the most relevant production SaaS/platform architecture you have personally designed or owned. What scale did it reach?
2. Tell us about a system you inherited that was already in production. What did you keep, what did you change, and what did you deliberately not rebuild?
3. Describe your experience with multi-tenancy, integration-heavy systems, reliability, observability, queues/retries, and third-party API failures.
4. You inherit a production platform that may need to support 10–50× its current volume. What are the first five things you would investigate before recommending architectural changes?
5. Why do you believe your experience is specifically relevant to TorQi Core, rather than simply general software or AI development?

📌 Principal Backend / Platform Architect — AI SaaS (Bengaluru)
🏢 TorQi
📍 Bengaluru