> Markdown version of [/jobs/ext/4113846-software-engineer-problem-analysis-systems-design](https://www.wearedevelopers.com/jobs/ext/4113846-software-engineer-problem-analysis-systems-design). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - problem analysis & systems design - **Company:** pantaBio AG - **Location:** Heidelberg, Germany - **Salary:** €51,900 - €72,000 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Business Process Model and Notation, Databases, Data Structures, Software Architecture, Software Maintenance, Software Engineering, Software Systems, UML, Build Management, Data Management - **Published:** October 26, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=1d50c80e31cf70bb ## About the Role The ideal candidate thinks before and beyond the code. When confronted with an new problem, your first instinct is not necessarily to open an editor. You want to understand what the concepts mean, which distinctions matter, what assumptions are being made, and whether the proposed solution actually addresses the underlying problem. We value independent thinking over the mechanical application of established patterns and methodologies. You should be able to question the framing of a problem, identify assumptions that others have overlooked, and develop your own well-reasoned approaches when existing ones are insufficient. * You can analyse, dissect, and evaluate an unfamiliar problem into its core challenges - and come up with potential solutions. * You can evaluate importance and relevance, design & implement & validate solid solutions on your own. * A very strong capacity for abstraction. * You can turn informal descriptions into explicit models with the appropriate representations. * You are comfortable with engaging with multiple domains, including domains outside software engineering. * You can move effortlessly between high-level reasoning and detailed technical implementation. * You have an eye and a particular knack for the fine details even when confronted with vast information. * Pragmatic judgement: You know when formal modelling adds value, when a simple solution is sufficient, and how to balance conceptual correctness against implementation cost and practical constraints. * End-to-end ownership: You can take a loosely defined problem from initial exploration through architecture, implementation, validation, and delivery. * You have substantial practical software engineering experience and have independently designed and implemented non-trivial software systems. A substantial part of your work will involve determining what should be built, why, and how the underlying domain should be represented-not simply implementing requirements that others have already defined. If you primarily enjoy working through clearly specified development tickets within a familiar technology stack, this may not be the right role. If you enjoy discovering what the problem actually is and taking responsibility for solving it, we'd be interested in hearing from you. Our technologies We work with the best technological tool fit for each problem at hand, be it BPMN for formal process notations, OWL/SKOS for structured knowledge, UML diagrams for designing, the various software stacks, frameworks, databases, and many more. We don't expect you to know all these technologies. We do expect you to be curious enough to explore unfamiliar ones and capable of understanding when and why they are useful. ## Description This job is about much more than coding - it is about understanding complex problems. Developing & designing creative solutions. Structure data & systems & knowledge using formal systems. Rapidly develop a working understanding of unfamiliar domains. Implement solid software solutions. Our work sits at the intersection of software, data, laboratory workflows, automation, and cross-organizational collaboration. Much of it begins with questions rather than clear specifications. The challenges often begin long before the first line of code: understanding unfamiliar concepts and relationships, working with customers and stakeholders, untangling conflicting requirements, and translating business processes and domain knowledge into models and software architectures. Solving these problems requires intellectual curiosity, strong analytical and abstraction skills, independent thinking, and the willingness to venture beyond familiar technical territory. What you will do * Develop concepts, conceptual and logical models to adress specific problems - not only in software engineering. * Translate abstract models into sound software architectures, data structures, APIs, and working implementations. * Reason about the correctness, consistency, and implications of design decisions rather than focusing solely on implementation details. * Familiarize yourself with non-software domains, including semantic technologies, formal process notations, platform architecturing, laboratory automation, biology, chemistry, ontologies, business analysis, requirements engineering - not all of them, not all at once, but when needed. * Work with semantic data technologies, structured knowledge representations, and explicit domain models. * Write high-quality, maintainable software and take responsibility for the resulting systems. * Work on large multi-organizational data platforms, collaborate with multiple partners in working groups, understand the challenges, design&develop solutions for specific problems and implement these. * Rapidly develop prototypes for interesting and challenging problems - both for customers as well as for internal ideation. * Contribute to software solutions from initial problem analysis and requirements engineering to customer deployment, either as a team member or as full end-2-end owner.