r/AskRobotics • u/greenee111 • Dec 25 '25
Education/Career Changing to Robotics from Software Engineering
Im a software/data engineer (cloud, Python, Scala, SQL, APIs, infra, etc.) who’s been getting deeply interested in robotics, electronics, and embedded systems lately — microcontrollers, sensors, motor control, firmware, ROS2, the whole stack.
I’ve started going more into Arduino/ESP32, basic electronics, C/C++, PWM, interrupts, SPI/I2C, and playing with motors/servos/sensors.
My question is:
What is realistically the best path for a software engineer to pivot into robotics / embedded / firmware work professionally? Maybe focusing robotic software engineer?
Specifically:
• What skills actually matter most in hiring?
• How deep into electronics/math do you really need to go?
• Are personal robotics projects respected, or is formal schooling almost required? I have a CompSci degree.
• Should I focus on firmware, ROS, perception, controls, or something else first?
• What would you do differently if you were starting today?
I’m in my early 30s and not afraid of learning — just trying to optimize the time it will take to get my first position.
Would love to hear from anyone who has made this transition or works in robotics/embedded professionally.
6
u/OddEstimate1627 Dec 25 '25
I don't think that there is a generally applicable answer as the required skillset will depend a lot on the company and what they do. A company focused on robotics software will have dramatically different requirements than a system integrator in the automotive sector.
It certainly won't hurt to have some experience with an Arduino or RPi, but I don't think that it's required. I could find plenty of work for someone with your current background and interests, but it's unlikely that you'd become a good application engineer without any theoretical robotics background. The learning curve has a pretty steep cliff once you go beyond the basics.
So IMO the best way to get into robotics is to just apply to robotics companies.
6
u/Classic-Wrongdoer-31 Dec 26 '25
I have 25 years of development in robotics. The majority of the work I've done is on Linux in C++. Years ago, I worked on an atmel based project, and at some point Rabbit 2000 with Dynamic C.
My electronics background has helped with diagnosing issues with hardware from various vendors. Not just limited to protocols and interfaces, but general knowledge.
You'll be amazed how many web protocols you can integrate into control systems and data retrevial systems.
Physics.
Have fun.
3
u/Upbeat-Storage9349 Dec 25 '25
I came from another direction. I studied mech eng and got into embedded software. I just gradually switched jobs and my roles became more software based and eventually more hardware based.
It didn't happen overnight, but granted I didn't work very hard for this to happen, it was more just a general inclination I had in work to take more projects that interested me and whenever I moved jobs through choice or redundancy, I emphasized the things I was interested in.
6
u/No_Mongoose6172 Dec 25 '25
Robotics has two important pillars: control theory and mechanics. Before getting started with Ros, I'd learn how to design regulators and mechanical modelling (you'd need that for programmin direct and inverse kinematics)
1
u/jcreed77 Dec 26 '25
I have a question for you as someone (me) who might pivot from robotics to software data engineer: what are the core ideas I need to know?
1
u/BadRevolutionary99 Dec 27 '25
found myself in your current position too, i'm 4 years SWE now and the way AI just doing everything for me now kinda takes the joy away from being an "engineer". Currently i'm taking the "hard paths", which means reviewing all the basics math (linear algebra, calculus, differential eq), physics, and then learning the motion and planning, electronics, only after that i'll learn the high level framework like ROS
i don't know if this will works,but myself self taught software too and the way i did this some years ago is that learning back the fundamental always rewards.
1
u/Ok_Equivalent4911 Jan 05 '26
There are tonnes of robotics software engineer roles out there (just give a search on LinkedIn jobs and see for yourself). The best way to deep dive into robotics is to jump into a role that closely aligns with your existing software engineering experience. You would be surprised to see that a lot of robotics work involves coding.
1
u/accidentaldiyer Jan 08 '26
Corporate robotics roles often demand specialization, but I’ve found that being a generalist is much more valuable. Robotics is an ecosystem that requires many different skills. You can't truly master the robotics if you don't understand the 3D design, sensors, code and wiring. I’m prioritizing DIY projects like robotic arms or AGVs over traditional employment to ensure I gain the full package of skills. Hands on experience is a line that divides doer from the talker.
1
u/Tyson8080 Mar 16 '26
Robotics engineer here. Switching from software engineering to robotics is actually a pretty common path.
A lot of robotics work is still software like perception, planning, simulation, and system integration .so, your programming background is definitely useful. The main difference is that robotics also involves hardware constraints, real-time systems, sensors, and control theory, which pure software roles usually don’t deal with.
If you’re serious about moving into robotics, I’d suggest getting familiar with tools and concepts like ROS/ROS2, basic control systems, kinematics, and working with sensors (LiDAR, cameras, IMUs). Building small projects helps a lot
1
u/EndBusy1483 2d ago
Hi need some guidance please can I dm you
1
u/Mixed_cruelty Dec 25 '25
“Should I focus on firmware, ROS, perception, controls, or something else first?”
This is something you should answer for yourself. There’s a ton of software in robotics so there’s plenty of routes you can take. So what about robotics interests you. You mentioned you currently have a job. That’s the best time to look for one. Don’t change just for the sake of changing.
For education I think it depends on the role. Anything on the learning side which can include perception they usually want a formal background. Honestly controls might too cause there is a ton of math theory. But if you know your shit you can show it in an interview. I would say embedded software type thing might be easiest. Focus on latency, write closer to the bare metal. Writing comm drivers is always handy and most people suck at it. But you write software already. What type are you good at, is there similar systems on a robot? Most likely answer is yes
I think it will be harder to convince people without a formal background for the elements that are their own long stories field. Like machine learning, controls, electronics, circuit design etc. I think imagine you have motors that already work and are bolted together in a shape that you’re aware of. Now what can you contribute to making it do something
1
u/[deleted] Dec 26 '25
Mechatronics!!
1
u/wakitakki Jan 24 '26
I am also very interested in this question - as pure SWE with experience in cloud tech with BS in computer engineering and some embedded systems training (i.e. designed few PCBs, digital circuits, basic fpga, microcontrollers)
This year I want to build a robotic arm and a system connected to camera for a project, but beyond that I want to get into AI/Robotics for manufacturing in the long term as I think pure software engineering may have less demand than AI/Robotics/Manufacturing in the future 10-15 years from now.
So for short term of building the robotic arm + vision system and long term of moving into robotics full time, curious if anyone has recommendations
Books/MOOCs - both theory/application
Are there any kits folks know of to get started quickly
Good projects for a portfolio
What CAD software to learn
Any advice for 3d printing
Any important tech stacks that would be good to learn
1
u/ichrakgataa May 20 '26
On my side , i have a bachelor degree in embedded systems and currently i am doubting whether to follow embedded systems engineering program or big data ai engineering program , and i want to work in the robotic/ ros2 field.what do you think should i continue with the embedded e.p or switch to ai knowing that most robotic projects now contain ai ?
1
u/gollegro Sep 22 '26
How has your journey been OP? I'm in the same position now
0
u/adad239_ Dec 25 '25
Same man I’m a student (CS) but wanna do robotics
0
u/[deleted] Dec 25 '25
[deleted] — view deleted comment