Junior Robotics Engineer

Aeolus Robotics; Wien; On-site; EUR 38,000 - 60,000; Full time

Job summary

Aeolus Robotics in Vienna, Austria, is hiring a Junior Robotics Engineer to work across our robotics stack, with close mentorship and hands-on development on real hardware in the lab.

You will debug components, analyze logs, and help turn research code into reliable production code while collaborating with mentors and other teams. Fresh graduates with practical robot experience are welcome.

Qualifications

• Solid CS fundamentals and practical knowledge of complexity, data structures, memory handling, and basic concurrency.
• Enough C++ to read and reason about a large codebase; roughly 90% of our code is C++.
• Working knowledge of Git.
• Strong ability to learn quickly and adapt to new technologies.
• Good written and spoken English.

Responsibilities

• Debug and maintain components across the robotics stack.
• Investigate and troubleshoot robot failures by analyzing logs and telemetry.
• Help take research code (e.g., grasping pipelines) toward reliable production.
• Write production code with mentorship on conventions.
• Support other teams with tooling, experiments, and automation.

Skills

C++

Git

English

Robotics fundamentals

Education

BSc or MSc in a relevant field

Tools

ROS1/ROS2

Job description

About Us

9 Years. 50+ Engineers. Zero Hype.
Aeolus Robotics builds autonomous service robots that operate in dynamic human spaces worldwide. We’ve been through the full arc of hardware development: the early days of flashy CES booths, the humbling reality of real-world field deployments, and the years of relentless engineering focus required to build true system stability.

After hardening our hardware and software stack against the messy reality, we are expanding our fleet with a battle-tested team and a mature product. We aren't here to sell ungrounded promises or CGI prototypes. We engineer quiet, high-ROI, rock-solid service robots designed for customers who expect real-world execution.

Role Overview

As a Junior Robotics Engineer, you will join us as a generalist and work across our robotics stack rather than being locked into a single specialty. You will learn the codebase and the systems from the ground up under close mentorship, contributing wherever you are needed most: debugging real robots, hardening code, and taking on new work as you grow. This is a hands-on role with real hardware in the lab, and you may help resolve issues coming from live customer deployments.

What You Will Do

• Debug and maintain existing components across the robotics stack
• Investigate and troubleshoot robot failures by analyzing logs and telemetry, forming and testing hypotheses
• Help take promising research code (e.g., grasping and manipulation pipelines) from a rough prototype toward something reliable enough to ship
• Write new production code as you ramp up, with mentorship on our conventions
• Support other teams with tooling, experiments, and automation

Who We Are Looking For

The single most important thing we want to see is genuine, hands-on immersion in robotics, not just relevant coursework. Ideally you have:

• Spent real time in a robotics lab, competition team, or equivalent, working alongside peers and more senior people
• Been exposed to the messy reality of robotics: hardware that misbehaves, sensors that lie, debugging on real systems
• Some awareness of where the robotics field is today, beyond what a curriculum covers
• Fresh out of university is completely fine, but in that case we expect RoboCup or equivalent: a serious robotics competition, or a lab project that actually ran on real hardware.

Location

Vienna,Austria (in-office, no remote work)

Must be eligible to live and work in Austria

Education

BSc or MSc in a relevant field

Experience

Junior; fresh graduates welcome, provided they bring hands-on experience with real robots

CoreSkills

Solid CS fundamentals; enough C++ to read and reason about a large codebase

RoboticsStack

Practical ROS1/ROS2 exposure is a plus

Mandatory Requirements

• Solid computer science fundamentals: a practical, working command of complexity, data structures, how a computer handles memory, and basic concurrency (not competitive-programming or from-scratch-algorithm skill)
• Enough C++ to read and reason about a large codebase, and the ability to become genuinely comfortable in it quickly (roughly 90% of our code is C++, so you will live in it)
• Working knowledge of Git
• Strong ability to learn quickly and adapt to new technologies
• Grit, delivery focus, and systematic problem-solving
• Good written and spoken English

Preferred Requirements

• Familiarity with ROS1 or ROS2, or similar message-passing frameworks
• Python for scripting, experimentation, and data analysis
• Background in any relevant robotics subfield (e.g., perception/vision, manipulation, navigation, planning, or machine learning)
• Comfort with the math these fields rest on (linear algebra, 3D geometry)
• Experience with common robotics, vision, or ML libraries (e.g., OpenCV, PCL, PyTorch)
• Autonomy Built on Trust: We aim for high domain ownership and minimal micromanagement. Newer hires or juniors get closer guidance early on, but as trust is built, you get full room to run.
• Fast PoCs, Rigorous Production: Build scrappy prototypes fast to prove value on physical hardware. Once greenlit, switch to extreme rigor—because this code runs autonomously around real people.
• Radical Accountability: When something breaks, no hiding or blame-game. Own it candidly, fix it fast, and re-engineer the system so it never happens again.
• Data Over Ego: No politics, no bureaucracy. Technical truth is decided by physics, telemetry, and test data—the best idea wins regardless of title or tenure.
• Global & Hands-On Collaboration: Work with a lean, cross-functional team across Vienna lab and multiple other locations, keeping tight feedback loops on real robots.

Why This Role Matters

A lot of what separates a robotics prototype from a product that runs 24/7 in the real world is not the first exciting demo; it is the debugging, hardening, and relentless follow-through that come after. That work is essential, and it is where you will have impact from early on. Chasing down why a robot failed on-site, or dragging a promising research pipeline from "works in the paper" to "works reliably enough to ship," is exactly the kind of problem you will own here, with the scope of what you take on growing as fast as you do.

This is also a deliberate investment in you. Rather than boxing you into one corner, we want you to gain breadth across vision, manipulation, and real-robot systems, with close mentorship from people who have done it. If you have spent time where robots are actually built and broken, and you want to learn serious robotics engineering somewhere that will invest in you, we would like to hear from you.