Platform Engineer

About SVECTOR

SVECTOR builds intelligence infrastructure for enterprises and institutions making complex, high-consequence decisions. We build and own products, workflows, data systems, and technical infrastructure that integrate context, evidence, data, AI, human judgment, and operational workflows into dependable systems. Our work spans areas such as talent intelligence, financial intelligence, defensive intelligence, and other enterprise decision systems. We believe the AI model is only one component; the architecture around it—workflow, data, permissions, evidence, integrations, auditability, reliability, and system improvement—is what matters. We are building the technical foundation for a stronger, shared platform.

The Role

We are hiring a Platform Engineer to take meaningful technical ownership across our environment. This is not a narrow development role with pre-defined tickets. You will collaborate with the Founder and engineering team to evolve important product problems from incomplete direction to clear technical approaches, implementation, deployment, and reliable operation. The ideal candidate will understand the complete product flow, think about architecture while remaining grounded in implementation, write production code, investigate failures, make sound technical decisions, and elevate engineering standards. We seek individuals with unusually strong technical ability and problem-solving depth relative to their experience, welcoming both exceptional early-career engineers and those with several years of experience. Capability, judgment, learning speed, and demonstrable building experience are valued over title, seniority, or tenure at large companies.

What You Will Own

Your responsibilities span the full product lifecycle, from requirement to production:

• Translating product direction into practical technical architecture and work sequences.
• Building production software across frontend, backend, data, and AI-assisted workflows.
• Understanding the entire product journey: user entry, data capture, service communication, decision generation, evidence storage, and failure handling.
• Designing APIs, data models, services, permissions, integrations, and reusable platform components.
• Building systems using modern backend and frontend technologies.
• Working with LLM APIs, retrieval systems, structured outputs, search, model orchestration, evaluations, and human-review workflows where genuinely beneficial.
• Building reliable asynchronous workflows, workers, queues, retries, and background processes.
• Working with SQL and NoSQL databases, data modelling, migrations, indexing, and data integrity.
• Managing deployment, environments, access control, secrets, logging, monitoring, backups, releases, and rollbacks.
• Debugging system-wide issues, not just within your module.
• Testing complete workflows, including edge cases and failure conditions.
• Reviewing code and technical decisions made by other engineers.
• Identifying weak architecture or technical shortcuts before they become significant problems.
• Making routine technical decisions independently and raising important risks early.
• Ensuring architecture and critical technical decisions are comprehensible for system extension by other strong engineers.

What We Are Looking For

We seek a builder with strong technical instincts, capable of breaking down unclear problems. You should be able to fluidly move between product thinking, architecture, code, data, deployment, and debugging with a sense of ownership. Quick learning in unfamiliar technical areas is crucial. We value individuals who can move forward without constant direction, disagree technically with sound reasoning and propose better approaches, and execute on those solutions. The focus is on the complete system's success, not just assigned tasks, with accountability for outcomes. Genuine problem-solving ability is paramount.

We Are Not Looking for Vibe Coders

Hiring is driven by capability, not trends. We are not interested in candidates whose technical identity is primarily based on AI buzzwords, social-media trends, certificates, copied projects, or an extensive, superficial list of frameworks. While using AI tools for speed is normal, a lack of understanding of the code or system being built is not. We seek engineers who can explain the underlying architecture of their work, not just generate impressive prototypes. We are not looking for prompt-only engineers or those who indiscriminately add "AI" to every solution. Deep understanding of at least one personally built system is preferred over broad, shallow knowledge of many tools. We want engineers who use technology intelligently, including AI, but retain a strong grasp of software engineering, systems, data, failure modes, and first-principles problem-solving. The strongest candidate may not know every current technology but must be capable of rapid learning.

Technical Background

There is no single mandatory technology stack. Excellent fundamentals and exceptional learning ability are prioritized over superficial familiarity with many tools.

What Good Looks Like

A strong candidate can explain in detail a system they personally built: the problem solved, their individual contribution, system mechanics, architectural choices, considered alternatives, failures, difficulties, debugging process, scalability implications, and potential redesigns. The depth of these answers is more important than a long list of technologies on a CV.

Examples of Strong Evidence

• A deployed product you built.
• A significant personal project.
• A GitHub repository demonstrating meaningful engineering work.
• A production system you owned.
• An open-source contribution.
• A technically challenging university project with clearly identified personal contributions.
• An unusual technical experiment showcasing deep thinking.
• Evidence of independently learning and applying difficult technology.

What This Role Is Not

This is not a project-management role, nor is it solely for coordinating other developers. It is not a detached architecture role focused only on diagrams without building. It is not a position where you permanently own a single small component while ignoring the broader product. Progress is not measured by tickets closed; the expectation is technical ownership.

Working at SVECTOR

You will join a high-performance team where strong individuals are given significant responsibility early. You will have direct access to the Founder and are expected to communicate clearly about issues, incompleteness, or technical weaknesses. Expect ambiguity, difficult technical problems, and situations requiring independent problem-solving beyond available documentation. We value independent judgment, speed of learning, technical honesty, ownership, and the ability to transform difficult problems into working systems.

Location

This is a full-time, on-site role in Ahmedabad, Gujarat, India. Candidates must be currently based in Ahmedabad and able to work from the office. This is not a remote or hybrid position.

Selection Process

Our selection process focuses on evidence of actual ability:

• Initial conversation: Background, motivation, and technical interests.
• Deep technical discussion: Focus on one or two systems you personally built.
• Discussion on architecture, failures, trade-offs, debugging, and problem-solving.
• Alignment on responsibilities from day one.
• Final discussion: Role and compensation.

If you are technically ambitious, learn unusually fast, enjoy challenging problems, and desire substantially more ownership than a conventional engineering role, we encourage you to apply.