AI Career Transition for Working IT Professionals (2026)

Between 2023 and 2026, AI hiring in India shifted from credential-shaped to evidence-shaped. The 2023 proxy — a certificate — failed, because too many certified people couldn't ship. The demand side is not in doubt: nasscom's Strategic Review 2026 describes CY25 as the year Indian tech moved "from AI experimentation to industrialisation", and Naukri's JobSpeak index has recorded AI/ML as the fastest-growing white-collar segment for two years running.

What replaced it is engineering evidence: has this person deployed something, can they debug retrieval failures, do they manage token cost and latency, do they know what happens when the model returns malformed JSON at 2 a.m. That is production discipline applied to a new component — what an employed IT professional has and a fresher doesn't.

Three tailwinds are real. Indian enterprises — banks, insurers, hospitals, retailers, manufacturers, IT services firms — bolt AI onto SAP, mainframes and old claims engines, so legacy-integration survivors beat Kaggle-only candidates. "AI + domain" hybrid roles are now a distinct hiring category — nasscom's read of India's AI talent inflection point is that the shortage is concentrated in applied, deployment-capable talent rather than in headcount. And the rising bar thinned the top of the applicant pool.

Now the conditions. Your advantage is latent, not active — it converts only when attached to AI-specific evidence; "8 years, Java, Spring Boot, Oracle" plus a certificate is screened out as fast as a fresher's identical certificate. A switcher discount on the first AI offer is common — negotiate scope and title over CTC, and expect to close the gap in one to two cycles. Adjacency does the rest: the further your role from the target, the longer the timeline.

The Indian AI job market split into three tiers during 2025–26. Choosing the wrong one costs a year, not a weekend.

CTC bands above are the author's editorial reads, cross-checked against public India bands on AmbitionBox, Levels.fyi and Payscale — check all three, plus our own AI engineer salary breakdown, for your city and years before you anchor on any number.

Read Tier 3 honestly: it needs a postgraduate programme, not evening study — Stanford HAI's AI Index tracks how concentrated that talent pool is and where its graduates go. Any course implying otherwise is selling a story.

The mechanism: the certificate wave didn't predict capability, so hiring moved to evidence verifiable in ninety seconds — a GitHub profile and a demo.

Synthesis from conversations with hiring managers, leads and recruiters across product companies, GCCs, startups and IT services AI practices. Ordering reflects my reading, not survey data.

1. 1A deployed system with a public demo — one that runs at a URL they can click, not the most sophisticated project.
2. 2A GitHub with genuine commit history. Incremental commits read as real work; one 5,000-line commit reads as a rewritten fork.
3. 3Ability to defend trade-offs. "Why chunk at 512 tokens?" "Why RAG instead of fine-tuning?" Builders answer in their own words; tutorial-followers recite.
4. 4Production instincts — cost per request, p95 latency, failure modes, monitoring, graceful degradation. Switchers outperform freshers here.
5. 5Domain and production experience, positioned rather than buried — proof you've shipped to real users in a domain they sell into.
6. 6Communication — explaining an AI system, its limits and evaluation to a non-technical stakeholder. Enterprise AI work is 40% stakeholder management.
7. 7The credential — last, only an HR-gate tick or tiebreaker.

Items 1–4 come from building, item 5 from rewriting your resume, item 6 from status calls you resented — and item 7 is where most people spend their money and their year.

Bands assume 8–15 hours a week alongside a full-time job, consistent over months. "Job-ready" means surviving a technical round; "time to offer" adds the search. Typical bands from tracked transitions, not promises.

Anyone promising an AI job in 90 days from a non-coding base is describing an outlier, not a plan. Many transitions run past these bands; some don't convert. Non-conversion rarely traces to age or aptitude — it traces to building or applying stopping. Those who kept doing both, even slowly, eventually landed.

An advertised "average placement CTC" is usually a survivor average over learners who completed and had an offer worth reporting — and a total CTC bundling variable pay, joining bonus and ESOP, not like-for-like against your fixed salary.

The second distortion is the switcher discount: a first AI role lands below what AI-native experience commands, closing within one to two cycles. Optimise for scope, team quality and title, not the last lakh.

The third is internal versus external economics. Internal moves bring a modest correction with near-zero risk, plus the resume line blocking you today; external switches carry the larger hike and the larger risk. Metro versus Tier-2 gaps persist, though remote roles have narrowed them. Before any negotiation, pull your own band from AmbitionBox, Levels.fyi and Payscale India — three independent reads beat one marketing banner.

Treat every row as a band, not a target — it moves with employer type, city, negotiation and evidence strength. These are the author's bands from tracked transitions, sanity-checked against the public aggregators linked above and against live postings on Naukri and LinkedIn Jobs; no row is a survey statistic.

Production paranoia. You've been paged at 3 a.m., so you assume things fail. With a non-deterministic, confidently wrong core component, that assumption is the whole discipline. Asked "what if the model returns invalid JSON," a fresher says "that shouldn't happen"; you describe your retry-with-repair path.

Estimation honesty. AI pilots are notorious for demos that never ship. "Retrieval quality needs three iterations and a labelled eval set before this is safe" beats promising a fortnight.

Working within constraints. Legacy systems, security reviews, procurement, data-residency rules, budget — enterprise AI lives inside exactly these, so fluency in them is the job, not baggage.

Communicating with non-engineers. Explaining a production incident to an account manager is the same muscle as explaining why the assistant hallucinated a policy number. Every hiring conversation named it as a scarcity.

For most engineering backgrounds the real gap is two things: LLM-specific engineering (model behaviour, retrieval design, agents, adaptation, evaluation, guardrails — months, not weekends), and public evidence a stranger can inspect without your explanation attached.

What is not in the gap is what courses spend most time on: programming, version control, HTTP, deployment, cloud, databases, testing. If a curriculum's first ten weeks are Python basics and you've written Java for five years, you're paying to be bored — and boredom is where dropout happens.

Some things on your resume have no destination in an AI role. Ticket-closure metrics and SLA-attainment percentages mean nothing outside your process. Tool-specific routines on legacy stacks don't travel. Manual-only process work with no automation has no equivalent. And years of experience as a standalone claim — "8 years in IT" — argues for nothing in an AI screen; it's context, valuable only attached to domain depth or engineering evidence.

These aren't defended, they're repositioned: "manual regression testing" becomes "test-case design and coverage reasoning," mapping to evaluation-set construction. Note the trap: seniority on an old stack can create salary expectations the first AI role won't meet. At ₹32 LPA leading a stack nobody hires for, the market may price your first AI role below that. Re-read the salary-reality section before interviewing, not after your first offer.

Role:

builds products on LLMs rather than training them. Work: prompt/output design, retrieval, tool calls, cost/latency control, evaluation. Demand: highest-volume AI title in Indian product firms, GCCs and services. Fits: backend/full-stack devs, data engineers, strong QA automation engineers. Bar: 3–5 deployed projects, retrieval fluency, defends architecture live. Band: ₹10–32 LPA. Growth: platform/architecture, agents or evaluation.

Role:

broader title — LLM work plus classical ML integration, data plumbing and deployment. Work: model integration, pipelines, APIs, ops. Demand: widely used, often interchangeable with GenAI Engineer; read the JD body. Fits: backend developers, data engineers, ambitious analysts — the standard route to becoming an AI engineer. Bar: as GenAI Engineer, sometimes more classical ML. Band: ₹10–30 LPA. Growth: specialised GenAI, ML engineering or platform work.

Role:

builds, trains and serves models — recommendations, forecasting, fraud, ranking — with modelling depth GenAI often skips. Work: feature engineering, training/validation, metrics, serving, retraining. Demand: steady, unglamorous; competition per posting often lower. Fits: data engineers, statistics-strong analysts, backend devs willing to do the maths. Bar: genuine ML fundamentals, one model deployed and monitored. Band: ₹12–34 LPA. Growth: senior ML engineer → platform or applied science.

Role:

owns the infrastructure and lifecycle around models — deployment, serving, versioning, monitoring, cost; for LLMs add prompt versioning, eval gates, token spend and provider failover. Work: pipelines, containers, GPUs/managed inference, observability, cost dashboards. Demand: persistently under-supplied in India. Fits: DevOps, SRE, cloud/platform engineers. Bar: infra depth plus model-layer literacy. Band: ₹14–35 LPA. Growth: AI platform engineering, infrastructure lead.

Role:

builds systems where an LLM plans, calls tools and executes multi-step work — increasingly multi-agent, with the Model Context Protocol (MCP) connecting models to tools and data. Work: tool design, planning loops, memory/state, guardrails, failure recovery, cost control on long runs. Demand: fastest-rising JD requirement, often folded into GenAI postings. Fits: backend developers, integration/workflow engineers, RPA specialists — start with AI agent building courses. Bar: one non-trivial deployed agent with real failure handling. Band: ₹12–34 LPA. Growth: agent platform work, AI architecture.

Role:

emerging 2026 role owning whether an AI system actually works: eval datasets, LLM-as-judge pipelines, regression suites, adversarial testing. Work: golden datasets, outcome-tied metrics, release gating, red-teaming against the OWASP Top 10 for LLM Applications. Demand: rising sharply as teams reach production and can't tell if a change helped. Fits: QA automation engineers above all, plus analysts and test architects. Bar: an evaluation harness you built, with numbers and a metric-validity argument. Band: ₹10–24 LPA, wide given the role's newness. Growth: AI quality lead, responsible-AI/governance.

QA professionals, read that card twice. Most testers compete head-on with developers for GenAI Engineer roles, where their background reads as a deficit. Approached as evaluation, that background is the qualification — the fastest-converting niche.

Role:

the data foundation under AI systems — ingestion, cleaning, chunking, embedding pipelines, vector stores, corpus freshness. Work: pipelines at scale, incremental re-indexing, quality monitoring, access control. Demand: steady; every serious RAG deployment finds a data problem, usually late. Fits: data engineers, ETL developers, database specialists. Bar: a production-shaped embedding pipeline with incremental updates and quality checks. Band: ₹12–30 LPA. Growth: AI/data platform leadership.

Role:

owns what gets built and why, including non-deterministic behaviour, evaluation criteria, acceptance thresholds and model cost as a unit economic. Work: discovery, scoping, eval criteria with engineering, expectation-setting on accuracy and cost. Demand: growing in product companies and GCCs; candidates who understand AI limits are scarce. Fits: PMs, senior BAs, tech leads moving to product. Bar: literacy deep enough to argue with engineers, one shipped feature, a spec with eval criteria. Band: ₹15–40 LPA. Growth: senior PM, AI product leadership.

Role:

client-facing Tier 1 role — finding use cases, scoping feasibility, designing the workflow around the model, managing adoption. Work: discovery workshops, feasibility assessment, solution design, vendor evaluation, change management. Demand: strong across IT services AI practices, consulting firms and enterprise adopters; domain depth outweighs coding. Fits: SAP/ERP/CRM consultants, BAs, delivery/pre-sales professionals — a route that works without writing code. Bar: credible AI literacy, one prototype or case study, strong scoping. Band: ₹8–24 LPA. Growth: AI practice lead, solution architecture, product.

In one paragraph:

a GenAI/LLM Engineer builds apps on existing models. An ML Engineer builds and serves models trained on your data. A Data Scientist answers business questions with statistics and analytics. An MLOps Engineer runs the infrastructure under all of it. Most 2026 Indian postings saying "AI Engineer" mean the first. Read responsibilities, not the title.

Adjacency is the single highest-leverage decision here — more than course, framework, or hours put in. It sets timeline, competition, and how much salary and seniority carries across. A Medium-adjacency route you find interesting beats a High-adjacency one abandoned in month three; motivation depletes fast after a nine-hour workday. A Stretch route chosen purely for salary has the highest failure rate — the gap is largest where the pull is weakest.

Standalone "prompt engineer" postings. The role peaked as a distinct title, now largely absorbed into engineering and product work. Many remaining postings are underpaid and hard to move out of. Spot it: no deployment, no evaluation, no systems responsibility in the JD.

"AI analyst" roles that are relabelled reporting jobs. If responsibilities are dashboards, MIS reports and Excel plus one bullet on "exploring AI tools," it's a BI role in costume — won't read as AI experience later.

Annotation-heavy roles marketed as AI careers. Data labelling and RLHF annotation are legitimate but usually low-paid, high-volume, and rarely build engineering evidence.

"AI support" roles with no growth path. Supporting an AI product isn't building one. Ask what share is triage versus implementation, and who owns fixes. If "we escalate everything," price and plan it as a support role.

Ten layers, in sequence, each with an IT-pro head start and an interview note.

Layer 0 — Programming and data foundations. Python, Git, SQL, JSON, basic Linux, HTTP/APIs — write a non-trivial program unaided. Head start: developers, DevOps, data engineers largely have this; manual QA, support and sysadmins usually don't, and this is their real gate. Interview: expect live coding.

Layer 1 — ML fundamentals, scoped. Supervised vs unsupervised learning, train/validation/test discipline, overfitting, metrics (precision, recall, F1, ROC-AUC), and when a classical model beats an LLM. Andrew Ng's Machine Learning Specialization covers this layer at exactly the right depth, free to audit. Head start: analysts have the statistical intuition. Interview: "why not just an LLM?" is a filter question.

Layer 2 — How LLMs actually work. Tokens, embeddings, attention/transformers intuitively, context windows, temperature/sampling, and why hallucination happens mechanically. Head start: none. Interview: "a probabilistic next-token predictor without grounding" is the right start.

Layer 3 — Applied LLM engineering. Provider APIs, schema-validated outputs, tool calling, prompting patterns, retries/repair, caching, streaming, cost/latency control. Head start: backend developers move fastest. Interview: "how did you make output reliably parseable?" separates builders from tutorial-followers.

Layer 4 — RAG. Chunking, embedding models, vector databases, hybrid search, re-ranking, citation/grounding, retrieval evaluation. The RAG survey literature and Anthropic's contextual retrieval write-up are the two best free starting points. The most-requested competency in 2026 Indian GenAI JDs. Head start: data engineers, search-adjacent developers. Interview: deep questions on chunk size and measured retrieval improvement.

Layer 5 — Agents and agentic systems. Tool use, planning loops, memory/state, multi-agent orchestration, and the framework landscape — LangGraph, CrewAI, AutoGen, the OpenAI Agents SDK [verify current] — plus MCP as an integration standard. Head start: integration/workflow engineers. Interview: "what did your agent do when a tool failed?" reveals deployed versus demoed.

Layer 6 — Fine-tuning and adaptation. Above all the decision framework: prompting vs RAG vs fine-tuning vs a different model, and why. Then supervised fine-tuning, LoRA/QLoRA (parameter-efficient tuning, implemented in Hugging Face's PEFT), dataset construction, evaluation against base. Head start: none. Interview: decision questions outnumber implementation ones.

Layer 7 — Deployment, MLOps and production. FastAPI or equivalent, Docker, cloud deployment, secrets management, logging/tracing (LangSmith, MLflow), monitoring, cost tracking, rollback. Head start: DevOps and SRE readers own this layer outright. Interview: the demo URL is evidence; questions probe scale failures.

Layer 8 — Evaluation, guardrails and responsible AI. Evaluation datasets/pipelines (Ragas, DeepEval), LLM-as-judge and its limits, prompt regression testing, prompt-injection defence, PII handling/redaction under India's Digital Personal Data Protection Act, 2023, BFSI/healthcare compliance in India. Head start: QA readers own the mindset. Interview: "how do you know it got better?" is the question most fail.

Layer 9 — Portfolio, communication and interview craft. Repository presentation, architecture write-ups, project defence under questioning, switch narrative, negotiation. Head start: leads and consultants already explain well. Interview: this layer is the interview.

Two capabilities per layer. Count only what you could demonstrate today, unprepared. Be strict.

1. 1I can write a non-trivial Python program without following a tutorial.
2. 2I use Git branches, resolve merge conflicts, and can write a clean commit history.
3. 3I can explain overfitting and choose an appropriate evaluation metric for a given problem.
4. 4I can say when a classical ML model is the better choice than an LLM.
5. 5I can explain tokens, embeddings and context windows in plain language.
6. 6I can explain mechanically why an LLM hallucinates and what reduces it.
7. 7I have called an LLM provider API and enforced a validated structured output.
8. 8I have implemented tool / function calling with error handling.
9. 9I have implemented retrieval over my own documents end to end.
10. 10I have compared two chunking or retrieval strategies using measured results.
11. 11I have built an agent that uses at least two tools and handles a tool failure.
12. 12I can explain what a multi-agent orchestration framework gives me over a plain loop.
13. 13I can decide between prompting, RAG and fine-tuning for a stated use case and defend it.
14. 14I understand LoRA/QLoRA well enough to scope a fine-tuning task and its dataset needs.
15. 15I have built and deployed a REST API that others can call.
16. 16I have containerised an application and deployed it to a cloud environment.
17. 17I have built an evaluation harness with a golden dataset and repeatable scoring.
18. 18I have tested an AI system against prompt injection or adversarial input.
19. 19I have a public repository with genuine incremental commit history and a real README.
20. 20I can present an AI system's design, trade-offs and limits to a non-technical stakeholder.

Your score routes your roadmap. 0–6 → 12-month plan. 7–13 → 6-month plan. 14–20 → 90-day sprint. Note your number before continuing.

With ten hours a week, allocation discipline beats ambition.

Exhaustive classical-ML depth for GenAI roles — Layer 1's scoped version suffices. Deep-learning theory from first principles (deriving neural network maths by hand) for Tier 2 roles; intuition beats derivation. Building a transformer from scratch — good exercise, but no portfolio value; defer it. DSA grinding beyond moderate screening level — AI loops lean toward system design and project defence. Tableau/Power BI modules bundled into "AI" curricula — common padding.

The rule: before a weekend on anything, find three real JDs asking for it on Naukri or LinkedIn Jobs. If you can't, defer it.

Edge:

API design, systems thinking, deployment, debugging — Layers 0, 3, 7 in hand. Best target: GenAI/LLM Engineer; alternate, AI Agent Developer. Gap: Layers 2–6, evaluation, public evidence. Projects: a production-shaped LLM app with validated outputs; a RAG service with citations and a scored evaluation harness; a tool-using agent with failure handling and cost logging. Repositioning: "Backend engineer (N yrs) building production LLM systems." Internal move: volunteer for your org's GenAI pilot. Timeline: 3–5 months to job-ready, 5–9 to offer. Trap: staying in tutorial mode instead of shipping imperfect work publicly.

Frontend developers: same route via full-stack framing — add backend and deployment depth first. Your niche edge is AI interface work: streaming, citation display and human-in-the-loop UIs are badly built almost everywhere.

Edge:

Layer 7 is yours already — containers, pipelines, observability, cost. Best target: MLOps/LLMOps Engineer; alternate, AI infrastructure. Gap: Layers 2–5 plus evaluation literacy. Projects: a self-hosted LLM served with monitoring and a cost dashboard; CI/CD for a RAG app with evaluation gates; a GPU cost-optimisation study with before/after numbers. Credential worth having: one cloud AI certification — AWS Certified Machine Learning Engineer – Associate, Azure AI Engineer Associate or Google Professional Machine Learning Engineer — because it is often the literal keyword the JD screens on. Repositioning: "SRE (N yrs) specialising in LLM serving and inference cost optimisation." Internal move: own deployment and monitoring of any AI pilot. Timeline: 3–6 months to job-ready, 5–10 to offer. Trap: assuming infra alone suffices — interviewers probe the model layer.

Edge:

test design, harness construction, regression discipline, adversarial thinking — the exact mental model AI evaluation needs. Best target: AI Evaluation Engineer; alternate, GenAI Engineer. Gap: Layers 2–5, especially retrieval and agent behaviour. Projects: an evaluation harness with golden datasets and reported metric agreement; a CI prompt-regression suite that fails builds on quality drop; an adversarial/prompt-injection suite against your own RAG app. Repositioning: "Automation engineer (N yrs) building evaluation and regression systems for LLM applications." Internal move: propose owning quality for any AI feature — nobody currently does. Timeline: 4–7 months to job-ready, 7–12 to offer. Trap: undervaluing your niche and competing as a generic developer.

Be honest first: this is a two-stage transition. Stage one is Layer 0 — real programming, three to five months, Python/Git/SQL, the gate for anyone starting from a non-programming base. Stage two follows the QA-automation playbook above. Best target: AI Evaluation/QA; alternate, a Tier 1 role if you'd rather not code. Projects: a small automation utility for a real work problem (no employer data in the repo); a scripted test suite for a public API; a basic evaluation harness. Repositioning: "Test engineer (N yrs) transitioning to AI evaluation." Internal move: ask to be the tester on any AI pilot. Timeline: 10–15 months to job-ready, 12–20 to offer. Trap: certificate-collecting instead of learning to code.

Edge:

SQL fluency, data intuition, business framing, comfort with metrics. Best target: applied AI/ML Engineer; alternate, AI Product Analyst (Tier 1). Gap: engineering depth and deployment — APIs, containers, Layer 7. Projects: a RAG system over business documents with a metrics dashboard; an ML model deployed as a monitored API, not a notebook; an LLM analytics assistant turning questions into validated queries. Repositioning: "Analyst (N yrs) building and deploying AI systems." Internal move: propose an AI assistant over your own reporting layer. Timeline: 5–8 months to job-ready, 8–14 to offer. Trap: staying in notebooks — nothing counts till it runs outside your laptop.

Edge:

pipelines, scale, orchestration, data quality at volume. Best target: AI Data/Platform Engineer; alternate, GenAI Engineer. Gap: embedding/retrieval patterns, agent systems, evaluation. Projects: a production embedding pipeline with incremental re-indexing; a multi-source retrieval system with hybrid search and permission-aware filtering; drift-alerted data-quality monitoring for a RAG corpus. Repositioning: "Data engineer (N yrs) building retrieval and embedding infrastructure for production AI." Internal move: own the data layer of any GenAI initiative — it fails first. Timeline: 4–6 months to job-ready, 6–11 to offer. Trap: treating GenAI as "just another pipeline," skipping evaluation.

Edge:

enterprise domain depth nobody can shortcut — an engineer can learn RAG in two months but not how a procure-to-pay cycle breaks in an Indian manufacturer. Best target: AI Solutions Consultant; alternate, platform-embedded AI roles [verify current]. Gap: technical credibility to back the domain story, plus one built artefact. Projects: an AI copilot prototype for a domain workflow you know cold; a RAG system over module documentation with evaluation; an automation agent for a routine process with a benefit estimate. Repositioning: "ERP consultant (N yrs) designing and prototyping AI solutions for [domain] workflows." Internal move: your firm's AI practice needs domain consultants more than another engineer [verify current]. Timeline: 5–9 months to job-ready, 8–14 to offer. Trap: waiting for your platform to "add AI for you" instead of building your case.

Edge:

requirements discipline, stakeholder management, delivery, prioritisation. Best target: AI Product Manager or AI Business Analyst (Tier 1). Gap: AI literacy deep enough to scope, evaluate and challenge engineers — not to build. Know why a RAG system returns the wrong clause, not how to implement re-ranking. Projects: an AI feature spec with evaluation criteria, acceptance thresholds and a cost model; a working no-code/low-code prototype; a sanitised AI-adoption case study. Repositioning: "Product manager (N yrs) scoping AI features — evaluation criteria, cost modelling and adoption." Internal move: volunteer to run the AI pilot nobody wants. Timeline: 3–6 months to job-ready, 6–11 to offer. Trap: drowning in code-first curricula built for engineers, concluding you're "not technical enough."

The decision comes before the plan. Fork one: hands-on GenAI engineering — six to nine months of IC building, often with a title that won't flatter you for a year. Fork two: AI engineering leadership — literacy for architecture and vendor calls, delivery credibility, one real AI initiative led end to end. Edge: architecture judgement, delivery record, stakeholder trust. Gap: fork one needs everything built by you; fork two needs one genuine AI delivery narrated in detail. Projects: fork one follows the backend playbook; fork two substitutes a led initiative, an architecture decision record and a cost/risk assessment. Repositioning: "Engineering leader (N yrs) who has delivered production AI systems — [specific initiative]." Timeline: 4–8 months to job-ready, 7–14 to offer. Trap: the half-commitment — too senior to build, too shallow to lead AI credibly.

The shape is identical across all ten: pick the adjacent role, close the specific gap, produce inspectable evidence, reposition your experience, and run both tracks in parallel. Between two playbooks, run the higher-adjacency one, borrowing the capstone from the other.

Your deliverable here is not knowledge. It is a body of evidence a hiring manager can inspect in four minutes and then want to interrogate for forty-five. Knowledge that produces no inspectable artefact is invisible to hiring, however real it is — the hardest thing for studious people to accept, because studying feels like progress and shipping feels like exposure.

Project 6 carries disproportionate weight. Hiring managers recognise cohort-template projects instantly — when forty candidates from one programme submit the same movie-recommendation RAG bot, the projects stop being evidence and become noise. A capstone anchored in the domain you have worked in is unforgeable by anyone without your background, and converts "did a course" into "already solves problems I have": a test-case generation assistant from a QA engineer, a reconciliation-exception triage agent from a banking engineer, a purchase-order anomaly copilot from an SAP consultant. Build it on public or synthetic data, never on your employer's.

• Deployed beats notebook, every time. A public URL — Hugging Face Spaces, Streamlit Community Cloud and Render all have free tiers that clear this bar — or, where hosting cost or auth makes that impractical, a two-minute demo video. A notebook is coursework; a running service is evidence.
• README standard. Every repository gets: the problem in two sentences, an architecture diagram (a simple boxes-and-arrows image is fine), key decisions and the trade-offs behind them, evaluation results with actual numbers, how to run it locally, and what you would improve with more time. That last section signals judgement more than any other line in the repo.
• Commit-history authenticity. Build in public increments over weeks. A single "initial commit" containing 5,000 lines reads as copied, and reviewers check.
• GitHub hygiene. Remove or archive tutorial forks and abandoned experiments. Pin the four to six real repositories. Make your profile README a portfolio index with one line and one link per project.
• A short write-up per project — a LinkedIn post or a blog entry explaining what you built, what broke and what you measured. Optional, but disproportionately high-leverage: it is how recruiters discover you rather than the reverse, and it doubles as defence rehearsal.
• Confidentiality, once more: never employer data, code, documents or IP. Not in the repo, not in the demo, not in the screenshot.

Here is exactly what happens when a hiring manager opens your portfolio link, and what fails at each step. Second 0–20: they look at your pinned repositories. If there are eleven repos with no pins and three are forks named after tutorials, they close the tab. Second 20–60: they open the most relevant repo and skim the README. No problem statement, no architecture, no numbers — the tab closes. Minute 1–2: they look at the architecture diagram and the decisions section, checking whether the choices are yours or the tutorial's. A diagram that shows retrieval, evaluation and a fallback path reads as real. Minute 2–3: they scan the evaluation numbers. Any honest number — even a modest one, especially a modest one with a note about its limits — beats the absence of numbers, which is the single most common portfolio failure. Minute 3–4: they glance at the commit history and, if there is a demo URL, they click it. If it loads, you are usually in the interview.

Order matters. Headline states the target role — "GenAI / LLM Engineer | 6 yrs backend, RAG and agent systems" beats "Senior Software Engineer". A three-line summary links IT to AI capability. Projects sit above Experience, since evidence outranks title. Then Experience reframed, skills, education.

Reframe bullets rather than replacing them:

None invented AI experience — each tied a real capability to an AI outcome.

Keyword alignment without stuffing. Mirror the literal strings from ten target JDs. Recruiters search Boolean on titles and skill tokens: someone hunting agent experience types LangGraph, not "agent frameworks". If you used Qdrant and the JD says "vector database", write both, honestly — and make sure the framework you name (LangGraph, CrewAI) is one you actually shipped with.

ATS myth-buster. ATS is a searchable database, not a robot rejecting you at 74%. Screening is a recruiter keyword-searching and skimming thirty seconds — use standard headings, no text in images, one column if unsure, PDF unless told otherwise.

Headline:

current strength → target direction, e.g. "Backend Engineer → GenAI Systems | RAG, Agents, LLMOps" — signals direction without an unearned title.

About:

the switch narrative in four short paragraphs — what you've done, what pulled you to AI, what you've built since, what you want. First-person.

Featured:

demo links and one write-up — the highest-value real estate on the profile, and most leave it empty.

Activity cadence:

one write-up per fortnight is enough. Consistency beats volume; a build log beats reshared AI news.

Recruiter mechanics:

Open to Work set to recruiters-only visibility, precise location, target titles, and target-role keywords in skills — searchable in a way About text isn't.

Every switcher needs three parts, rehearsed: continuity, trigger (a specific reason, not "AI is the future"), evidence (what you built, broke, learned).

A worked example, a template to adapt:

Note

"Five years in test automation, the last three owning the regression suite for a payments platform — deciding what 'working' means and proving it at scale, on a non-deterministic system under load.

>

Note

A year ago our team piloted a support-summarisation feature and I was asked if it was good enough to ship. Nobody could answer that. That's why I moved.

>

Note

Since then I've built and deployed three systems. The main one is a RAG Q&A service over internal policy documents, with a 120-question evaluation set, retrieval and answer-quality scoring, and a regression gate in CI. It scored badly on table-heavy documents at first; I fixed that with a different chunking strategy and re-ranking, and I can show the before-and-after numbers, including what still fails.

>

Note

I'm looking for an AI evaluation or applied engineering role where correctness is the hard part — that's been my job for five years, just on deterministic systems."

Continuity, trigger, evidence. No apology for the past role.

Internal moves are cheaper and safer but slower and lower-paid; external switches pay better and screen harder — the strongest position runs both.

Run both tracks in parallel from month 3–4, once you have one deployed project. They compound: internal exposure unblocks external applications, where "no professional AI experience" is the top rejection reason. Only-internal leaves you dependent on one manager; only-external means zero workplace evidence.

Find where the AI budget lives — client pilots, internal automation programmes, or a central AI practice/CoE [verify current: names change often — confirm your employer's before naming them]. Find the budget first; the role follows.

Make your interest legible. Tell your manager directly: "our account is getting AI asks and I've been building retrieval systems on my own time — I'd like the next one." Managers sponsor visible capability.

Volunteer for the unglamorous parts. Every pilot needs evaluation, data prep, cleanup and integration — nobody wants these. That's your entry wedge, and evaluation ownership is a legitimate resume line.

Use the formal machinery. Internal job boards, transfer policies and mobility windows exist and are underused; GCCs run formal mobility with defined tenure rules. Ask early in the appraisal cycle, not before ratings.

The 60–90 day notice problem is real and costs offers, mostly because candidates disclose it late. Raise it in the first recruiter conversation. Ask early about buyout — employers often fund part for a hard-to-fill role, rarely on offer day — and mention if part can be served against leave.

Time the waves. Apply two to three months before a bonus or vesting date, so the offer lands after the money does. Don't resign in anticipation — get the offer in writing first, notice terms included.

External pays better, screens harder. No internal reputation carries over — the portfolio and loop are all the evidence you have.

Negotiate posture for the switcher discount. The first AI offer is often priced below market since you're paid partly on AI experience you don't yet have. Fighting it to a standstill usually fails. What works: trade title for the right work — year-one exposure shapes your second offer more than a two-lakh gap in the first — get the review timeline in writing, and negotiate scope: which layer of the stack, evaluation ownership or just tickets.

No unethical shortcuts. No dual employment, absconding, overlapping payroll or fake experience letters — each is a contractual breach, BGV catches most, and one flagged BGV follows you across employers.

Channels, ranked for switchers:

1. 1Referrals — bypasses the "no AI experience" filter and gets a human to open your project link. Outreach: who you are, the system you built, why their team, one clear ask ("would you refer me for the GenAI Engineer role, ID 4471?"). No mass templates.
2. 2LinkedIn — best for GCC and product roles; apply within 48 hours and message the hiring manager separately with the project link.
3. 3Naukri — highest volume for services and enterprise roles; update the profile weekly since recruiter search sorts on recency.
4. 4Instahyre / Cutshort — curated, decent signal for mid-market product companies.
5. 5Wellfound — startups, where deployed-project evidence outweighs brand pedigree.
6. 6Company career pages — necessary for GCCs, which often post roles internally days before aggregators see them.

Application discipline. Ten to twenty quality applications a week beats two hundred sprayed with no tailoring. Track: date, company, role, channel, JD link, resume version, referral contact, round reached, outcome, rejection reason, follow-up date. Tailor the top third per cluster — evaluation, RAG engineering, AI-adjacent consulting — not per application.

Bands from tracked transitions, not survey data. 50–150 applications across two to four months is a normal, healthy funnel, not failure, and the distribution is lumpy: silence, then three loops at once. Review your log monthly for which round eliminates you. No callbacks means resume and channel mix are wrong; dying at coding means Python needs drilling; dying at project defence means your projects are shallower than they look; dying repeatedly at the final round is narrative or comp misalignment, not skill.

Six rounds, and switchers usually lose at round five — the round their portfolio was supposed to win.

Round 3 — eight real example questions:

Fine-tuning vs RAG — when neither? Why do embeddings retrieve semantically similar but wrong chunks? What does temperature actually change? How do you measure whether a RAG answer is grounded? What's a re-ranker and when is it worth the latency? Why do agents loop, and how do you bound them? What is context-window pressure and how do you manage it? How do you detect and handle hallucination in production?

Round 4 — the answer framework. Given a system-design prompt like "design document Q&A over 10M files" or "design an agent that files support tickets": start with requirements (users, latency, freshness, accuracy tolerance, budget), then retrieval and model choices with a reason for each, then evaluation (what, on what dataset, what gate), then cost and latency (per query, at 100× load), then failure modes (what breaks first, the fallback). Say the sections aloud — interviewers score structure as much as content.

The single highest-value prep: have a peer or mentor attack one project for thirty minutes, told to be unkind. Sample questions: Retrieval quality drops on tables — why, and what did you try? What does this cost at 100× load? Why this vector database? What breaks first if traffic triples? How do you know answers are grounded? What would you delete if you rebuilt it? Why chunk at that size? What happens when the provider deprecates your model version? Which part did you copy, and what did you change?

Record the session. The goal isn't answers for these ten — it's becoming unsurprisable about your own system.

Decode the CTC before you celebrate, and benchmark the fixed component against AmbitionBox and Levels.fyi for your city and band. Fixed pay is the only number that pays your EMI. Variable is conditional on performance — in a bad year it's 60–70% of target. ESOPs at a private company are paper with a vesting cliff and no liquidity event — value them at zero for budgeting.

Optimise for the work, not the last two lakh. What you touch in year one determines your second offer. Owning retrieval, evaluation and deployment beats a marginally better-paying role writing prompts against someone else's pipeline.

1. 1The tutorial and certificate loop. Consuming forever, shipping never — a completion screen feels safe, a public repository feels exposed.
2. 2Hiding IT experience instead of repositioning it. Shortening the years that are the entire reason a hiring manager would prefer you to a fresher.
3. 3Learning breadth-first across all of AI instead of gap-first against ten target JDs — six months of classical ML for a role that will never test it.
4. 4Notebook-only portfolios. Five Jupyter files with no deployment, no evaluation and no README read as coursework, because they are.
5. 5Running only one track — applying externally for months without asking internally, or waiting on an internal pilot that never got funded.
6. 6Spraying 200 identical applications, getting nothing, and concluding the market is dead rather than that the tailoring was.
7. 7Quitting to study full-time when an evenings plan carried zero downside, adding financial pressure and a resume gap for a few extra tired hours a day.
8. 8Stopping at rejection number thirty — inside the normal funnel range — usually one pattern-fix away from the loop that converts.

Myth: "You need a Master's or PhD." → Reality: true for Tier 3 research roles, where publication and depth are the product. False for applied Tier 2 engineering, where four deployed systems with honest evaluation outrank a degree in almost every loop I've seen — and Stanford HAI's AI Index shows how small the doctoral pipeline is relative to the number of applied AI roles being posted. Degrees help at HR gates and visas; they don't decide applied AI interviews.

Myth: "You need heavy mathematics." → Reality: applied roles need working intuition for metrics, trade-offs and failure modes, not derivations. ML Engineer carries the highest maths load, GenAI Engineer meaningfully less, AI Product Manager least. Choose the role and the maths question answers itself.

Myth: "35 — or 40 — is too late." → Reality: age is not the filter; evidence is. AI-plus-domain roles reward the years, since enterprise AI work is mostly integration with messy systems a fresher has never seen. Ageism exists in pockets, but tracked transitions include successful switchers at 35 and beyond.

Myth: "You will restart at fresher salary." → Reality: a switcher discount on the first AI offer is common; a reset to fresher pay is not, when experience is positioned rather than hidden. Most of the gap closes within one to two cycles once you have professional AI delivery on record.

Myth: "Certificates get jobs." → Reality: they satisfy HR gates and occasionally a staffing filter. In 2026 they carry near-zero weight with hiring managers, who've seen thousands. Evidence gets jobs; certificates get you past the form.

Myth: "Prompt engineering is the easy way in." → Reality: it's declining fast as a standalone role and rising as a layer inside real engineering and product roles — provider documentation now treats it as a baseline engineering skill (OpenAI, Anthropic), not a job description. Prompting skill is genuinely valuable; a career built only on it is exposed.

Myth: "You must quit to learn properly." → Reality: tracked transitions say otherwise. Employed switchers negotiate better, keep the internal track alive, carry no resume gap and burn nothing. The constraint is consistency, not hours available.

Myth: "AI roles will be automated soon anyway." → Reality: nuanced. Tooling compresses tasks — code generation already changed junior work — while demand shifts toward system design, evaluation, integration and accountability, exactly what this page teaches — the WEF Future of Jobs Report 2025 projects 170 million new roles created against 92 million displaced by 2030, a net gain concentrated in exactly these technology skills. Nobody can promise any role's ten-year safety, and anyone who does is selling something.