AI Research Jobs

AI Research Jobs

1,768 open rolesEngineering

Explore 1,768 open AI research jobs at fast-growing tech, startup, and AI companies hiring right now. Push the frontier: train new models, run the experiments, and publish what works.

Typical salary
$140K–$220K
US median base, mid–senior
Top skills
System designAPIsTestingCI/CD
Common tools
TypeScriptReactPythonAWS
Open roles
1,768
open AI research roles

Open Positions1,768 AI Research jobs

Liquid AI
Member of Technical Staff - ML Research Engineer, Pre-Training DataLiquid AI
Otter.ai
Director of AI ResearchOtter.ai
LG AI Research
Research Scientist - Physical AI & Robot Foundation ModelsLG AI Research
LG AI Research
Research Internship - Physical AILG AI Research
Pluralis Research
Research Engineer InternPluralis Research
LG AI Research
Speech LLM Research Scientist InternshipLG AI Research
Pluralis Research
Research Scientist - Geo-Distributed InferencePluralis Research
Sieve
Member of Technical Staff, Robotics ResearchSieve
Embedding VC
Member of Technical Staff, Applied ResearchEmbedding VC
Convergent Research
Research Hardware EngineerConvergent Research
Black Forest Labs
Member of Technical Staff - Research EngineerBlack Forest Labs
Crosby
Member of Technical Staff, Research EngineerCrosby
LG AI Research
Research Scientist - Ontology & Knowledge GraphLG AI Research
LG AI Research
Research Scientist - Industrial OptimizationLG AI Research
Profound Research
Sr. Clinical Research Coordinator (Pasadena, CA)Profound Research
Callosum
ML Research Engineer - Member of Technical StaffCallosum
Pluralis Research
Research Engineer - Pre-trainingPluralis Research
A
Member of Technical Staff, Research (Intern)Abundant
Tower Research Capital
Quantitative ResearcherTower Research Capital
DoorDash USA
Member of Technical Staff, Lead ResearcherDoorDash USA
Red Cell Partners
Member of Technical Staff, AI Researcher (New Stealth Startup)Red Cell Partners
Toyota Research Institute
Human-Centered AI Research Intern, Human Language ModelsToyota Research Institute
Rhoda AI
Research Member of Technical Staff - Data & EvaluationRhoda AI
Tanium
AI Research ScientistTanium
Polymath
Member of Technical Staff - ResearchPolymath
Convergent Research
Postdoctoral Research Scientist, Ocean CDR AtlasConvergent Research
Pluralis Research
Research Engineer - Post-TrainingPluralis Research
Rhoda AI
Research Member of Technical Staff- Training SystemsRhoda AI
Chai Discovery
Research Scientist, Applied ResearchChai Discovery
Odyssey
Member of Technical Staff, Applied ResearchOdyssey
Career Path

The engineering career ladder

Most software engineering careers begin the same way. You start in an internship or new-grad role, get promoted to Software Engineer, then to Software Engineer II as you begin owning features on your own. This shared early track is where the fundamentals get built: shipping code, reviewing pull requests, and learning how a real production system behaves under load.

Around the senior level the ladder splits. You can keep going deeper on the technical side as an individual contributor, or move toward leading people on the management side. One is not a promotion over the other. Most companies pay a Staff Engineer and an Engineering Manager the same, so the real question is which work you want to do all day.

The pivot point: Senior Engineer

Senior is where most engineers choose. If you like mentoring, planning, and getting more out of a team, the Tech Lead and Manager path fits. If you would rather stay close to the code and own the hardest problems, the Staff and Principal path is yours. You can start down one and cross over later.

What changes as you climb

  • Pay bands overlap across the two tracks at every matching level. A Staff Engineer (L5) and an Engineering Manager (L5) are peers.
  • The IC track narrows fast near the top. There are far more Senior roles open than Principal or Distinguished ones, which the live counts show.
  • Management roles cluster at scale-ups and larger companies. Early-stage startups hire mostly ICs.
  • Switching tracks later is common. Plenty of Directors were once Staff Engineers, and the reverse happens too.

IC vs. Management, side by side

Individual ContributorManagement
Core workArchitecture and the hardest technical problems, hands on the codePeople, delivery, hiring, and coordinating across teams
Judged onTechnical impact and the systems you make possibleTeam output, growth, and retention
A normal dayDesign docs, prototypes, long stretches of focus1:1s, planning, unblocking people, reviews
Scope grows byThe reach and depth of your technical influenceThe size of the org you lead
Focus Areas

Kinds of engineering

Engineering is a wide field. Most people specialize in one area over time, and the day-to-day work looks different in each. Here are the main tracks and what they cover.

FAQ

Engineering jobs: common questions

What does a software engineer do?

A software engineer designs, writes, and maintains the code behind an application or system. Day to day that means building features, reviewing other engineers work, fixing bugs, and keeping the software running in production. The exact focus depends on the area, from frontend and mobile to backend, infrastructure, and machine learning.

How do I become a software engineer?

Most engineers get in through a computer science degree, a coding bootcamp, or self-study plus a strong portfolio of real projects. Companies care most about what you can build, so shipped projects and a clean GitHub often matter more than the path you took. Internships and open-source contributions are the usual way to land a first full-time role.

What is the difference between the IC and management tracks?

The individual contributor (IC) track keeps you close to the code and the hardest technical problems, growing from Senior to Staff to Principal. The management track shifts you toward leading people, from Tech Lead to Engineering Manager to Director. Most companies pay the two tracks the same at each level, so it is a choice about the work, not a promotion.

Which programming languages should I learn?

Start with one language you can go deep in, then add breadth. TypeScript and Python are the safest first picks because they show up across web, backend, data, and AI work. From there, Go and Rust are strong for systems and infrastructure, Swift and Kotlin for mobile, and SQL is worth knowing no matter what you build.

Do software engineers need a degree?

No. Plenty of working engineers are self-taught or came through a bootcamp. A degree helps with some larger companies and visa cases, but most teams hire on demonstrated skill: your projects, how you reason through a problem, and how you perform in the technical interview.

How much do software engineers make?

Pay ranges widely by level, location, and company. In the US, a mid-level engineer commonly lands in the range shown on this page, senior and staff roles go higher, and total compensation at larger companies includes equity on top of base. The live salary bands above are illustrative; the open roles listed here show real postings.

Explore other roles

Browse open roles in other functions across tech, startup, and AI companies.

Explore Sales22,223 jobs

Find the buyers, run the deals, and grow revenue.

Explore Data7,799 jobs

Turn raw data into models, metrics, and decisions.

Keep the company running and the trains on time.

Explore Product6,018 jobs

Decide what to build and why, then get it shipped.

Build the physical thing: chips, robots, spacecraft, and the machines that run them.

Get the right people to hear about the product.

Engineering jobs by location

View all locations →

See where engineering roles are concentrated, by state and city.