AI Professionals Career Guide

Explore AI jobs, salaries, and career paths across research, engineering, product, and governance. Find the specialism that fits you, and stay current on models, agents, evaluation, and AI regulation.

How we research our career guides

The Top AI News, in 5 Minutes.

We handpick the best AI newsletters and distill key news and insights into a 5-minute audio briefing, texted to you every morning.

Try the AI Briefing, FreeFree
See the 10 newsletters we handpicked

At a glance

AI Careers at a Glance

There is no federal occupation called AI professional. The Bureau of Labor Statistics counts the field in pieces: 275,600 data scientists at a $120,230 median in May 2025, growing 35 percent to 2035; 1,717,800 software developers at $135,980; 38,600 computer and information research scientists at $140,300; 192,900 information security analysts at $129,180; and 685,800 computer and information systems managers at $175,140. Across computer and information technology occupations the projection is about 280,000 openings a year. The common picture of the job, somebody training a model, covers one slice of it. The field extends well beyond training: research scientists who design and probe methods, machine learning engineers who make training and serving reliable, AI engineers who build retrieval and agents on models somebody else trained, product managers who decide what is worth building and what counts as good enough, consultants who judge whether an organisation can carry the promise, and governance and security specialists who answer for what the system does. Demand is real and narrower than the discourse: Lightcast's work for the 2026 Stanford AI Index put AI skills in 2.5 percent of United States postings, up 55 percent in a year. Entry is by evidence in most of the field, by graduate degree in research, and the regulatory layer is becoming part of everyone's job.

Key Industry Statistics

2.5%

US job postings naming AI skills (2025)Lightcast, for the 2026 Stanford AI Index

$140,300

Median pay, computer and information research scientistsUS Bureau of Labor Statistics

+35%

Projected growth for data scientists, 2025 to 2035US Bureau of Labor Statistics

280,000

Annual openings across computer and IT occupationsUS Bureau of Labor Statistics

Common Roles

  • AI Engineer
  • Machine Learning Engineer
  • AI Research Scientist
  • AI Product Manager
  • AI Consultant
  • AI Governance Lead

Where AI Professionals Work

  • Frontier model labs
  • Software and platform companies
  • Banks and insurers
  • Healthcare and life sciences
  • Government and defence
  • Consultancies and agencies

Credentials That Matter

  • Bachelor's in a computing field
  • Master's or doctorate for research
  • A portfolio with measured results
  • Cloud and ML platform certifications
  • NIST AI RMF fluency

Key Areas in AI Careers

  • Research & Methods

    Designing, training and probing architectures, objectives and the learning methods behind them.

  • Applied AI Engineering

    Retrieval, agents and evaluation built on top of models somebody else trained.

  • ML Platform & Serving

    Pipelines, training infrastructure and inference held inside a latency and cost budget.

  • Product & Adoption

    Deciding what is worth building, and what counts as good enough to ship.

  • Governance & Policy

    Risk frameworks, transparency duties and the audit trail a regulator will ask for.

  • Security & Red Teaming

    Prompt injection, excessive agency and the blast radius of a tool call.

AI Jobs and Salaries

There is no AI occupation in the federal statistics, so this table uses the five adjacent occupations the work is actually counted under. Every figure is the May 2025 median from the Occupational Outlook Handbook, and no blended AI salary is invented here.

  • Data scientists

    $120,230

    275,600 jobs · +35% to 2035

  • Information security analysts

    $129,180

    192,900 jobs · +21% to 2035

  • Software developers

    $135,980

    1,717,800 jobs · +10% to 2035

  • Computer and information research scientists

    $140,300

    38,600 jobs · +22% to 2035

  • Computer and information systems managers

    $175,140

    685,800 jobs · +16% to 2035

Source: US Bureau of Labor Statistics, Occupational Outlook Handbook, May 2025 wage data, accessed October 2026.

AI Career Paths

Working in AI is not one ladder. It is four tracks that share a vocabulary and then diverge sharply in what they reward, who they report to and how much of the day is spent near a model.

  1. Junior AI Engineer0 to 2 yearsBuild features on an existing stack. Measured on reliability and on whether your own evaluation catches your bugs.
  2. AI Engineer2 to 5 yearsOwn a surface end to end, including its evaluation set, its cost per resolved task and its failure taxonomy.
  3. Senior AI Engineer5 to 9 yearsOwn the seams: retrieval quality, agent permissions, routing policy and the budget that constrains all three.
  4. Staff or Principal Engineer9 or more yearsSet technical direction across teams and decide which model bets the organisation stops funding.

Credential that fits A portfolio of shipped systems with measured failure rates

There is no federal occupation code for an AI engineer, a machine learning engineer or a head of AI. The figures on this page therefore come from the five adjacent occupations the Bureau of Labor Statistics does publish, which is also how an employer's compensation system is likely to file the role.

A Typical Day in AI Jobs

Five roles that between them cover most of the field's headcount, ordered from the applied end toward research and leadership. The schedules are representative rather than universal: company size, sector and whether anything is on fire move all of it.

AI EngineerEntry to Mid · Applied ProductBuilding a user-facing feature on a model somebody else trained, where most of the difficulty is retrieval, evaluation and cost.
  1. 09:00Check overnight evaluation runs and the cost dashboard before opening anything else. Regressions hide in both.
  2. 09:30Read ten real traces from yesterday's failures. This is the habit that generates everything else on the list.
  3. 11:00Change one thing: a chunking rule, a reranker, a tool schema. Re-run the evaluation set before and after.
  4. 14:00Review a colleague's prompt change the way you would review code, including what it costs per call.
  5. 16:00Write up what moved and what did not, so the next person does not repeat the experiment.
Machine Learning EngineerMid-Level · Platform and ServingKeeping training and inference reproducible, fast and affordable for everyone else, usually with a pager attached.
  1. 08:30Check pipeline health and drift monitors. A silent data change upstream is the most common cause of a bad week.
  2. 10:00Work a latency budget: profile where the time goes, then argue about which part of it is negotiable.
  3. 12:00Move an offline workload to batch processing, which halves its cost, and verify nothing depended on it being live.
  4. 14:30Pair with a researcher on getting an experiment reproducible enough to hand over.
  5. 16:30Capacity planning, because the next model version will not fit the current budget without a decision.
AI Research ScientistSenior-Level · Methods and EvaluationOwning a line of questions rather than a product surface, with a master's degree or doctorate as the usual entry.
  1. 09:00Read overnight results and kill the variants that are clearly not working, before sunk cost sets in.
  2. 10:30Design the next ablation so it can only have one explanation. Most of the skill is here.
  3. 13:00Reading group or paper discussion, which is where the field's actual peer review happens.
  4. 15:00Write. A result nobody can reproduce from your description did not happen.
  5. 17:00Negotiate compute with the platform team, which is the real constraint on an agenda.
AI Product ManagerMid to Senior · Product and AdoptionDeciding what is worth building and what counts as good enough to ship, with the evaluation bar written before the work starts.
  1. 09:00Look at yesterday's user-reported failures, not the dashboard. The dashboard shows what you already thought to measure.
  2. 10:30Agree the quality bar for a new surface with engineering, in numbers, before anybody builds it.
  3. 13:00Sit with a customer and watch them use the thing. Half of the roadmap comes from this hour.
  4. 15:00Work the design question of what the product does when the model is wrong, which is most of the product.
  5. 16:30Write the decision down with the evidence attached, so the next reversal is informed rather than political.
AI Governance LeadSenior-Level · Risk and ComplianceOwning the approval route, the incident process and the answer a buyer or a regulator receives about a live system.
  1. 09:00Review deployment requests against the Govern and Map functions: named owner, stated context, affected users.
  2. 11:00Work a security question with engineering, usually about tool permissions and what untrusted content can reach.
  3. 13:00Answer a customer's due-diligence questionnaire, which is where governance work meets the sales cycle.
  4. 15:00Track the regulatory calendar and turn one date into an engineering ticket with an owner.
  5. 16:30Run or review an incident post-mortem, and change the standing process rather than the individual.

JOB SEARCH

How to Get an AI Job in 2026

Working in AI is not one job. It is six, with different entry evidence, different pay bands and different employers, and the first useful decision is which of them you are applying for. What follows is grounded in federal occupational data, the measurement work the field runs on, and the regulation that is now part of shipping.

Entry-Level

Break Into the AI Field

What the field is actually made of, which of its six jobs you are applying for, what each one expects on paper, and what a hiring manager reads instead of the paper.

What you should know about the field

How the work is counted, what the routes into it are, and what the demand data really supports.

There Is No AI Occupation in the Federal Data

The Bureau of Labor Statistics does not publish an occupation called AI professional, AI engineer or prompt engineer. It counts the field in pieces: 275,600 data scientists at a $120,230 median in May 2025, 1,717,800 software developers at $135,980, 38,600 computer and information research scientists at $140,300, 192,900 information security analysts at $129,180, and 685,800 computer and information systems managers at $175,140.

That matters for a job search. The title on the posting is set by the hiring team, while the pay band is usually set by whichever of those occupations the finance system files you under. Ask which internal job family a role sits in, because it predicts the ceiling better than the title does.

Sources:

The Six Jobs People Mean by Working in AI

Research scientists design and probe methods, and the federal proxy for them expects a master's degree. Machine learning engineers make training and serving reliable and affordable. AI engineers build retrieval, agents and evaluation on top of models somebody else trained. Product managers decide what is worth building and what counts as good enough. Consultants judge whether an organisation can carry the promise. Governance and security specialists answer for what the system does once it is live.

They share vocabulary and almost nothing else day to day. Choosing between them early is worth more than any certificate, because the evidence each one asks for takes a year or two to build and does not transfer cleanly.

Sources:

What the Demand Data Actually Says

Lightcast's analysis for the 2026 Stanford AI Index found AI skills named in about 2.5 percent of United States job postings, up 55 percent on the previous year, 72 percent on 2022 and close to 300 percent over the decade. Python remained the most requested specialised skill, appearing in 258,674 postings, roughly 30 percent above 2024.

One posting in forty is real growth and a narrow market at the same time. Read it as a reason to be specific rather than a reason to be confident: the roles exist, but a generic AI enthusiast competes against everyone, while a candidate with a named specialism competes against a much smaller field.

Sources:

Which Credential Each Route Expects

The federal entry requirement differs by route. Software developers, data scientists and information security analysts are all recorded with a bachelor's degree as typical entry-level education. Computer and information research scientists, the nearest proxy for frontier research work, are recorded with a master's degree, and doctorates are common in practice.

So there is no single answer to whether you need a graduate degree. For applied engineering, product and consulting the answer is usually no and the portfolio decides. For research posts the degree is close to a filter, and the time it costs is the real decision rather than the tuition.

Sources:

Skills employers look for

What a hiring manager checks when there is no track record to check, beyond the degree itself.

Python and SQL, Still the Baseline

Python was the most requested specialised skill in United States AI postings in 2025, named in 258,674 of them, about 30 percent above 2024. SQL sits beside it because almost every applied problem starts with getting the right rows out of somebody's warehouse. Neither is a differentiator any more, and the absence of either is still disqualifying.

Sources:

Reading an Evaluation Before Believing It

The AI Index exists because headline capability claims move faster than the evidence for them. The entry-level version of this skill is modest: know what the benchmark measured, on what data, against what baseline, and whether the comparison was run at the same cost. Candidates who ask those four questions out loud read as practitioners rather than enthusiasts.

Sources:

Shipping Something a Stranger Can Run

Across every route into this field the entry evidence is the same shape: a working artefact with a readme, a reproducible setup and an honest account of what it gets wrong. The federal occupations behind these jobs all record a bachelor's degree as typical entry, which means the degree gets you read and the artefact gets you hired.

Sources:

Cost Literacy From Your First Project

Model spend is an engineering variable, not a finance one. Prompt caching bills cache writes at 1.25 times base input tokens and cache reads at a fraction of it, and the Message Batches API halves the cost of work that does not need an immediate answer, with most batches finishing inside an hour. Knowing those two levers early separates a prototype from something anyone will run.

Sources:

Interview questions and answers

Questions entry candidates actually get, and what the interviewer is listening for underneath them.

Which part of AI work do you want to do, and why that one?

What they are looking for: Whether you have chosen a lane. Generalist enthusiasm is the most common reason an otherwise strong entry candidate is passed over.

I want applied engineering rather than research. I like problems where the model is fixed and the difficulty is retrieval, evaluation and cost, and I proved that to myself by rebuilding a search feature three times before the answers were actually right. Research appeals to me intellectually, but I would rather ship something people use every week.

Make it yours: Name the route and the thing you did that tested the preference. A choice with no evidence behind it reads as a guess.

Walk me through a project you built, including what it gets wrong.

What they are looking for: Honesty and measurement. Interviewers assume every entry project is fragile; they are testing whether you know where.

It answers questions over about four thousand internal documents. It is reliable on direct factual lookups and poor on anything requiring two hops, because my chunking splits tables from their captions. I know that because I labelled sixty real questions and scored them, and the two-hop ones failed roughly half the time.

Make it yours: Bring a number you measured yourself. A candidate who can quantify their own failure rate is instantly above the median.

How would you tell whether a new model is actually better for us?

What they are looking for: Whether you reach for a benchmark leaderboard or for your own task. This is the single most useful entry-level instinct.

I would not start from a public benchmark, because it is not our distribution. I would take fifty real requests we already have correct answers for, run both models at the same cost ceiling, and compare accuracy, latency and spend. If the new one wins on two of three I would shadow it in production before switching.

Make it yours: Say out loud that you would hold cost constant. Most candidates compare quality and quietly ignore the bill.

What would you do if the model is confidently wrong in production?

What they are looking for: Debugging order. They want to hear you isolate the layer before you start changing prompts.

First I check whether the right context was retrieved at all, because a retrieval miss and a generation error look identical to a user. If retrieval was fine I look at whether the model version or the prompt changed recently. Only then do I touch the prompt, and I add the case to the evaluation set before I do.

Make it yours: Mention adding the case to the evaluation set. It is the step that separates a fix from a habit.

Why AI Professionals Need to Stay Informed

No other field changes its own working assumptions this fast. A method published this quarter can be the default next quarter, a price change can rewrite what is affordable to build, and a regulatory date can move a roadmap. Staying current is not background reading here. It is the part of the job that decides whether your judgement is still worth asking for.

Read more

The second reason is commercial. Enterprise buyers now ask which risk framework you map to and which compliance dates apply before they ask about accuracy, and those answers change more often than the models do.

The bottom line

AI Careers Are Splitting Into Specialisms. Choose Yours.

The federal projections point in five different directions at once: data scientists up 35 percent to 2035, research scientists 22 percent, security analysts 21 percent, systems managers 16 percent and software developers 10 percent from a far larger base. The opportunity is real, and it rewards being specific.

Stay Informed with Hark's AI Briefing

How it works

  1. Curated from the best newsletters

    Hark's editorial team handpicks the sources worth following. See how we rank

  2. The news that matters in 5 minutes

    Hark distills the most important stories into a concise audio briefing.

  3. Texted to you every morning

    You set the time and listen when you want.

  4. Go deeper if you want

    Upgrade to the 15-minute briefing and select up to 50 newsletters.

The 10 AI Newsletters We Handpicked

  1. The Rundown AI

    Rowan Cheung

    • Free
    • Daily
    • 2M readers

    Rowan Cheung's daily five-minute rundown of AI news and tools, teaching 2 million+ readers what just shipped and how to actually use it.

    Why AI professionals read it

    The largest AI newsletter, a five-minute daily on what launched and how to use it. Even for a specialist it is the quickest read on what the wider market now expects AI to do.

    Listen to The Rundown AI free

    More about this newsletter

    Rowan Cheung's The Rundown AI is one of the largest AI newsletters, a daily digest of model launches, tools, and industry news built for a broad audience. Each issue turns the day's biggest release into a workflow you can try the same morning. Breadth over depth, delivered fast.

    Best for: Anyone who wants to keep up with AI in five minutes a day. It's the largest AI newsletter for a reason: every issue turns the day's biggest model release or tool launch into something you can actually try that morning, no technical background needed.

  2. Superhuman AI

    Zain Kahn

    • Free
    • Daily
    • 1.5M readers

    Zain Kahn's daily briefing on AI news, tools, and how-tos, engineered for busy professionals and read by 1.5 million+ subscribers.

    Why AI professionals read it

    Zain Kahn's daily on AI news, tools and how-tos, built for professionals rather than researchers. Good for tracking the tooling layer that turns a model release into something a team can actually adopt.

    Listen to Superhuman AI free

    More about this newsletter

    Zain Kahn's Superhuman AI is built around using AI at work: practical tool tips, prompts, and news framed for productivity in a quick daily read. It is the fastest scan of the big AI dailies. Best for professionals who want practical how-to alongside the headlines.

See the other 8 newsletters
  1. TLDR AI

    TLDR

    • Free
    • Daily (weekdays)
    • 1.1M readers

    TLDR's daily AI edition compresses research papers, product launches, and industry news into a five-minute weekday read for over a million subscribers.

    Why AI professionals read it

    The most technical of the big AI dailies, compressing the day's research papers, model launches and industry news into a five-minute scan written for engineers. The fastest way to be sure nothing that shipped overnight got past you.

    Listen to TLDR AI free

    More about this newsletter

    TLDR AI compresses the day's AI research, product launches, and industry news into one-sentence summaries you can scan in minutes. It is the most technical of the big AI dailies, written with engineers in mind. Efficient, dense, and no-nonsense.

  2. The Neuron

    The Neuron (TheurgyOne)

    • Free
    • Daily (weekdays)
    • 700k readers

    A daily tour of AI news and tools written for working professionals, translating the industry's firehose into practical takeaways for 700,000+ readers.

    Why AI professionals read it

    A weekday tour of AI news translated into practical takeaways for working professionals. It is the version of the firehose you can forward to a colleague who does not follow the field.

    Listen to The Neuron free

    More about this newsletter

    The Neuron explains AI news and tools in plain English with a light touch, for readers who want to understand what matters without a computer science degree. It is the most approachable of the daily AI digests. Friendly, clear, and genuinely useful for beginners.

  3. TLDR

    TLDR Newsletter

    • Free
    • Daily
    • 8M readers

    Five-line summaries of the day's engineering, startup, and science links.

    Why AI professionals read it

    Five-line summaries of the day's engineering, startup and science links. It keeps an AI specialist attached to the rest of technology, which is easy to lose sight of.

    Listen to TLDR free

    More about this newsletter

    Five-line summaries of the day's tech, startup, and programming links, chosen for engineers rather than investors. No commentary and no filler; the TLDR homepage claims more than eight million readers.

  4. The Download

    MIT Technology Review

    • Free
    • Daily
    • 250k readers

    MIT Technology Review's daily dose of what matters in emerging technology, written with institutional rigor.

    Why AI professionals read it

    MIT Technology Review's daily on emerging technology, sober and hype free. It puts your field in the context of the ones it is about to collide with.

    Listen to The Download free

    More about this newsletter

    MIT Technology Review's daily briefing distills what matters in emerging technology, drawing on the magazine's own reporting on AI, biotech, climate, and computing. It is institutional, sober, and reliably free of hype. One of the few tech dailies with a real newsroom behind it.

    Best for: Readers who want emerging tech coverage from a real newsroom: sober, hype free daily reporting on AI, biotech, climate, and computing from MIT Technology Review.

  5. TechCrunch Daily News

    TechCrunch

    • Free
    • Daily

    TechCrunch's flagship roundup of the day's top startup and technology stories, delivered every weekday and Sunday.

    Why AI professionals read it

    TechCrunch's weekday roundup of funding, launches and industry news. It tells you which AI companies just raised and which are quietly consolidating.

    Listen to TechCrunch Daily News free

    More about this newsletter

    The best of TechCrunch's daily coverage (funding rounds, product launches, and tech industry news) compiled by the site's editors. Arrives every weekday plus a Sunday edition. Free, alongside TechCrunch's other newsletters (Startups Weekly, Mobility, Week in Review, StrictlyVC).

  6. The Pragmatic Engineer

    Gergely Orosz

    • Free
    • Frequent
    • 1.1M readers

    Deeply reported dispatches on how Big Tech and startups actually build software, from an ex-Uber engineering leader.

    Why AI professionals read it

    Deeply reported dispatches on how Big Tech and startups actually build software, from an ex-Uber engineer. The best account anywhere of the engineering reality your models ship into.

    Listen to The Pragmatic Engineer free

    More about this newsletter

    Gergely Orosz, formerly an engineering manager at Uber, reports on how software actually gets built inside Big Tech and startups: engineering culture, compensation, layoffs, and deep dives into real systems. His reporting on tech companies is read industry-wide. The deep dives are paid, but the free weekly issues keep casual readers current.

  7. TLDR Dev

    TLDR (TLDR Media)

    • Free
    • Daily
    • 470k readers

    Daily software engineering news, tools, and web dev links in a five minute read.

    Why AI professionals read it

    Daily software engineering news, tools and web dev links in a five minute read. The practitioner's feed, and a useful counterweight to research-heavy AI reading.

    Listen to TLDR Dev free

    More about this newsletter

    TLDR Dev is the software engineering edition of the TLDR network: one daily email of programming news, new tools, and web development links, each with a one-paragraph summary. It is aggregation, not commentary, tuned for working developers across the stack. Best for engineers who want the day's dev news skimmed in five minutes.

  8. ByteByteGo Newsletter

    Alex Xu (ByteByteGo)

    • Freemium
    • 1M readers

    System design newsletter by Alex Xu, co-author of the System Design Interview books, explaining complex architectures in plain language with heavy use of diagrams.

    Why AI professionals read it

    Alex Xu's system design newsletter, explaining complex architecture in clear diagrams. Serving models is a systems problem, and this is the clearest teaching on systems.

    Listen to ByteByteGo Newsletter free

    More about this newsletter

    Issues break down how large systems work (Docker internals, network protocols, the tech stacks behind companies like Netflix) in the same diagram-first style as Xu's bestselling system design books. Hosted on Substack with a free tier and paid deep-dive content; the site claims over 1,000,000 readers.

Frequently Asked Questions

Entry-Level

What does it actually mean to work in AI in 2026?

It means one of about six jobs, not one. Research scientists design and probe methods. Machine learning engineers make training and serving reliable and affordable. AI engineers build retrieval, agents and evaluation on models somebody else trained. Product managers decide what is worth building and what counts as good enough. Consultants judge whether an organisation can carry the promise. Governance and security specialists answer for what the system does once it is live. They share vocabulary and very little else day to day, and the first useful decision in an AI job search is choosing which of them you are applying for.

Is working in AI a good career in 2026 and beyond?

On the federal numbers, yes, with a caveat about breadth. There is no AI occupation, so the field is counted as data scientists, growing 35 percent to 2035 at a $120,230 median, software developers at $135,980 growing 10 percent from a 1,717,800-job base, computer and information research scientists at $140,300 growing 22 percent, information security analysts at $129,180 growing 21 percent, and computer and information systems managers at $175,140 growing 16 percent. Lightcast's work for the 2026 Stanford AI Index puts AI skills in 2.5 percent of United States postings, up 55 percent in a year. Real growth, narrow market.

Do you need a degree, and does it have to be in computer science?

It depends which route you want. The Bureau of Labor Statistics records a bachelor's degree as typical entry-level education for software developers, data scientists and information security analysts, and a master's for computer and information research scientists, where doctorates are common in practice. For applied engineering, product and consulting the degree gets your application read and the portfolio decides the outcome. For frontier research the graduate degree is close to a filter, and the years it costs are the real decision rather than the tuition.

How do AI engineers, machine learning engineers and research scientists differ?

By what they own. An AI engineer builds products on a model somebody else trained, so their problems are retrieval quality, agent design, evaluation and cost. A machine learning engineer owns the pipelines, training runs and serving infrastructure, and is usually on call for them. A research scientist owns a line of questions and is judged on results that survive someone else reproducing them. Our AI engineers, machine learning engineers and AI research scientists guides each cover one of those ladders in full depth.

What skills and tools should a beginner learn first?

Python and SQL remain the baseline rather than a differentiator. Python was named in 258,674 United States AI postings in 2025, about 30 percent more than in 2024, and almost every applied problem starts with getting the right rows out of somebody's warehouse. After that, learn to read an evaluation before believing it: what was measured, on what data, against what baseline, and at what cost. Then learn the two cost levers, caching and batch processing, because a prototype nobody can afford to run is not a portfolio piece.

How do you build an AI portfolio that gets you hired without experience?

Build one artefact a stranger can run, not five demos. It needs a readme, a reproducible setup and an honest account of its failure rate measured on cases you labelled yourself. Fifty real questions scored by hand beats any benchmark number you can quote. Say what it gets wrong and why, because interviewers assume every entry project is fragile and are testing whether you know where. A candidate who can quantify their own error rate is immediately above the median.

What are the best entry-level jobs for getting into AI work?

The reliable routes in are data or platform engineering, where pipeline work is permanently under-supplied and teaches you the data layer everything else depends on; junior software engineering on a team that already ships AI features; and analyst or associate product roles where you write the evaluation criteria. Research internships are the route into research and are far more competitive, with only 38,600 computer and information research scientist jobs in the whole country. Going in sideways through the data layer is underrated and works.

Get Tomorrow's AI Briefing

TLDR AI alone reaches more than a million engineers who scan the day's models, papers and launches before work, and The Pragmatic Engineer is read by the leaders who decide what ships. In a field moving this fast, being last to hear is a real disadvantage.