You'd be one of the first engineers here, building alongside the founder. That means shaping the architecture and the product, not implementing someone else's spec.

The work spans the whole stack — the core engine, the integrations that feed it, the intelligence built on top, the CLI, and the UI. You won't touch all of it at once, but you'll own whole pieces end to end.

It's self-hosted, Go on the backend, and the engine underneath is genuinely hard systems work.

What You'll Do

- Build the core engine — the reconciliation logic that turns everything we ingest into one continuously updated model. This is the hardest part of the system and everything else sits on top of it.
- Connect deeply to cloud providers, IaC tooling, and observability systems — pulling in what each one knows and turning it into one coherent picture.
- Build the intelligence on top — what breaks if I ship this, what caused this incident, what's running that nobody needs. The query is easy. Being right is the hard part.
- Build the context layer that serves the model outward, so incident tooling,



agents, and engineers query real state instead of guessing at it.
- Make AI reason over a large, constantly changing model while keeping every answer grounded. We're not building a chatbot. The substance is the engineering underneath.

Who You Are

- Solid in Go. If you're excellent in another systems language and want to go deep on Go, we should still talk.
- Comfortable across the stack — you can build the backend service and the UI in front of it.
- You've built something hard and owned it. Years on a résumé matter far less to us than that.
- You take a vague problem, decide the right shape, ship it, and own the outcome.
- You use AI as leverage and keep a high bar for what actually ships.

Helps if you've worked with cloud infrastructure, IaC, distributed systems, observability, graph data structures, or LLMs — and especially if you've been the person in the war room at 2am.

📌 Founding Engineer (Coimbatore)
🏢 Platform Pilot
📍 Coimbatore