Job DescriptionTechnical Architect — Product Engineering
NExperience: 12+ years in software engineering, with at least 6 in product engineering
NNotice period: immediate to 60 days preferred;
buyout considered for the right candidate
NReports to: Delivery Manager, with a direct working line to the client's principal engineer
NEngagement: Full time/permanent on SUIPL payroll
NAbout the role-
nSUIPL is building a new multi-tenant SaaS platform for an international client. The client, the sector, and the product are confidential until launch. We are direct about that up front rather than hinting at it: the domain and commercial context are described in full under NDA at the final interview stage, and not before. What we can describe completely is the engineering, which is the part that should decide whether you want the job.
NYou are the senior technical owner of the build. Greenfield, no existing codebase, no inherited constraints. You set the data model, the domain architecture, and the service boundaries, and you carry those decisions through implementation.



The pod grows from five engineers to ten around you.
NThe work is architecturally demanding rather than novel. It is a transactional system where correctness matters more than throughput: long-lived records edited concurrently by several people in different roles, strict auditability, financial accuracy, and a set of third-party dependencies that are unreliable in ways you have to design around rather than complain about. If you have built systems where a wrong write costs someone real money, you will recognize the shape of it.
NYour architecture is reviewed and formally approved in writing by the client's principal engineer before implementation begins. If that reads as interference, this is not your role. If it reads as having a peer who will engage seriously with your design instead of rubber-stamping it, it is.
NWhat you will own-
nDomain and data architecture
N
- n
- The multi-tenant

📌 Hiring: Principal Engineer (India)
🏢 Stabdha
📍 India