Careers
Build the inference layer a country runs on.
paranine is a small team in Pakistan building a sovereign AI gateway and an NPU-native serving stack. When we hire, the roles appear on this page first.
- Huawei Ascend 910B
- Go on the hot path
- ClickHouse telemetry
- Django control plane
- Next.js dashboard
Four things that are true of the team before anything is true of a role.
Own the hardware problem
Ascend is unfamiliar silicon with a thin ecosystem. The learning curve is the job, not the excuse; we write the kernels, the batching and the runbooks ourselves.
Small team, whole problems
One person carries a problem from the serving stack to the dashboard. Nobody hands a ticket over a wall, and nobody waits a sprint for an answer.
Accountable for uptime
We are on call for what we ship. The people who wrote the Ascend serving stack are the people who answer when it pages, and customers know their names.
Write it down
Decisions, runbooks and the reasons behind them live in the repo. The next person starts from the record, not from a rumour or a meeting they missed.
Four surfaces, one stack, no walls between them.
Every engineer here touches more than one of these. The gateway is what a customer calls; the NPUs are what answers; the platform is how they see and pay for it; forward deployment is how it lands inside their team.
The gateway
A Go service on every request
Keys, scope, budgets, metering and the relay to the model, all on the hot path, all measured. Sub-millisecond overhead is the standard it is held to.
NPU serving
Open weights on Ascend 910B
Getting gpt-oss, Kimi and Qwen to run well on 64GB NPUs: batching, KV-cache management, quantisation, and the instrumentation that proves it.
The platform
Billing in rupees, telemetry in ClickHouse
The control plane, the ledger and the dashboard teams run their AI spend from: per-key attribution, hard caps, an audit log, a playground.
Forward deployed
Inside a customer's team
Sitting with an engineering team for weeks, moving a workload onto the P/9 stack and leaving it in production with the people who own it.
What is open right now.
0
No open roles right now.
We are not hiring at the moment. If you have already built the kind of thing described above, write anyway: the next role is usually shaped by the person who writes first, and we answer every note.
Four steps, none of them a trick.
Write to us
A short note with what you have built and a link to it. Code, a paper, a system you ran: something we can read.
A conversation
With the engineers you would work beside, about the work, not a brain-teaser. Ask us anything; we will answer plainly.
A real problem
A small, scoped piece of our actual backlog, paid, so both sides see the work rather than an interview performance.
An offer in writing
In rupees, with the role, the scope and the on-call expectations written down before you say yes.
Not a role, but adjacent: teams that want one of our engineers embedded with them can hire a forward deployed engineer.