Stella Maidorn
Requirements Engineering · Product Ownership · Technical Analysis
I work at the intersection of business, product, and engineering. When requirements are unclear, processes are getting messy, or technical questions need to be understood before a team can move, I bring structure to the situation.
My background combines mathematics, computer science, philosophy, software engineering, and product work. That lets me analyze complex domains, assess technical feasibility, and document work in a way that turns conversations into decisions and decisions into implementation-ready next steps.
I am especially useful in phases where many perspectives, constraints, and open questions come together: discovery, requirements engineering, backlog structuring, process analysis, technical pre-analysis, and prototyping.
Clarify unclear requirements
- Structure goals, stakeholder perspectives, assumptions, and domain logic
- Requirements engineering, user stories, and acceptance criteria
- Prioritization, backlog structure, and decision documents
Mediate between business and engineering
- Translate and mediate between business, product, and engineering
- Establish a shared goal and a common language
- Create documentation that business and engineering can both work with
Make processes and patterns visible
- Analyze workflows and expose friction
- Recognize recurring patterns in requirements, alignment loops, and process steps
- Derive concrete actions, target processes, and next steps
Stay technically connected
- Coming from software development — on equal footing with engineering teams
- Assess technical feasibility, interfaces, and system boundaries early
- Use technical pre-analysis and prototypes to make product ideas more grounded
What comes out of it
My work does not stop at conversations or notes. Typical outcomes include prioritized backlogs, decision documents, clear requirements, process sketches, technical pre-analyses, and recommendations that product and engineering teams can act on directly.
- Requirements catalogs, user stories, and acceptance criteria
- Prioritized backlogs and decision documents
- Workshop documentation and stakeholder alignment
- Process sketches, target-process designs, and action lists
- Technical pre-analyses, interface descriptions, and prototypes
Analytical profile and technical fluency
Analytical perspective: My background in mathematics (M.Sc.), computer science (B.Sc.), and philosophy (minor) shapes how I work with complexity: recognizing patterns, sharpening concepts, testing assumptions, and structuring problems clearly.
Requirements and product work: Requirements engineering and product ownership in practice — most recently as a Requirements Engineer at Milch und Zucker — backed by IREB CPRE (Foundation Level) and iSQI Scrum Master Pro certifications.
Technical fluency: Several years of software development with Java, Spring Boot, TypeScript, React, GraphQL, and SQL — in demanding domains such as Open Banking (Klarna) and energy management (Janitza), including data analysis with Splunk and Elasticsearch.
Experience
Requirements Engineer — Milch und Zucker — Gießen
Product and requirements work in an HR-tech context: structuring requirements, bringing stakeholder perspectives together, coordinating with product development, and documenting new processes for an emerging department.
Software Engineer — Janitza — Lahnau
Full-stack development in a Scrum team for an application to manage and visualize measurement data in power quality and energy management; work on domain-complex data models and interfaces across frontend and backend.
Software Engineer — Klarna — Gießen
Backend development in an Open Banking context with regulated, domain-complex interfaces; data analysis with Splunk and Elasticsearch, monitoring-tool development, and communication with customers, banks, and regulators.
Teaching Assistant / Lecturer — JLU / THM — Gießen
Communicating complex computer science and mathematics topics through tutorials, exercise sessions, and introductory courses.
Beyond work
When you can't find me at my computer, you'll usually find me on the rock or in the climbing gym. Whether I'm climbing and bouldering myself or setting routes as a route setter, I love puzzling over the problems — working away at them until every move clicks and everything fits together.
During my university years, I spent a long time doing improv theatre. Improvising means listening, engaging, acting, reacting. A good scene comes together when the impulses of everyone involved merge into something shared — formed, shaped, and moved by all of them together.