Every role lives on Blowtrumpet

We are building the company you’ve always wanted to work at, with people you always wanted to work with.

Blowtrumpet’s [Work with us] page covers every discipline in the company. This page is narrower on purpose. It is for people who write software, and it is on the Vedoki property because Vedoki is where the engineering actually happens.

What “forward edge” means here, and what it does not

Every company claims a modern stack. Ours is deliberate rather than fashionable:

Node.js and TypeScript end to end. NestJS on the backend, Next.js on the frontends, containerised with Docker and OCI, orchestrated on infrastructure we run ourselves in India. Python where a specific workload earns it, and nowhere else. An AI-native core built in-house from the foundation rather than retrofitted onto something that was not designed for it.

That list is the easy part, and it is not the reason to come here. A framework choice is a Tuesday afternoon decision. The edge is in the problems:

Decisioning at scale with no viewer personal data. There is no ad call anywhere in our system — no tag, pixel, SDK, cookie, device identifier or viewer-side request. Creative is composited locally before broadcast. Work out what that removes from your toolkit, and you will understand why the measurement problems here have to be solved properly instead of looked up.

Insulation enforced in the schema. Our demand and supply sides are structurally separated: no price discovered on one side sets a price on the other, and no customer’s money is traceable to any supplier’s payment. That is enforced in service boundaries and data model, not in a policy document — because a rule that lives only in a policy survives until somebody is in a hurry.

Verification as a load-bearing system. Delivery is verified before anything is billed and before anybody is paid. Now consider verifying something that happened once, in real time, on somebody else’s machine, during a live video stream, cheaply enough to run on everything.

Transparent abstraction. Complexity gets managed by the system while the underlying behaviour stays observable and controllable to whoever is accountable for it. The design work is deciding exactly which seams stay visible, and to whom.

Full tenant siloing. No tenant’s data, raw or derived, reaches another. Work through what that rules out — including several products that would otherwise be obvious — and you have most of our architecture.

A reward system that is not a payment instrument. Keys, points, experience, reputation and levels are first-class domain concepts, strictly non-financial, not convertible, not transferable. Designing motivation without accidentally building currency is a real constraint problem.

The [learning resource](/learn) covers all of this in the open, in more depth, with nothing asked in return. Read it before you talk to us. Candidates who have are obvious within ten minutes, and it works in their favour.

How we think about engineering

Never resolve uncertainty by inventing an answer — open questions go on a register and get decided properly. A recommendation is not a decision until it is adopted. One home for every document. Stable identifiers that are never renumbered. Build-time enforcement of the rules that matter, because a rule nobody *can* break is worth more than a rule everybody agrees with.

Small teams, wide remits. You will work across more of the stack here than you would anywhere with a bigger org chart, and you will work directly with the people making the decisions rather than through three layers of coordination.

Campuses and institutes

HFW — Hire For Work, Blowtrumpet’s community initiative — runs verified campus communities at IIT Delhi, DTU, NSUT, IIIT-Delhi, BITS Pilani, IGDTUW and NIT Delhi. The campus restriction is the whole reason the opportunities posted in them are real.

What those communities are: a place to argue about the problem space with people working on it, early sight of apprenticeships, fellowships and internships, scheduled mentorship on your own work, and visibility for work you actually did.

What they are not: a back channel. Nothing in HFW is confidential, we do not publish interview questions, and an ambassador cannot get you a job.

We are open to formal collaboration with engineering departments and placement offices — joint projects, problem statements for capstone work, guest teaching, and research under [State of Ads]. If you run a programme and the problem space fits what your students should be learning, write to careers@blowtrumpet.com.

The Sprint Fellowship

Twelve weeks. Live projects from the first week. Mentorship from founders and domain experts. Certification and recognition for strong performance, and a genuine route into a full-time role.

The format is borrowed deliberately. The best engineering schools in the world do not teach practice through lectures — they use co-operative placements, practicums, studios and residencies where the student does real work, under supervision, and is assessed on what they produced. We built the fellowship on that model rather than on the internship model most companies run, where a student is handed a disconnected side project and a certificate at the end.

What that means in practice:

Week one	You are on a live project with real constraints, not a sandbox
Throughout	A named mentor, scheduled, not “available if you need anything”
Reviews	Your work is reviewed the way everyone’s work is reviewed
Writing	You write up what you built, and we publish the good ones
Ending	An assessment of what you actually produced, and a decision about a full-time role

All-round, because engineering is not only the code. You will leave able to explain a technical decision to somebody who does not share your vocabulary, hold an argument about your own work without taking it personally, write something a stranger can follow, read a requirement and find the question nobody asked, and work inside constraints you did not choose. Those are the things that separate people five years in, and almost nobody is taught them deliberately.

It is paid. Where the work is substantial enough to be work, it is paid, and that is agreed in writing before you start.

Being honest about how open this is

The cohort is small, because mentorship that is actually available does not scale. Most people who apply will not get in, and that has more to do with how few of us there are than with them. Pretending otherwise would be dishonest.

So here is what is open to everybody, with no application and no fee:

• The [learning resource](/learn) — the full problem space, free, no sign-up
• The [HFW community](/hfw) on Discord and the discipline-based WhatsApp groups
• The campus communities, if you are a verified student or alumnus of one of those seven
• [State of Ads](https://stateofads.com) research, published whatever it finds
• Writing for us through [Contribute](/contribute), which is read by a person

Several people now working here came through those routes rather than through a form. That is the intended path, not a happy accident.

How we hire

Everything runs through HFW on Discord. Not because it is fashionable, but because the people we want to hire are already in communities and not in an applicant tracking system. Openings are posted there and applications come back there.

We ask for a Statement of Purpose. What draws you to this work, when you started doing whatever you do, where you want to be in three to five years, and how this fits. It is not a formality — it is the part that gets read first, and a good one has got people interviews their CV would not have.

We do not ask for marks, percentile, backlog history, a photograph, your family’s details, or what you are currently paid. If a form ever asks you for those, it is a mistake and we want to know.

The process. A conversation rather than a panel. Then something real — a brief or a problem with actual constraints, scoped to a few hours and not a free weekend. Then a conversation about what you did and why.

Three ways in. An apprenticeship if you are learning the craft and want it taught properly. The Sprint Fellowship if you are early career and want the immersive version. An internship if you are studying and want scoped work with an owner and a deadline.

Two things you should know before applying

Vedoki is internal, so some of your best work here will not be public. There is no public API, no self-service tier and no integration surface, and that is deliberate rather than a stage we have not reached. If a public portfolio matters to you — and it reasonably might, early in a career — say so early. We will deliberately route a share of your work to things you can show: writing, open problem statements, State of Ads research, conference talks.

We are small and in closed testing. We hire slowly, we do not always have an opening in the area you want, and timing matters more than it should. If you do not hear back it is more likely to be about us than about you. If it has been a while, write again — that is not rude.

Where to write

Engineering roles	careers@blowtrumpet.com
Sprint Fellowship	fellowship@blowtrumpet.com
Campus communities and HFW	hfw@blowtrumpet.com
Institutional collaboration	careers@blowtrumpet.com
Account or sign-in problems	access@vedoki.com

[Join HFW on Discord →] · [Open the learning resource] · [Work with us at Blowtrumpet]

*Vedoki is the internal intelligence platform of Blowtrumpet Technologies, South Delhi. All hiring, reviews and HR functions are managed by Blowtrumpet. In closed testing.*