What you need to know
Most AI-engineer job searches fail for the same reason: they are run as a lottery. You spot a role, fire off an application into a portal, and wait. Nothing comes back, so you fire off ten more. There is no memory of what you sent, no sense of what is working, and no way to tell whether the silence means your positioning is weak, your targeting is wrong, or your proof of work is invisible. It feels like effort, but it is really just noise, and noise does not compound.
The people who land good AI roles quickly tend to run their search as a system. They borrow the one discipline that every sales team already knows works: treat the whole thing as a pipeline. There are defined stages a candidate moves through — Positioning, Sourcing, Outreach, Interviews, Offer — and every one of them has a conversion rate you can measure and improve. A tracker holds the state so nothing falls through the cracks. A weekly cadence keeps the top of the funnel full. And a handful of ratios tell you, without guessing, exactly where your search is leaking so you can fix that stage rather than flailing at all of them.
This guide is the end-to-end operating system that ties the pieces together. It is deliberately orthogonal to the single-topic careers guides we publish — the ones on your resume and the ATS screen, cold outreach, your LinkedIn recruiter visibility and your proof-of-work portfolio. Each of those is a deep-dive into one stage. This is the machine those parts bolt into. We will walk the five stages in order, put real numbers on the funnel, hand you a tracker schema you can paste into a spreadsheet or Notion this afternoon, and finish on the flywheel that quietly makes the whole thing easier over time: being discoverable enough that the best opportunities start coming to you.
Your search is a pipeline, not a lottery
A lottery has one lever — buy more tickets — and no feedback. A pipeline has many levers and constant feedback. That single shift in framing is worth more than any resume tweak, because it changes what you do when things are not working. In a lottery you just apply harder. In a pipeline you look at where candidates are dropping out and you fix that specific joint.
Picture the funnel the way a customer-relationship-management tool would. At the top sits a wide pool of companies you could plausibly work for. They move rightward through your process one stage at a time, and at every boundary some fall away — that is normal and expected. Your job is not to prevent every drop-off; it is to keep the shape of the funnel healthy and to keep enough volume entering the top that a healthy shape still produces offers at the bottom. The five stages are these:
- Positioning — deciding what you are, in one sentence, and assembling the proof that makes the claim credible. Everything downstream inherits this.
- Sourcing — building and constantly refilling a target list of companies and specific people worth reaching, across India, the UK and remote-global.
- Outreach — a repeatable weekly cadence of first touches and follow-ups that reference your proof of work rather than begging for a look.
- Interviews — the calls, technical loops and onsites, where preparation and signal turn conversations into advancement.
- Offer — negotiation and close, and the quiet leverage that comes from having more than one live conversation at once.
Two things make this a system rather than a metaphor. First, state is written down — a company is always at exactly one stage, with a last-touch date and a next action. Second, the boundaries between stages are measured, so you know your conversion at each joint. Get those two habits in place and the search stops being a source of dread and starts being a dashboard you nudge a little every day.
Stage 1 — Positioning
Positioning is the highest-leverage stage because every later stage inherits it. If your positioning is muddy, your outreach is generic, your interviews wander, and recruiters who glance at you cannot slot you into a role. Positioning is not your CV and it is not a list of the frameworks you have touched. It is the single, memorable claim that all of those exist to support — the answer to "what are you, in one line, and why should this specific team believe it?"
Start by picking a lane. The AI-engineering market has sorted itself into a handful of recognisable ones, and choosing among them is not limiting — it is what makes you legible. The four that hire hardest right now are:
- Agents — building systems that plan, call tools and act, including the orchestration, memory and guardrails that make them reliable in production.
- Evals — measuring model and system quality: harnesses, graders, offline and online evaluation, and the judgement to know what "good" even means for a given task.
- Infra — the serving, inference optimisation, retrieval and data plumbing that make models fast, cheap and dependable at scale.
- Forward-deployed engineering (FDE) — sitting with customers, shaping their problem into something an AI system can solve, and shipping it end to end. Part engineer, part solutions architect.
Pick one as your primary. You can be adjacent to a second — an agents engineer who is strong on evals is a lovely combination — but lead with one, because "I do a bit of everything" is not a position, it is a shrug. Then write your one-line pitch: role plus lane plus the proof, in a sentence a busy person remembers. Something like "AI engineer specialising in agent reliability — I built the eval harness and guardrails for a production support agent handling thousands of tickets a week." Notice the shape: what you are, the lane, and a concrete piece of evidence in the same breath.
That evidence is the third leg, and it is where most positioning collapses. A claim with no visible proof is just an assertion. The proof might be a shipped feature, an open-source project, a technical write-up, a benchmark you ran, or a demo someone can click. Whatever it is, it needs a canonical, linkable home so that your pitch, your outreach and your CV all point at the same place. This is precisely what a Verified Builder profile is built to be: one durable URL that states your lane, carries your one-line pitch, and links your proof of work, so every downstream touchpoint resolves to the same credible page rather than a scatter of half-updated links. Get the deep mechanics of that evidence layer from our proof-of-work portfolio guide; the point here is that positioning without a home to point at leaks value at every later stage.
Write your one-line pitch, then read it aloud to a friend and ask them to repeat it back an hour later. If they can, it is sharp enough to survive a recruiter's ten-second glance. If they mangle it into "you do AI stuff", you have named a topic, not taken a position — cut it down until one lane and one proof point are all that remain.
Stage 2 — Sourcing
Sourcing is building the list of who you will reach, and then never letting it run dry. A pipeline with an empty top produces nothing a few weeks later, so this stage is not a one-off exercise but a standing weekly habit. The aim is a living target list of companies and, crucially, specific people at those companies — a hiring manager, a team lead, an engineer whose work you admire — because you reach people, not portals.
Segment your list by type, because each behaves differently. Early-stage startups hire fast, care most about proof you can ship, and often have a founder you can reach directly. Scale-ups have real teams and defined roles, so your lane matters more and the process is a touch more formal. Labs and research-heavy shops weight depth and publications, and move more deliberately. Knowing which bucket a target sits in tells you how to pitch and how much patience to budget.
Layer geography on top. If you are in India, the dense home turf is the Bengaluru, Pune, Hyderabad and Gurugram belt — a deep pool of AI-first startups plus the global capability centres that now run serious engineering, not just support. If you are in the UK, London anchors the scene, with Cambridge, Oxford and Manchester adding research-heavy and scale-up clusters. Remote-global roles widen the funnel again, but they are more competitive and often carry time-zone or visa considerations, so treat them as a deliberate second lane rather than the entire plan. Your positioning and your tracker work identically across all three; only the density and the norms change.
Finally, tag every target as warm or cold, because the channel changes everything. A warm path — a former colleague, someone from your university, a person you met at a meetup, a maintainer whose project you have contributed to — converts far better than a cold one, because the interest does not start from zero. Cold outreach still works and you will do plenty of it, but always ask first whether a warm route exists, even a second-degree one. Building and surfacing those warm paths is largely a visibility problem, which is exactly what our LinkedIn recruiter-search playbook is about: being findable so that "cold" contacts already half-know who you are before you message them.
Do not confuse sourcing with applying. Dumping fifty roles from a job board into your tracker feels productive, but a job-board listing is a portal, not a person, and it usually means you are entering the funnel at its most crowded point. A sourced target has a named human and a reason you are reaching them. If a row in your tracker has no person and no angle, it is not sourced yet — it is a bookmark.
Stage 3 — Outreach cadence
Outreach is where the pipeline either flows or stalls, and the thing that keeps it flowing is cadence — a repeatable weekly rhythm rather than sporadic bursts of motivation. Sporadic outreach produces a sawtooth funnel: a flurry, then silence, then panic. A steady cadence produces a smooth one, where new conversations start every week and the follow-ups take care of the rest.
A cadence that is sustainable alongside a full-time job looks roughly like this. Each week, add eight to twelve new, well-researched targets and send each a tailored first touch. Then run a disciplined follow-up schedule on everyone already in flight: a first follow-up around three to four working days after an unanswered first touch, a second a week after that, and then let it rest. Two unanswered follow-ups is usually the polite ceiling; a third rarely helps and can cost you goodwill. Treat these as rules of thumb, not laws — the numbers matter far less than the fact that you have a rhythm you actually keep.
The content of the touch is what separates a reply rate you are proud of from silence. Every first message should do three things: show you have done a minute of homework on their actual product or problem, connect that to your positioning in one line, and point at a specific piece of proof. "I saw you are building X; I have shipped the closest thing to that, here is the two-minute version" beats "I am a passionate AI engineer seeking opportunities" every single time. The proof link matters enormously here, and it is another reason a single canonical profile pays off — one durable URL you can drop into any message, that always shows your current best work. The full templates, subject lines and timing live in our dedicated cold-outreach guide; the cadence is the machine, and that guide is the ammunition.
"When I stopped applying and started running a pipeline, the change was almost embarrassing. I had a spreadsheet with a stage column and a next-action column, I did my eight new targets and my follow-ups every Monday and Thursday, and I looked at my reply rate every week. The moment I could see that my outreach-to-reply was fine but my reply-to-call was terrible, I knew the problem was my first call, not my messaging — and I fixed the right thing. You cannot fix a funnel you cannot see."
— Rishi Kora, Verified Builder · London, United KingdomEvery article here is written by a Verified Builder. Want your name on the next one?
AI Tech Connect lists AI engineers, founders and researchers across India and the UK — and the people hiring browse it to find them. Adding your profile is free.
Become a Verified Builder →Stage 4 — Conversion metrics
Here is the part that turns a to-do list into an operating system: the numbers. Four conversion ratios describe the health of your search, and each one, when it is low, points at a different and specific fix. The values below are illustrative rules of thumb for a warm-led search by a competent engineer — not cited data, and not targets to obsess over. What matters is watching your own ratios move and reading what a low one is telling you.
| Funnel joint | Rough healthy range | What a low number is telling you |
|---|---|---|
| Outreach → reply | ~25–50% (warm), lower for cold | Your targeting or your message is off. Either you are reaching the wrong people, or your first touch reads as generic. Tighten the homework and the proof link before you send more. |
| Reply → first call | ~40–60% | Interest exists but you are not converting it to time. Usually a positioning problem — they replied out of politeness but do not see a clear fit. Sharpen the one-line pitch. |
| Call → onsite / loop | ~30–50% | Your first call is not landing. Either the role is a genuine mismatch, or you are not conveying signal in the conversation. Prepare the call like an interview, not a chat. |
| Onsite → offer | ~15–30% | The technical or system-design loop is where you are dropping. This is a skills-and-preparation fix, not a funnel fix — drill the specific formats each company uses. |
Read the table as a diagnostic, top to bottom. If almost nobody replies, do not touch your interview prep — the problem is at the very top, in targeting and messaging, and no amount of coding practice will help. If people reply warmly but few take a call, your positioning is fuzzy: they are curious but cannot see the role you fit. If calls do not become onsites, work on how you show up in that first conversation. And if you reach plenty of onsites but the offers do not come, the leak is squarely in your technical performance, and that is a preparation problem you can grind down deliberately. The beauty of measuring is that it stops you from fixing the wrong stage — the single most common way a search wastes months.
One more number is worth watching across the whole funnel: how many live conversations you have running at once. A pipeline with a single company at the offer stage gives you no leverage and a lot of anxiety. Three or four live at similar stages changes both your negotiating position and your state of mind — which is why keeping the top of the funnel full through steady sourcing and outreach pays off precisely when it matters most, at the end.
The tracker
None of this works without a single source of truth, and it does not need to be fancy. A spreadsheet or a Notion board is perfect; the tool matters far less than the discipline of updating it. The one rule is that every company sits at exactly one stage at any moment, and every row has a next action with a date. If a row has no next action, it is either dead — archive it — or you are about to let it rot. Here is a schema that has everything you need and nothing you do not:
| Column | What goes in it |
|---|---|
| Company | The organisation, plus a one-word type tag: startup, scale-up or lab. |
| Role / contact | The specific role and, more importantly, the named person you are actually reaching — not "careers@". |
| Stage | Exactly one of: Sourced, Outreach, Replied, Call, Onsite, Offer, Closed. This drives the whole funnel view. |
| Last touch | The date of your most recent contact. This is what tells you a follow-up is due. |
| Next action | The single next thing you must do, with a date. "Follow up 28 Jul", "Prep system-design loop", "Send thank-you". |
| Source | How this entered the pipeline: warm intro, cold email, referral, event, inbound. Lets you see which channels actually convert. |
| Notes | Context that makes your next touch personal: their product, the person's background, what was said on the last call. |
Two habits make the tracker earn its keep. First, sort by next-action date and work the top of that list each session, so nothing overdue slips. Second, once a week, tally how many rows sit at each stage and compute the ratios between adjacent stages — that is your funnel health check, and it takes five minutes. The Source column quietly does something powerful over time: it shows you which channels convert, and warm and inbound sources almost always win, which is the whole argument for the flywheel we turn to next.
The visibility flywheel
Everything so far has been outbound — you finding companies and reaching them. It works, and you should run it hard. But there is a quieter, compounding engine underneath a good search, and it runs the other way: inbound. Inbound is companies finding you, and it converts better than outbound for a simple reason — when a recruiter or founder reaches out, the interest starts on their side of the table. You are no longer persuading; you are choosing.
Inbound does not happen by wishing. It happens because you are discoverable — because when someone searches for an engineer with your exact lane and proof, you appear. This is the flywheel: strong positioning makes you legible, a public profile makes you findable, being found brings inbound conversations, those conversations produce shipped work and social proof, and that proof strengthens your positioning again. Each turn makes the next easier, and the whole thing runs whether or not you are actively job-hunting that week. The engineers who always seem to have options are rarely applying more — they are more discoverable.
The lever you control is your discoverable home. A Verified Builder profile on AI Tech Connect is built to be exactly the page a recruiter or founder lands on when they search for someone like you: your lane, your one-line pitch and your proof of work, verified and in one durable place. It is the same URL your outbound outreach points at, so your outbound and inbound reinforce each other rather than living in separate worlds. Combine it with a sharp LinkedIn presence — our recruiter-search playbook covers that surface — and a CV that clears the machines, which our resume-and-ATS guide handles, and you are findable across every place the people hiring actually look.
Stop chasing. Get found — and claim the Founding Builder badge while it lasts.
Inbound beats outbound, and a discoverable profile is how inbound starts. Early profiles carry the Founding Builder badge — a permanent marker that you were here first — and those spots are limited. Claim yours before they are gone.
Claim your Founding Builder profile →Putting it together
An AI-engineer job search does not have to feel like shouting into a void. Treat it as an operating system: a pipeline with five stages, a tracker that holds the state, a weekly cadence that keeps the top full, and four conversion ratios that tell you exactly which joint to fix when things stall. Start at positioning — pick your lane, write the one-line pitch, and give it a canonical home. Source real people, not portals, across your home market and beyond. Run outreach as a rhythm, not a mood. Measure the funnel and fix the stage that is actually leaking. And underneath all of it, build the visibility flywheel so the best opportunities begin to find you. Do that in Bengaluru or in London, and the search stops being a lottery and becomes something you run — and win.