We build software that gives robotics engineers clarity in complex robotic systems. Our tool makes (ROS‑based) robotic systems observable, understandable, and actionable. Like this, 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.

THE ROLE

You’ll own the user-facing layer of the product, the point where architectural decisions and system insight become useful to engineers. That includes shaping component structure, data flow, interaction patterns, and performance characteristics, in close collaboration with the rest of the team. This is a hands‑on, design‑and‑build role. There is no fixed blueprint: you’ll help define the architecture, make trade‑offs explicit, and evolve solutions as the product grows. The work sits at the intersection of complex state, live data, and developer experience, and requires sound judgment more than rigid adherence to patterns.

WHAT WE’RE LOOKING FOR

You bring experience building complex, stateful applications where the data model is as demanding as the UI such as developer tools, visualization software, or technical platforms. You’re open to modern tools and know when they actually help, rather than avoiding them or reaching for them by default. You’ve made architectural decisions before and understand their long‑term consequences. You’re comfortable thinking in systems, not just screens. UX for technical users matters to you, and you approach it deliberately, through information structure, interaction design, and clarity, not decoration. You think in user stories and user journeys to structure that work, not as process overhead but as a way to stay grounded in what users actually need. While your focus is the frontend, you’re at ease crossing boundaries: reading backend code, understanding interfaces, and occasionally contributing where it makes sense. You care about reliability, test what users touch, and communicate clearly with engineers from different disciplines. You’re comfortable not having all the answers, as what matters is the clarity to say so and come back with a considered one. Finally, you are drawn to environments where design and engineering overlap; where the question isn’t just “does it work” but “is this the right shape.” Familiarity with IDE extension frameworks, graph visualization libraries, or Model-Driven Engineering (MDE) can give you a head start, however what we care about is a strong engineering foundation and the drive to ship. More broadly, you think in concepts first. The specific tools are secondary, what matters is understanding the underlying principles well enough to apply them in any context. This applies equally whether you come from academia, industry, or an unexpected path.

WHY THIS ROLE

You won’t be maintaining a finished system or implementing a fixed vision. The foundation exists, but the important decisions are still open and visible. The choices you make now will shape the product for years. You’ll work closely with a co‑founder who currently leads the frontend, 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. That includes asking the hard questions about priorities, timelines, and whether a given direction is the right one, before writing a single line of code. As the team grows, this work naturally evolves into technical leadership through influence and clarity rather than hierarchy.

HOW TO APPLY 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?