Program Analysis Engineer (m​/f​/d) Smarobix GmbH

We build software that gives robotics engineers clarity in complex robotic systems. Our tool makes (ROS‑based) robotic systems observable, understandable, and actionable — so developers can build safer, more capable robots with confidence. We are SMAROBIX — a team of 5 founders with complementary skill sets and different cultural backgrounds and a TU Dresden start-up. This role is part of the core team shaping the product’s foundations.

Type:
Full-time (Dresden-based preferred; hybrid welcome for EU-based candidates)

You’ll work on the static understanding of robotic systems — the point where source code, configuration, and build artifacts become a foundation the rest of the product can rely on. The focus is not on extracting data for its own sake, but on deciding what is valuable, at what level of abstraction, and why those choices remain valid as systems grow in size and complexity.

This is a hands‑on, design‑and‑build role. There is no fixed blueprint: you’ll explore solution paths, test assumptions, and converge on representations that are both technically sound and practical to ship. Much of the work sits near the limits of classical program analysis, and progress depends on clear judgement about those limits and on selecting approaches that hold up in real systems rather than idealized ones.

You bring experience with program analysis or language‑centric systems where representation and abstraction matter—whether from compiler construction, static analysis, language engineering, formal methods, or adjacent fields. You’ve worked on problems where understanding meaning across artifacts was harder than implementing the mechanics. You think carefully about models: what they capture, what they hide, and how those choices affect downstream use. You’re comfortable moving across languages and formats and don’t expect problems to arrive with prescribed methods.

Ambiguity doesn’t stall you; it sharpens your questions. While your focus is analytical, you approach the work pragmatically. The goal is always a reliable, working system. You use AI‑based methods where they help, rely on classical approaches where they’re appropriate, and are clear‑eyed about the trade‑offs between them. In a small team, you communicate clearly, work beyond narrow boundaries when it helps the product, and take responsibility for the outcomes of your design decisions.

Familiarity with robotics frameworks like ROS2, large C++ build systems, or model‑driven engineering can give you a head start, however, what we care about is genuine depth and the drive to ship. Same holds true for whether you come from academia, industry, or an unexpected path.

You won’t be maintaining an established analysis pipeline or implementing a predefined model. The foundation exists, but the important representational decisions are still open — and visible. The structures you design will sit beneath everything else the product does, and the choices you make will matter for years. You’ll work closely with the co‑founder responsible for language engineering, with real ownership and room to challenge assumptions.

This is a role for someone who wants their thinking — not just their code — to shape a product from the inside. As the team grows, this work naturally evolves into technical leadership through influence and clarity rather than hierarchy.

Send your CV and a short cover letter via E‑Mail. In your cover letter, tell us about a hard technical problem you worked on and the moment you realized your first approach was wrong — what did you do?