South Delhi · On-site · Full-time

We are not hiring for a stack. We are hiring for a mind.

Blowtrumpet is building a programmatic advertising stack from first principles — a DSP, an SSP, an exchange, and the platform layer beneath them. Real-time bidding at global scale is one of the harder engineering problems in commercial software: bid windows measured in tens of milliseconds, auction logic that has to be correct under load, and infrastructure economics that punish every wasted cycle. Most of the industry solved this once, a decade ago, and has been maintaining the result ever since.

We think there is a better answer, and we are bootstrapped enough to go looking for it.

We want people who find that compelling rather than intimidating.

Credentials

Graduates of tier-1 engineering institutes are preferred, and we say so plainly rather than filtering quietly at screening.

That preference is not absolute. Exceptional programming ability, demonstrated in work we can examine, will override it. If your degree is from elsewhere and your output is remarkable, apply and show us the output.

What is not negotiable is the degree itself. A completed engineering graduate qualification is required regardless of institution.

Who we are looking for

Exceptional programmers, regardless of where they came from.

We do not care whether your last five years were in ad-tech. We care whether you did something remarkable with them. Trading systems, game engines, compilers, logistics, embedded work, computational biology, something you built alone that nobody asked for — all of it counts if the achievement is real and you can walk us through it.

What we are actually screening for:

- Grip over algorithms and logical structure. Not competitive-programming trivia.



The ability to see the shape of a problem, choose the right structure, and reason about what happens when the input grows by three orders of magnitude
- Demonstrated automation instinct. You have looked at a manual process and made it disappear. More than once. This is a temperament as much as a skill
- Advanced engineering fluency. Concurrency, memory behaviour, systems design, distributed correctness. You should be comfortable at the level where the abstraction leaks
- Lateral thinking. The willingness to ask whether the standard approach is actually the right one, and the rigour to be right about it more often than not
- Landscape awareness. You read about your field. You have opinions about where software is going. You can see an industry's potential before it becomes consensus
- Appetite for risk. We are building toward a niche that does not exist yet. That is the point. If that reads as instability rather than opportunity, this is the wrong role

The stack Chosen per architectural requirement, not per fashion.

Services and platform: BunJS, NestJS, Next.js, Deno — we pick the runtime that fits the workload rather than standardising for comfort.

Data: MongoDB and PostgreSQL, used for what each is actually good at. If you have a strong view on when document stores stop making sense, we want to hear it.

Core products: C++ and Java.



The parts of the system where latency and throughput are the product, not a feature of it.

You will not know all of this. Nobody does. We expect you to be strong in some of it and capable of getting strong in the rest quickly — and to tell us honestly which is which.

Terms

On-site, South Delhi. All hardware and software in person, in the room, with the team. Architecture arguments happen at a whiteboard. Debugging happens with two people at one machine.

Serious about ad-tech. This is not a side project, not a contract, not something to run alongside other work. We are early enough that half-commitment is worse than none.

Early-stage bootstrapping. No large safety net. Constraints on everything. In exchange: real ownership, decisions that are yours, and a system you helped design rather than inherited.

How we hire

Expect a long technical conversation, a problem you work through with us rather than for us, and a discussion of something you built where we will keep asking why until we hit the bottom of your reasoning.

We are looking for the bottom to be deep.

How to apply

Visit our website before you apply. Include your PIN code in your CV. When asked in the interview process, provide Flight No. AI 176 for ready reference.

Send your CV with a note covering:

1. The most technically difficult thing you have built or solved, and what made it difficult
2. A process you automated, and what it cost the organisation before you did
3. A widely accepted engineering practice you think is wrong, and your reasoning
4. What you think is structurally interesting — or structurally broken — about programmatic advertising

Applications without the note will not be reviewed.

📌 Systems Engineer — Founding Team (South Delhi)
🏢 Blowtrumpet
📍 South Delhi