Engineering · Architecture · Ownership
Platform Architect
Take an important product outcome from incomplete direction to a working system: a clear technical plan, reliable deployment, and visible operational ownership.
Role at a glance
- Location
- Ahmedabad, Gujarat
- Employment
- Full-time · On-site
- Experience
- Production ownership matters more than one exact technology history
- Reports to
- Founder & CEO
A hands-on company-wide engineering role for someone who can move between product, code, data, deployment, and operational failure without losing accountability. You will stay close to the code, guide other builders, and remain responsible until the complete system works in production.
Why this role exists
SVECTOR is moving from separate product builds toward a coherent shared platform. This role converts product direction into dependable architecture, working software, and repeatable releases while reducing fragmentation across codebases, data models, environments, and engineering decisions.
What you will own.
- 01
Ship production software across frontend, backend, data, and AI-assisted workflows.
- 02
Understand and own complete product flows, including failure states and human review.
- 03
Translate incomplete product direction into architecture, sequence, dependencies, test conditions, and a release path.
- 04
Define practical module boundaries, APIs, data models, permissions, and integration patterns.
- 05
Build evidence-grounded AI workflows with retrieval, structured outputs, evaluations, citations, and review.
- 06
Own environments, access controls, logs, monitoring, backups, releases, rollback, and incident response.
- 07
Review technical work, correct weak decisions early, and raise the output of other builders.
- 08
Maintain concise records of architecture, material decisions, risks, owners, and next actions.
What strong evidence looks like.
- 01
Strong engineering fundamentals and evidence of owning real production systems.
- 02
Hands-on judgment across product, architecture, implementation, deployment, and reliability.
- 03
The honesty to separate production experience from experimentation.
- 04
The ability to work with younger and older contributors without dismissing either group on age or title.
- 05
Comfort with direct technical debate, visible assumptions, and accountability after release.
What success looks like.
- 01
Complete workflows are shipped, used, and supported rather than left as partial prototypes.
- 02
Architecture, code quality, access control, testing, deployment, and operational discipline improve visibly.
- 03
Risks are raised early with facts, options, and a recommendation.
- 04
Shared foundations let SVECTOR move between products without rebuilding basic infrastructure each time.
Boundaries
What this role is not.
- 01
A detached architecture role that ends with diagrams.
- 02
A project-management role that only updates trackers.
- 03
A narrow coding role attached permanently to one module.
- 04
A title for someone who wants authority without production accountability.
Apply
Show us the work behind the claim.
Share one or two systems you personally built. Explain the architecture, scale, trade-offs, failures, and measurable outcomes with enough detail for a serious technical conversation.