Platform Engineer

Ahmedabad, Gujarat | Full-time | On-site

About SVECTOR

SVECTOR builds intelligence infrastructure for enterprises and institutions making complex, high-consequence decisions.

We are not building another generic AI application or software-services company. We build and own products, workflows, data systems and technical infrastructure that bring together context, evidence, data, AI, human judgment and operational workflows into systems people can actually depend on.

Our work spans areas such as talent intelligence, financial intelligence, defensive intelligence and other enterprise decision systems.

We believe the AI model itself is only one component of the system. Models will change. Vendors will change. What matters is owning the architecture around them: the workflow, data, permissions, evidence, integrations, auditability, reliability and the ability of the system to improve over time.

We are now building the technical foundation that allows these products to move from individual applications into a stronger, shared platform.

The Role

We are hiring a Platform Engineer who can take meaningful technical ownership across this environment.

This is not a narrow development role where someone receives perfectly written tickets and completes one small part of the system.

You will work closely with the Founder and the engineering team to take important product problems from incomplete direction to a clear technical approach, working implementation, deployment and reliable operation.

The right person should be able to understand the complete product flow, think about architecture without becoming detached from implementation, write production code, investigate failures, make sound technical decisions and help raise the standard of the engineering around them.

We are looking for someone with unusually strong technical ability and problem-solving depth relative to their experience.

We are open to exceptional early-career engineers as well as engineers with a few years of experience. We care far more about capability, judgment, learning speed and what you have actually built than about title, seniority or years spent inside a large company.

What You Will Own

You will work across the complete path from product requirement to production.

Your responsibilities may include

- Translating product direction into a practical technical architecture and sequence of work.
- Building production software across frontend, backend, data and AI-assisted workflows.
- Understanding the full product journey, including how users enter the system, what data is captured, how services communicate, where decisions are generated, what evidence is stored and what happens when something fails.
- 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 they are genuinely useful.
- Building reliable asynchronous workflows, workers, queues, retries and background processes.




- Working with SQL and NoSQL databases, data modelling, migrations, indexing and data integrity.
- Taking responsibility for deployment, environments, access control, secrets, logging, monitoring, backups, releases and rollback.
- Debugging problems across the entire system rather than only within your own 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 expensive problems.
- Making routine technical decisions independently while raising important risks early.
- Keeping architecture and critical technical decisions understandable enough that another strong engineer can extend the system.

What We Are Looking For

We are looking for a builder with robust technical instincts.

Someone who sees an unclear problem and starts breaking it down.

Someone who can move between product thinking, architecture, code, data, deployment and debugging without losing ownership.

Someone who learns extremely quickly when entering an unfamiliar technical area.

Someone who does not need every decision made for them before they can move.

Someone who can disagree technically, explain why, propose a better approach and then execute.

Someone who cares about whether the complete system works, not simply whether their assigned code was written.

Someone who is comfortable being accountable for an outcome rather than only a task.

Most importantly, we are looking for genuine problem-solving ability.

We Are Not Looking for Vibe Coders

We are not hiring because AI is fashionable.

We are not interested in candidates whose technical identity is built primarily around AI buzzwords, social-media trends, certificates, copied projects or rapidly listing every new framework.

Using AI tools to build faster is completely normal. Not understanding the code or system you are building is not.

We are not looking for someone who can generate impressive-looking prototypes but cannot explain the architecture underneath them.

We are not looking for prompt-only engineers.

We are not looking for someone who adds "AI" to every solution whether it is required or not.

We are not looking for engineers who know the names of twenty tools but cannot deeply explain one system they personally built.

We want engineers who use technology intelligently, including AI, but who still understand software engineering, systems, data, failure modes and first-principles problem solving.

The strongest candidate may not know every technology we use today.

They should, however, be capable of learning what they do not know quickly.

Technical Background

There is no single mandatory technology stack.





We would rather hire someone with excellent fundamentals and exceptional learning ability than someone with superficial familiarity across every tool.

What Good Looks Like A strong candidate should be able to sit with us, open something they personally built and explain:

What problem were you solving?

What did you personally build?

How did the system work?

Why did you choose that architecture?

What alternatives did you consider?

What failed?

What was difficult?

How did you debug it?

What would break if the system grew significantly?

What would you redesign today?

We care about the depth of those answers much more than the number of technologies mentioned on your CV.

Examples of Strong Evidence A strong application may include:

- A product you built and deployed.
- A serious personal project.
- A GitHub repository showing meaningful engineering work.
- A production system you owned.
- An open-source contribution.
- A technically difficult university project where your personal contribution is clearly identifiable.
- An unusual technical experiment that demonstrates depth of thinking.
- Evidence that you have independently learned and applied difficult technology.

What This Role Is Not

This is not a project-management role.

This is not a role where you only coordinate other developers.

This is not a detached architecture role where you produce diagrams but do not build.

This is not a role where you permanently own one tiny component and ignore the rest of the product.

This is not a role where progress is measured by tickets closed.

The expectation is technical ownership.

Working at SVECTOR

You will work inside a high performance team where strong people are given meaningful responsibility early.

You will have direct access to the Founder and will be expected to communicate clearly when something is wrong, incomplete or technically weak.

There will be ambiguity.

There will be difficult technical problems.

There will be situations where the answer is not available in documentation and you will have to work it out.

That is part of the role.

We value independent judgment, speed of learning, technical honesty, ownership and the ability to turn difficult problems into working systems.

Location

This is a full-time, on-site role at Ahmedabad, Gujarat, India.

We are specifically looking for candidates who are currently based in Ahmedabad and can work from the office.

This is not a remote or hybrid position.

Selection Process

Our selection process is designed around evidence of actual ability.

The process will typically include:

1. Initial conversation around your background, motivation and technical interests.
2. Deep technical discussion around one or two systems you personally built.
3. Discussion around architecture, failures, trade-offs, debugging and problem solving.
4. Alignment on the responsibility you can take from day one.
5. Final discussion around role and compensation.

If you are technically ambitious, learn unusually fast, enjoy difficult problems and want substantially more ownership than a conventional engineering role usually gives you, we would like to hear from you.

📌 Platform Engineer (Ahmedabad)
🏢 SVECTOR
📍 Ahmedabad