> ## Content Index
> Fetch the complete content index at: https://kello.ai/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Robotics engineer salary and skills in 2026: pay by specialism.
- URL: https://kello.ai/blog/robotics-engineer-salary/
- Published: 2026-11-04T10:57:51.000Z
- Updated: 2026-11-04T11:54:36.000Z
- Description: Robotics engineer salary by country, level and specialism, measured from 2026 job posts. For founders hiring robotics engineers: what to pay, which specialism to hire, which skills to ask for and where to find them.
- Author: Mona Gandhi
- Tags: Pay, Research, #report

Robotics engineer postings in 2026

6,606

US postings with advertised pay

1,004

Robotics engineers' careers

27,854

Data as of

4 Nov 2026

Based on 6,606 unique robotics engineer job postings from 2026, 1,004 US postings with an advertised salary range (recruiters removed), the careers of 27,854 people who hold the robotics engineer title, and self-reported salaries from Glassdoor and AmbitionBox. Data as of 4 Nov 2026.

## The short answer

The typical US robotics engineer salary in job postings is $132k to $192k, with a midpoint of $162.5k. Self-reported base pay on Glassdoor is lower, at a median of $111k. The title covers two jobs: robotics software roles advertise $152k to $220k, and postings that mention PLCs or industrial robot brands $100k to $130k. In India, AmbitionBox puts the median CTC at ₹4.25L, mostly for industrial automation roles.

## 01 · The shift Robotics engineer is one title for two jobs, and they pay very differently.

**A robotics engineer at a humanoid startup and one programming a car plant's robot cells share a title, but their advertised pay ranges don't overlap.** The robotics engineer salary you need to pay depends on which end of the job you hire for.

**What is a robotics engineer?** A robotics engineer designs, builds and programs robots: the software that lets a machine sense, plan and move, and often the hardware it runs on. In job postings the title covers two jobs: robot software and AI, and industrial automation (robot cells and PLCs).

In the US, robotics engineer postings that mention PLCs or industrial robot brands such as FANUC, ABB or KUKA advertise $100k to $130k (143 postings). The rest advertise $137k to $200k (861), and postings with "software" in the title $152k to $220k. At the midpoint, industrial robot roles advertise less than entry-level robotics roles: $117k against $120k.

| US robotics engineer postings                 | Midpoint ($k) | Postings |
| --------------------------------------------- | ------------- | -------- |
| "Software" in the title                       | 185           | 253      |
| Don't mention PLCs or industrial robot brands | 170           | 861      |
| All postings                                  | 162.5         | 1004     |
| Mentions PLCs or industrial robot brands      | 117           | 143      |

Source: Kello jobs index, unique 2026 US robotics engineer postings with an advertised annual range, recruiters and job boards excluded · Data as of 4 Nov 2026

**The work inside the title is split between AI and the factory floor.** Of 6,606 robotics engineer postings from 2026:

- 9.4% mention robot learning (robot, reinforcement or imitation learning), and 8.9% mention humanoids.
- 24.6% mention machine learning, and 15.7% simulation tools such as Gazebo, Isaac Sim and MuJoCo.
- 13.9% mention PLCs, and 11.7% name industrial robot brands such as FANUC, ABB or KUKA.

The two ends pay very differently (chapter 05).

## 02 · The race Startups and big companies compete for the same robotics engineers.

**Your competition is split between small companies and very large ones.** We tied 2,937 of the 6,606 robotics engineer postings from 2026 to a real employer of known size, after removing 1,006 posted by recruiters and job boards and those with a wrong or missing employer. Of those, 42.3% came from companies with 200 or fewer people (24.7% from 1 to 50) and 31.2% from companies with more than 10,000\. Amazon alone posted 295\. Domain-matched startups posted 649 roles across 322 companies.

**The people are mostly somewhere else.** Of 27,854 people who hold the robotics engineer title, only 9.1% work at startups and 16.5% at very large companies. The biggest employer industries are automation machinery manufacturing (13.1%), robotics (8.0%), software (6.9%) and car makers (4.9%).

**The top of the pay market is a handful of big tech companies.** US postings from companies with more than 10,000 people advertise $160k to $240k, but that's 71 postings from 18 employers, and Meta posted 35% of them. Startups advertise $147.5k to $210k, across 46 postings from 27 startups.

**Our view:** a seed-stage robotics startup competes with other robotics startups for the same small pool, and with a few large companies at the top of the pay range. A generic "robotics engineer" posting won't stand out. Name the specialism, pay what that specialism costs, and search outside the title.

## 03 · Winning What a good robotics engineer hire looks like.

**Our view: hire for the problem your robot has to solve first, not for the title.** A humanoid company that needs its robot to learn a task needs a robot learning engineer. A company automating a factory line needs an engineer who programs robot cells and PLCs. Both are called robotics engineers, and they cost very different amounts (chapter 05).

**Plan for hardware and software from day one.** At 1,532 early- and growth-stage robotics startups, 2,453 current roles are in software engineering and 2,099 in mechanical, electrical or mechatronics engineering. Only 248 of the 11,597 current roles there, 2.1%, carry the exact title "Robotics Engineer". If you search only for that title, you miss most of the people doing the work.

Four problems usually stand in the way:

- We don't know what to pay.
- We don't know which specialism we need.
- We don't know which skills to ask for.
- There's no one with the title.

Which ones matter most depends on what you're building:

| If you…                                    | What the data shows                                                                                                              | Start with         |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
| Build humanoids or robots that learn       | US robotics postings that mention robot learning have a median midpoint of $218k, against $160k for those that don't.            | Chapters 05 and 06 |
| Build industrial automation or robot cells | US robotics postings that mention PLCs or industrial robot brands advertise $100k to $130k, against $137k to $200k for the rest. | Chapter 05         |
| Are hiring your first engineer             | 29.7% of founding engineers at hardware startups came from physical engineering roles.                                           | Chapter 07         |
| Can't match big-company pay                | Startups advertise $147.5k to $210k. Reported base pay is about the same at every company size: $111k to $116k.                  | Chapter 04         |
| Hire in India                              | The median robotics engineer has 2.7 years of experience, and the ₹4.25L median CTC mostly reflects industrial automation roles. | Chapters 04 and 07 |

## 04 · Salary Robotics engineer salary: $132k to $192k in the US.

**If you don't know what to pay, start from the advertised range: $132k to $192k in the US.** That's the median bottom and median top of the range across 1,004 US robotics engineer postings from 2026 that state pay, after removing 232 posted by recruiters and job boards. The median midpoint, the closest thing to an average robotics engineer salary, is $162.5k. The middle half of postings have a midpoint between $125k and $200k.

| US robotics engineer postings                 | Typical advertised range | Postings |
| --------------------------------------------- | ------------------------ | -------- |
| Entry level                                   | $100k to $140k           | 100      |
| Associate                                     | $96k to $125k            | 72       |
| Mid-senior level                              | $140k to $194k           | 530      |
| Senior, staff, principal or lead in the title | $150k to $220k           | 341      |
| Robotics software engineer                    | $152k to $220k           | 253      |
| All robotics engineer postings                | $132k to $192k           | 1,004    |

*Source: Kello jobs index, unique 2026 US robotics engineer postings with an advertised annual range, interns, recruiters and job boards excluded · Data as of 4 Nov 2026\. Levels are the employer's own seniority label, except the title row. These are advertised ranges, not final offers.*

**Self-reported salaries give a second, lower lens.** On Glassdoor, US robotics engineers report a median base salary of $111k, across 2,112 salaries at 670 companies in records updated in 2025 or 2026\. The middle half of company-level medians runs from $101k to $126k, plus a median of $8,750 in bonus and other pay where people report it. Titles with "software" report $121k, and senior, staff, principal or lead titles $134k.

Advertised ranges show what employers posting now offer, and skew to US states that require pay in postings. Reported pay is base salary people already hold, reported over several years, across every kind of employer that uses the title. Treat advertised pay as the offer you compete with, and reported pay as what a candidate probably earns today.

**The starting salary for a robotics engineer is about $100k.** Entry-level postings advertise $100k to $140k. A quarter of all US postings start at $100k or less, and a quarter reach $240k or more at the top.

**Experience moves the range up steadily.** Postings asking for 2 to 3 years advertise $125k to $170k, 4 to 5 years $130k to $185k, 6 to 7 years $146k to $218k (a small sample of 45), and 8 or more years $151k to $222k. The typical US posting asks for 5 years. The people who hold the title have more: a median of 6.6 years in the US.

**"Robotics software engineer" is the better-paid part of the title.** Postings with "software" in the title advertise $152k to $220k. Other robotics engineer titles advertise $121k to $181k. Chapter 05 breaks the title down by specialism.

**Startups already advertise above the overall range.** Domain-matched startups advertise $147.5k to $210k (46 postings from 27 startups; the largest posted 15% of them). Companies with more than 10,000 people advertise $160k to $240k, but 71 postings from 18 employers, with Meta at 35% and Intuitive at 20%, so read that as a few big tech companies rather than all large employers. Reported base pay barely moves with size: a median of $111k at companies with 1 to 50 employees, $116k at 51 to 200 and $111k at 10,000+. Our reading: a startup can match the market on base pay; the very top of the range is a few companies.

**Where you hire in the US matters as much as the level.** Our reading: Bay Area robotics roles lean towards AI and autonomy, and Michigan's towards car-industry automation.

| US city                 | Typical advertised range | Postings |
| ----------------------- | ------------------------ | -------- |
| San Francisco           | $150k to $224k           | 133      |
| San Jose                | $149k to $221k           | 63       |
| Seattle                 | $150k to $204k           | 43       |
| Boston                  | $120k to $175k           | 57       |
| Austin                  | $113k to $157k           | 34       |
| Michigan (Detroit area) | $90k to $106k            | 50       |

*Source: Kello jobs index, unique 2026 US robotics engineer postings with an advertised annual range, recruiters and job boards excluded, by posting location · Data as of 4 Nov 2026\. One employer posted 30% of the Seattle postings, 25% of Boston's and 19% of San Jose's. Los Angeles isn't shown: one employer posted 60%.*

**Outside the US, we only publish India.** In the UK, 23 of the 25 robotics postings that state pay came from recruiters, and in Australia 10 of 13\. Glassdoor holds no robotics engineer salaries for either country updated in 2025 or 2026.

| Country | Advertised pay (job postings)   | Reported pay (self-reported)                    |
| ------- | ------------------------------- | ----------------------------------------------- |
| US      | $132k to $192k (1,004 postings) | Median base $111k (2,112 salaries, Glassdoor)   |
| India   | ₹4L to ₹6.75L (84 postings)     | Median CTC ₹4.25L (2,797 salaries, AmbitionBox) |

*Source: Kello jobs index, unique 2026 robotics engineer postings with an advertised annual range, recruiters and job boards excluded; Glassdoor (US, records updated in 2025 or 2026) and AmbitionBox (India) self-reported salaries, weighted by the number of salaries, no company above 10% · Data as of 4 Nov 2026.*

**In India, the title mostly means industrial automation.** On AmbitionBox, robotics engineers in India report a median CTC of ₹4.25L: ₹3.75L with 0 to 3 years of experience, ₹5.25L with 4 to 7 years and ₹7.75L with 8 or more. That's after removing profiles that are a different job (robotic process automation, simulation, service, production and trainee roles) and employers in education and staffing. The biggest employers behind it are car-parts makers, a construction-equipment maker and automation integrators. Robot software profiles are too few to measure (9 salaries). The 84 Indian postings with pay are a mix too: school robotics trainers, car-plant robot programmers and a few robot software roles at startups.

So read ₹4.25L as the floor for industrial robotics roles, not as the price of a robot software engineer. For software that runs on robot hardware, our [embedded software engineer guide](https://kello.ai/blog/embedded-software-engineer/) is a closer reference: embedded and firmware engineers in India report a median CTC of ₹5.75L, and ₹9.75L with 4 to 7 years.

**India's figures also reflect a younger pool.** The median robotics engineer in India has 2.7 years of experience, against 6.6 in the US and 5.9 in the UK.

What this gets you

A budget you can defend. In the US, budget $132k to $192k for a robotics engineer, $100k to $140k for entry level and $150k to $220k for a senior hire. In India, use ₹3.75L to ₹7.75L CTC by experience for industrial roles, and expect to pay more for robot software. Then adjust for the specialism in chapter 05.

## 05 · Specialism Robotics engineer salary by specialism: robot learning pays most.

**Not sure which specialism you need? Decide it before you set the budget, because it moves the salary as much as location does.** Inside US robotics engineer titles, roles with learning, ML, AI or research in the title have a median midpoint of $202.5k. Plain "robotics engineer" titles have $127.5k, and field service roles $97.5k.

| Title contains               | Midpoint ($k) | Postings |
| ---------------------------- | ------------- | -------- |
| Learning, ML, AI or research | 202.5         | 109      |
| Software                     | 185           | 253      |
| Controls                     | 175           | 67       |
| Autonomy or navigation       | 165           | 57       |
| Perception or vision         | 162.5         | 38       |
| Mechanical or hardware       | 161.5         | 109      |
| Automation or integration    | 130           | 111      |
| No specialism word           | 127.5         | 229      |
| Field service                | 97.5          | 38       |

Source: Kello jobs index, unique 2026 US robotics engineer postings with an advertised annual range, recruiters and job boards excluded · Data as of 4 Nov 2026

| Robotics engineer title contains        | What the robot needs                                               | Typical US range |
| --------------------------------------- | ------------------------------------------------------------------ | ---------------- |
| Learning, ML, AI or research            | Learn tasks from data, demonstrations or simulation                | $152k to $244k   |
| Software                                | Run the whole software stack, often on ROS                         | $152k to $220k   |
| Controls                                | Move precisely and stay balanced: motors, actuators, control loops | $130k to $201k   |
| Autonomy or navigation                  | Operate on its own (vehicles, drones, mobile robots)               | $115k to $200k   |
| Perception or vision                    | See and understand its surroundings (cameras, lidar)               | $130k to $200k   |
| Mechanical, mechatronics or hardware    | A body, arms and grippers that work                                | $120k to $186k   |
| Automation, integration or applications | Fit robots into a factory line or robot cell                       | $102k to $154k   |
| Field, service or technician            | Keep installed robots running at customer sites                    | $80k to $110k    |

*Source: Kello jobs index, unique 2026 US robotics engineer postings with an advertised annual range, recruiters and job boards excluded · Data as of 4 Nov 2026\. Every posting has "robotics" or "robotic" and "engineer" in the title; the specialism is another word in the same title, and a title can fall in two groups. One employer posted 21% of the autonomy postings and 16% of the controls postings. Manipulation (19), simulation (25), embedded or firmware (21) and planning (14) titles are too few to show. For embedded and firmware roles in general, our embedded guide puts US advertised pay at $127k to $177.7k (3,213 postings).*

**Controls engineers sit mostly in the better-paid market.** Chapter 01 shows the gap between industrial robot roles and the rest. Most robotics controls titles sit on the higher side: 50 of 67 don't mention PLCs or those brands, and they advertise $141k to $210k. Postings that mention humanoids or legged robots, and not PLCs, advertise $144k to $227k (153 postings). If your robot has to walk or balance, budget from that range, not from the industrial one.

**Robot learning is where the competition is hottest.** It's the best-paid end of the role: US postings that mention robot learning advertise $152k to $272k (98 postings). A humanoid or robot learning startup should budget from $152k to $244k, the range for learning, ML and AI titles, not from the overall robotics engineer range.

**Our view: hire a generalist robotics software engineer first, unless your product's main risk sits in one specialism.** At seed, your first engineer has to get a robot running end to end, and robotics software roles advertise $152k to $220k, against $152k to $244k for learning, ML and AI titles. Go straight to a specialist when that specialism is what you're selling. A humanoid or manipulation company whose robot must learn tasks should hire robot learning first, and expect to pay at the top of the market for it. If your robot has to walk or balance, hire its controls engineer early too, from the robotics market rather than the industrial one.

What this gets you

A budget that matches the job. Write down the first problem your robot has to solve, pick the specialism from the table, and budget from its range. If you need robot learning, start from $152k. If you need controls for a robot that moves like a person, budget from $144k to $227k, not the $100k to $130k of industrial robot roles.

## 06 · Skills Robotics engineer skills: Python and ROS, then the specialism.

**If you don't know which skills to ask for, start from what the market asks.** Across 6,606 robotics engineer postings from 2026, the most mentioned skills are Python (53.2%), controls (39.1%) and ROS (37.1%). We don't report C++: our text search can't tell it apart from C.

| Skill                                        | Share of postings that mention it |
| -------------------------------------------- | --------------------------------- |
| Python                                       | 53.2%                             |
| Controls (control systems, PID, MPC)         | 39.1%                             |
| ROS or ROS 2                                 | 37.1%                             |
| Embedded, firmware or microcontrollers       | 31.1%                             |
| Perception                                   | 30.1%                             |
| ROS 2                                        | 26.6%                             |
| Machine learning or deep learning            | 24.6%                             |
| Motion or path planning                      | 21.1%                             |
| Computer vision                              | 18.6%                             |
| SLAM or localization                         | 16.2%                             |
| Simulation tools (Gazebo, Isaac Sim, MuJoCo) | 15.7%                             |
| Sensor fusion                                | 14.0%                             |
| PLC                                          | 13.9%                             |
| Robot learning                               | 9.4%                              |
| MATLAB or Simulink                           | 5.1%                              |

*Source: Kello jobs index, descriptions of unique 2026 robotics engineer postings, all countries · Data as of 4 Nov 2026\. A mention isn't always a requirement.*

**Some skills mark the top of the market, and some the bottom.** In US postings with advertised pay, here's the median midpoint for postings that mention each skill, against those that don't:

| Skill                   | Mentions it ($k) | Doesn't ($k) |
| ----------------------- | ---------------- | ------------ |
| Robot learning          | 218              | 160          |
| Humanoid                | 198              | 160          |
| Sensor fusion           | 190              | 162          |
| Machine learning        | 186              | 151          |
| PhD                     | 182              | 155          |
| Perception              | 175              | 155          |
| Python                  | 170              | 150          |
| ROS                     | 168              | 162          |
| MATLAB                  | 168              | 162          |
| PLC                     | 122              | 168          |
| Industrial robot brands | 111              | 168          |

Source: Kello jobs index, 1,004 unique 2026 US robotics engineer postings with an advertised annual range, recruiters and job boards excluded · Data as of 4 Nov 2026

**ROS barely moves pay.** Postings that mention it advertise only 4.0% more, so asking for it tells a candidate little about the job. Ask for ROS 2 if you use it: 26.6% of 2026 postings mention it.

**Machine learning marks the top of the market.** Postings that mention it advertise 23.7% more ($186k against $151k), and those that mention robot learning 36.1% more. Postings that mention PLCs advertise 27.7% less.

**Leave MATLAB out unless you use it.** It appears in 5.1% of postings, while 16.1% of robotics engineers list it. It barely moves pay (3.9%).

**Ask for a PhD only for research work.** 14.1% of postings mention a PhD, and in the US they advertise more ($182k against $155k), but only 6.1% of people in the role have a doctorate. A PhD requirement on a robotics software role cuts your pool hard.

**Startups ask for different skills from large companies.** Across 649 postings from 322 startups, startup postings mention ROS (45.8% against 27.0%), Python (67.6% against 44.9%), perception (37.9% against 25.1%) and SLAM (19.6% against 13.1%) more than postings from companies with over 1,000 people. They mention a master's degree less (16.6% against 31.3%). Amazon posted a quarter of the large-company roles; without it the gaps narrow but hold (ROS 33.0%, master's 31.8%).

What this gets you

A job description that attracts the right market. Ask for Python as the base, C or C++ if your robot runs it, ROS 2 if you use it, and then two or three skills from your specialism: robot learning, perception and SLAM, or motion planning. Leave out MATLAB and a PhD unless the work needs them. If the role is industrial controls, say so, so the right people apply.

## 07 · Sourcing How to hire a robotics engineer: look past the title.

**"There's no one with the title" usually means searching for the title.** Most robotics engineers at startups held a different title in their previous job, and startups hire from different places than large companies do.

### Where startups find their robotics engineers.

**The employers they came from.** For people whose current title is robotics engineer, here's the kind of employer they worked for just before, at startups and at large companies:

| Previous employer                           | US startups | US large companies | Startups, all countries |
| ------------------------------------------- | ----------- | ------------------ | ----------------------- |
| An early- or growth-stage startup           | 32.4%       | 6.4%               | 32.9%                   |
| A large company                             | 32.6%       | 66.7%              | 27.4%                   |
| A company of 200 people or fewer            | 42.6%       | 23.0%              | 53.0%                   |
| A university or research organisation       | 27.6%       | 15.1%              | 23.3%                   |
| A robotics or industrial automation company | 18.2%       | 13.7%              | 20.9%                   |
| Software, internet or IT services           | 13.7%       | 14.6%              | 17.4%                   |
| Defence, aerospace or space                 | 7.8%        | 7.1%               | 6.4%                    |
| Medical and health                          | 5.9%        | 10.9%              | 4.5%                    |
| A car maker or automotive supplier          | 4.5%        | 9.6%               | 4.6%                    |
| Median time in that job                     | 19.0 months | 26.4 months        | 17.8 months             |
| Left it within a year                       | 31.0%       | 24.5%              | 34.9%                   |
| People with a previous job                  | 756         | 2,487              | 2,326                   |

**The roles they held.** And here's the title of the role they held there:

| Previous role                                                     | US startups | US large companies | Startups, all countries |
| ----------------------------------------------------------------- | ----------- | ------------------ | ----------------------- |
| Robotics engineer (or another robotics title)                     | 26.3%       | 19.2%              | 27.5%                   |
| Software engineer or developer                                    | 19.3%       | 12.7%              | 19.2%                   |
| Research or scientist title                                       | 16.8%       | 10.3%              | 12.3%                   |
| PhD, postdoc or research assistant                                | 10.1%       | 5.8%               | 5.9%                    |
| Internship or co-op                                               | 10.8%       | 8.4%               | 12.1%                   |
| Mechanical or mechatronics engineer                               | 5.2%        | 5.6%               | 3.7%                    |
| Teaching                                                          | 4.4%        | 2.5%               | 2.9%                    |
| Electrical, electronics or hardware engineer                      | 3.6%        | 3.0%               | 3.0%                    |
| Machine learning, AI or perception                                | 3.1%        | 1.4%               | 3.3%                    |
| Controls engineer                                                 | 2.5%        | 3.8%               | 1.6%                    |
| Automation or PLC                                                 | 2.2%        | 4.4%               | 2.2%                    |
| *By function: mechanical, electrical or mechatronics engineering* | 34.3%       | 43.2%              | 34.9%                   |
| *By function: software engineering*                               | 29.3%       | 18.4%              | 31.9%                   |
| Previous roles counted                                            | 989         | 3,312              | 2,919                   |

*Source: Kello career data, people whose current title contains "robotics" or "robotic" and "engineer" at early- or growth-stage startups (800 in the US, 2,625 worldwide) or at large companies (2,879 in the US), and the job they held just before · Data as of 4 Nov 2026\. Employer shares are of previous jobs whose stage, size or industry is known. Title shares are of previous roles; a title can fall in two groups, and many titles fall in none. Function comes from Kello's classification of each role, which is broader than the title words. Groups under 20 people aren't shown.*

**What's different about startup hires.** Against people with the same title at large companies, US startup robotics engineers came five times as often from another startup (32.4% against 6.4%), and much more often from a university or research organisation (27.6% against 15.1%). Their previous role was more often a software, research or PhD and lab role, and less often at a car maker or a medical company. They had also spent less time in their previous job: a median of 19.0 months, against 26.4.

**Our reading:** startups rarely hire robotics engineers straight out of large manufacturers. They hire people already used to small teams, from other startups, and people coming out of research, often with a software background. Searching large car and automation companies first means searching where large companies hire.

**Degrees.** Of 2,635 robotics engineers at startups worldwide, 48.9% have a master's degree and 7.7% a doctorate. The most common degree is mechanical engineering (16.1%), ahead of mechatronics and robotics (7.3%) and computer science (6.7%).

**They are earlier in their careers.** Startup robotics engineers are a little earlier in their careers than the whole field: a median of 4.6 years of experience, against 5.1\. In the US it's 6.0 years, and in India 2.3.

**Hiring your first engineer? Include hardware engineers.** Our [founding engineer guide](https://kello.ai/blog/how-to-hire-a-founding-engineer/) found that 29.7% of founding engineers at hardware startups came from physical engineering roles, against 1.0% at software startups. A mechanical or electrical engineer who has written robot software is often a better first hire than a software engineer who hasn't touched hardware.

**Search where they live.** The cities with the most robotics engineers are Pune (846), Bengaluru (814), San Francisco (777), Chennai (450), Singapore (412), Boston (391), Hyderabad (300) and Munich (274), with Los Angeles and Pittsburgh (188 each) next in the US. At startups, Bengaluru (138) and San Francisco (133) lead, followed by Los Angeles (56), Hyderabad (45), and Chennai and Munich (43 each).

### Boolean search strings for LinkedIn.

Paste these into LinkedIn's keyword search, or into Google with `site:linkedin.com/in` in front. Then read each person's role descriptions for the robot work, whatever their title.

```
("robot learning" OR "imitation learning" OR "reinforcement learning" OR "embodied AI") AND (robot OR robotics OR manipulation OR humanoid)
```

```
(perception OR "computer vision" OR SLAM OR "sensor fusion") AND (robot OR robotics OR autonomy OR lidar) AND ("C++" OR ROS)
```

```
("mechanical engineer" OR "electrical engineer" OR "mechatronics engineer" OR "embedded engineer") AND (ROS OR "C++" OR Python) AND (robot OR robotics)
```

What this gets you

A search plan in the order the data supports. First, robotics engineers at other startups. Second, university labs: PhD students, postdocs, research assistants and master's graduates. Third, software engineers and developers who have worked on robots. Fourth, mechanical, electrical and mechatronics engineers who write robot software. Search large car makers, medical-device companies and automation integrators last: that's where large companies hire.

## Putting it together: one founder's plan.

**Daniel has just raised a seed round for a humanoid robotics startup in the US.** He has a mechanical co-founder and needs his first robotics engineers. Daniel is a fictional founder; every figure comes from the chapters above.

1. **The specialism.** His robot first has to learn to pick up objects, so he hires for robot learning, then perception (chapter 05).
2. **The salary.** He budgets from the range for learning, ML and AI titles, $152k to $244k, not the overall $132k to $192k (chapters 04 and 05).
3. **The skills.** His posting asks for Python, C++ and ROS 2, plus imitation learning and simulation. It leaves out MATLAB and doesn't require a PhD (chapter 06).
4. **The search.** He searches robot learning labs and master's graduates, other robotics startups and software engineers who have worked on robots, then mechanical engineers who write robot code (chapter 07).
5. **The second hire.** For the controls engineer who'll make the robot walk, he budgets from the range for humanoid and legged-robot postings, $144k to $227k, not the $100k to $130k of industrial robot roles (chapter 05).

## How we know, and how Kello can help.

This guide is based on 6,606 unique robotics engineer job postings from 2026, 1,004 US postings with an advertised salary range after removing recruiters and job boards, and the careers of 27,854 people whose current title is robotics engineer, including 2,635 at early- and growth-stage startups. Data as of 4 Nov 2026.

Robotics engineer postings are those whose title contains "robotics" or "robotic" and "engineer", posted from 1 Jan to 31 Oct 2026, with internships excluded and each posting counted once however often it was reposted. Robotic process automation titles (software bots, not robots) are excluded from pay and people figures. Every figure states its country.

Advertised pay is the median bottom and median top of advertised annual ranges; the midpoint is the median of each posting's midpoint. They are advertised ranges, not offers. Postings from staffing firms, recruiters and job boards are removed from every pay figure, and from employer, size and startup figures we also remove postings whose employer we couldn't match reliably. Company size is the largest headcount in Kello's company data for the employer's web domain. Startups are employers tagged as early- or growth-stage startups in Kello's company data, matched by domain. When one employer posted more than about 15% of a group, we say so. Specialisms are a second word in the robotics engineer job title, and the groups overlap. Skill shares are phrase mentions in the job description, so a mention isn't always a requirement; we don't report C++, because our text search reads "C++" as "C".

Reported pay comes from self-reported salaries. Glassdoor: base pay for job titles containing "robotics" or "robotic" and "engineer", US, annual, regular employees, records updated in 2025 or 2026, process automation titles removed. AmbitionBox: CTC for robotics engineer profiles in India, with profiles that are a different job removed (process automation, simulation, service, production, application and trainee) and employers in education and staffing removed. Both are weighted by the number of salaries, with no company above 10% of a group, and read from pay bands, so each median is accurate to within half a band ($1,250 or ₹25,000). Glassdoor spreads are spreads of company-level medians. Groups under 20 salaries aren't shown.

People figures cover people whose current title contains "robotics" or "robotic" and "engineer", by their current country; startups are companies tagged as early- or growth-stage startups in Kello's company data, and robotics startups are those whose industry is robotics engineering. Previous-role shares are shares of roles, not people. Previous employers are grouped by industry and size in Kello's company data; industries are grouped by hand (for example, robotics, automation machinery and industrial machinery are one group). Large companies are those tagged as large enterprises or mega corporations. Title groups match words in the previous role's title. The search strings are starting points we wrote from these findings, not tested queries. A posting is a plan to hire, not a hire. The advice in each chapter, marked "Our view" or "Our reading", is our interpretation of these figures.

Kello uses the same data to find robotics engineers for companies like yours. Send us the role, and your shortlist usually arrives in about two hours. Most roles have people ready to interview within 7 days.

**Hiring a robotics engineer? [Send Kello the role.](https://kello.ai/get-started?ref=kello.ai) Your first role is free.**

Hiring the engineers who work closest to the hardware? Read our guides to [embedded software engineers](https://kello.ai/blog/embedded-software-engineer/) and [FPGA engineers](https://kello.ai/blog/fpga-engineer/).

Hiring your first engineers? Read our [founding engineer guide](https://kello.ai/blog/how-to-hire-a-founding-engineer/). Hiring engineers to deploy robots at customer sites? Read our [forward deployed engineer hiring guide](https://kello.ai/blog/forward-deployed-engineer-hiring-guide/).

### Updates

- 4 Nov 2026 First published.

## Questions.

#### What does a robotics engineer do?

A robotics engineer designs, builds and programs robots: the software that lets a machine sense, plan and move, and often its hardware. The title covers two jobs. One is robot software and AI at robotics and autonomy companies; the other is industrial automation, programming robot cells and PLCs at manufacturers.

#### How much does a robotics engineer make?

US robotics engineer postings advertise $132k to $192k, and entry-level postings $100k to $140k. On Glassdoor, US robotics engineers report a median base salary of $111k. Robotics roles with learning, ML or AI in the title advertise $152k to $244k, robotics software roles $152k to $220k, and postings that mention PLCs or industrial robot brands $100k to $130k.

#### What is the average salary for a robotics engineer?

In the US, the median midpoint of advertised robotics engineer salary ranges is $162.5k, across 1,004 postings from 2026\. Self-reported base pay is lower: a median of $111k across 2,112 Glassdoor salaries. Robotics software engineer postings advertise $152k to $220k.

#### What is the robotics engineer salary in India?

Robotics engineers in India report a median CTC of ₹4.25L on AmbitionBox, across 2,797 salaries: ₹3.75L with 0 to 3 years of experience, ₹5.25L with 4 to 7 and ₹7.75L with 8 or more. Most of these are industrial automation roles at car-parts makers and automation integrators; robot software roles at startups usually pay more. Indian job postings advertise ₹4L to ₹6.75L.

#### What skills do you need to be a robotics engineer?

Python (53.2% of postings) is the base, followed by controls (39.1%) and ROS (37.1%), with C or C++ for software that runs on the robot. Then come specialism skills: perception, motion planning, SLAM, simulation and robot learning. Postings that mention robot learning or humanoids pay the most.

#### What degree do you need to be a robotics engineer?

The most common field is mechanical engineering (12.8%), followed by mechatronics, robotics and automation (7.1%) and computer science (5.3%). 71.8% have a bachelor's degree, 37.3% a master's and 6.1% a doctorate.

#### Where do robotics engineers work?

Across many industries. The biggest employer industries are automation machinery manufacturing (13.1%), robotics (8.0%), software (6.9%) and car makers (4.9%). 9.1% work at startups. The largest cities are Pune, Bengaluru, San Francisco, Chennai, Singapore and Boston.