Skip to content

Careers

Careers at Bhogar

We are a small team building enterprise AI infrastructure that has to pass security review, handle production data volumes, and stay operable day to day. Here is what we hire for and how we work.

Colleagues planning at a whiteboard covered in sticky notes

Open roles

No advertised roles right now.

We publish roles only when the seat is real. There are no advertised positions at the moment, and we would rather show an empty list than an evergreen one. Open applications are read: tell us which discipline below fits, what you have built, and what you want to own next.

Send an open application
Three colleagues working from laptops on a sofa in an open office

Disciplines

Areas we hire into

The platform spans data, retrieval, agents, workflows, governance, and infrastructure. These are the areas with open ownership.

Platform engineering

Multi-tenant control plane, workspace separation, API surface, service availability.

Good fit · People who have operated multi-tenant systems and hold opinions on migrations and failure modes.

AI runtime

Agents, orchestration, retrieval quality, evaluation, and the LLM gateway.

Good fit · Engineers who care more about retrieval quality and evaluation harnesses than prompt tricks.

Product and design

Surfaces for builders, admins, and operators - including approvals and cost review.

Good fit · Designers energised by dense enterprise interfaces, not marketing pages.

Security and infrastructure

Identity, secrets, audit, deployment topology, residency, and evidence for security review.

Good fit · People who can hold a security review and a Kubernetes rollout in their head at once.

Solutions engineering

First implementations: data coverage, workflow design, and instrumenting the customer metric.

Good fit · Engineers who enjoy being in the room when the business process gets redesigned.

Go to market

Explaining the platform honestly - including its limits - and building what buyers and security teams actually need.

Good fit · People who qualify out early rather than win deals that churn.

Culture

How we work

  • Ownership from data model to screen

    Problems are assigned, not tasks. Owners hold the schema, the API, the interface, and the pager.

  • Written before scheduled

    Proposals are documents first, so they can be reviewed across time zones and argued with in the margins.

  • Production is the scoreboard

    Demos are easy. We are graded on behaviour under real data, real permissions, and real load.

  • Say the uncomfortable thing early

    Raising a known issue is the job, not negativity.

Interviewing

Our interview process

  1. 1

    Intro conversation

    What you have built, what you want to own next, and whether the scope matches. Compensation range is discussed openly here.

  2. 2

    Technical or craft deep dive

    A working session on a real problem. No trick questions and no take-home marathons.

  3. 3

    System and collaboration review

    A discussion with future peers on design trade-offs, failure modes, and how you handle disagreement.

  4. 4

    Decision and references

    A clear answer, quickly, with the reasoning. If it is a no, we tell you what informed it.

Not sure which discipline fits?

Write to us anyway. We reply to every application with a real answer.