I connect business needs with technology and delivery, so the solution actually works in practice.
I've worked across the full software product lifecycle: understanding what customers need, turning it into requirements, working with developers, testing what comes back, and then getting the system into daily use. What I enjoy most is the connection between the problem someone needs solved and the solution that finally does it. I'm comfortable holding the customer, business, user and developer perspective at the same time, and keeping the reason we're building something from getting lost along the way.
Understand the problem first. Then look for the solution.
I always start with the people who will work in the system. I talk to end users, key stakeholders and the client's own teams to understand how their work really runs. Requirements written that way describe the actual problem, not just what somebody asked for.
That's not where my part ends. Requirements have to be turned into development tasks, the result has to be tested, UAT has to be prepared, and then the system has to be brought into everyday use through configuration, demos, workshops or training. I like to stay with a project until people are genuinely using it.
Four areas — approach and impact in each.
How I work in each area. The specific projects, clients and numbers are in the career journey below.
Product Management
Products that stay coherent as they grow — balancing user needs, business priorities and long-term maintainability.
Start with the problem
A product decision only makes sense once I know what problem we're solving, who it affects and what should change afterwards. I work with stakeholders to understand needs, weigh up ideas and set priorities before anything goes into development. Business value is only one side of it. Development capacity, technical constraints and how the product will be maintained in two years matter just as much.
- Clearer product decisions based on value and context.
- Products that can evolve without becoming unnecessarily complex or difficult to maintain.
Business Analysis
Requirements that teams can build from with confidence.
Translate between worlds
Business stakeholders talk about problems and results. Developers need something concrete to build. My work sits in between: analysing needs, mapping processes, questioning assumptions and turning messy requirements into user stories with acceptance criteria that can actually be tested. I keep checking that with both sides as we go, so nobody discovers a different understanding at the end.
- Less ambiguity and unnecessary rework.
- Better alignment between business expectations and technical implementation.
Implementation & Adoption
Systems that become part of everyday work — not just software that has been technically deployed.
Make the change work
Launching a system is the easy part. I go through the existing processes with the team, get the solution ready for real use, help with configuration and rollout, and support people while they change the way they work. Depending on the project that means process mapping, workshops, training, UAT and staying available after go-live.
- Smoother transitions to new systems and processes.
- Users who understand how and why to use the solution.
Quality & UAT
Software that is validated before release — technically, functionally and from a real user perspective.
Deliver with confidence
I test against the intent, not only the ticket. Because I know the business side, I can tell when something technically passes but would still break someone's day. I design and run functional, regression and end-to-end tests, prepare UAT scenarios, guide stakeholders through acceptance, and give the team a clear picture before a release goes out.
- Issues identified before they affect users or business operations.
- Greater confidence that releases are ready for real-world use.
From testing software to shaping what gets built.
The roles, projects and industries I've worked in, and where each one sits across Product Management, Business Analysis, Implementation and Quality.
- Client
- Santander Consumer Bank
- Industry
- Consumer Finance · Banking · Automotive Finance
Project contextA web application built from scratch for internal users in the Automotive division of a consumer finance bank. It supports three key areas: Residual Value (RV), Commissions and Campaigns.
My contribution- Design and execute functional, regression and end-to-end tests
- Validate functionality against business requirements and acceptance criteria
- Identify, document and follow up on defects, working closely with developers
- Write new user stories from stakeholder feedback, and review and refine existing ones
- Analyse business needs and clarify requirements with stakeholders
- Participate in on-site UAT sessions and support business stakeholders during acceptance
- Bring UAT findings back into the development process
Key achievements- Cover both sides of the work on this project: I write and refine the user stories, and I test the result against them
- Run UAT on site with the business users, then rewrite what comes out of it into user stories the team can actually pick up
Functional testingRegressionEnd-to-end testingUATRequirements analysisJiraBrunoDevin AI- Client
- 7 client organizations — selected clients: Decathlon, Baťa
- Industry
- B2B SaaS · HR Technology — client industries: retail, fashion, financial services
Project contextTRIA is a B2B HR platform used by several client organizations, together representing over 3,000 employees. I worked across the whole lifecycle: client requirements, product decisions, coordinating development, testing, UAT, implementation and adoption.
My contribution- Collected requirements, ideas and enhancement proposals directly from clients
- Analysed and evaluated requests for business value, technical feasibility and product fit, and decided what was suitable for implementation
- Translated requirements into structured development tasks, then assigned and coordinated the work
- Reviewed and tested delivered functionality and supported UAT
- Presented new functionality to clients and collected their feedback
- Helped create and establish the product strategy together with colleagues
- Participated in sales activities and contributed to evaluating project revenue and costs
Key achievements- Ran the end-to-end implementation for a major international retail client: product-fit assessment, process mapping, translating processes into the system, initial configuration, workshops, training and demo sessions, and user support through adoption
- Helped that client improve internal processes through the implementation itself
- Balanced client needs against product scalability, development capacity, technical feasibility and business sustainability
Product managementRequirements & specificationsImplementationWorkshops & trainingUAT- Industry
- Cybersecurity · B2B · E-commerce · Partner Management
Project contextOMS was the internal B2B ordering platform where Avast partners and distributors bought software licences for their own customers. In practice a B2B e-shop and partner portal, with card payments, a line of credit and monthly closing balances.
My contribution- Built a deep understanding of the existing system and its business workflows
- Tested both the existing system and the redesigned application
- Validated complex business workflows and worked closely with developers
- Contributed to API and technical documentation, and created user documentation
- Helped onboard and train new QA colleagues as the team and system grew
Key achievements- Took over a system originally built and maintained by an external US-based company: our newly formed team spent three weeks in the United States transferring knowledge before assuming ownership
- Supported quality through the modernisation — front end rebuilt first, then the back end — replacing an outdated application with a modern solution
Functional testingRegressionEnd-to-end testingDefect analysisAPI documentationJira- Industry
- HR Technology · HRIS · Attendance Management
Project contextSYSDO is an attendance and HR management system. I started out testing it and gradually took on the Product Owner role: requirements, backlog, prioritisation, customer communication and implementation.
My contribution- Tested the system and collected requirements directly from customers
- Analysed customer needs and translated requirements into user stories with acceptance criteria
- Managed the product backlog, participated in prioritisation and helped decide what to work on next
- Communicated directly with customers, presented the system to potential clients and took part in sales activities
- Configured the system for customers and supported them in adapting it to their needs
Key achievements- Monitored Czech Labour Code changes, analysed their impact on the product, and translated regulatory requirements into product changes and test coverage
- Created a comprehensive online user guide for SYSDO, turning complex functionality into clear, practical documentation
- Moved from tester to Product Owner on the same product: quality, then requirements and analysis, then product decisions, then client work and implementation
Requirements analysisBacklog & prioritisationUser stories & acceptance criteriaSQLREST APIsPostmanJira
Skills that connect business and software.
Business & Product
Technology & Quality
Collaboration
Product Management · Product Owner · Business Analysis · Requirements Engineering · Functional Specifications · User Stories · Acceptance Criteria · Backlog Management · Roadmap Planning · Release Management · Stakeholder Management · Process Mapping · Process Improvement · Gap Analysis · Fit-Gap Assessment · Software Implementation · System Configuration · Data Migration · User Training · Workshops · Change Management · Quality Assurance · QA Engineering · Test Analysis · Test Cases · Functional Testing · Regression Testing · Integration Testing · API Testing · REST API · Postman · SQL · Jira · Confluence · Azure DevOps · TestRail · Agile · Scrum · Kanban · UAT · Defect Management · HRIS · HR Information Systems · Payroll Systems · Attendance Systems · Order Management · Banking Administration · B2B SaaS · Enterprise Software · Cross-functional Collaboration · Stakeholder Communication
Foundations in informatics and business.
- Masaryk UniversityBSc.Business InformaticsFaculty of Economics and Administration
- Masaryk UniversityApplied InformaticsFaculty of Informatics
- Driving license — category B
- LanguagesCzech — NativeEnglish — C1
Download my latest CV.
The PDF covers the essentials; this page has the detail. Share whichever suits your process.
Let's discuss how I can help your team.
Whether you're building a new product, improving an existing system or looking for an experienced IT professional to strengthen your team, I'd be happy to talk.
Long-term Roles
Own outcomes inside your team as a product, delivery or quality lead, across releases, roadmap decisions and stakeholder alignment over time.
Short-term Projects
Take a focused initiative such as a product launch, system rollout or release cycle, and deliver hands-on results within a defined scope.
Product Consulting
Audit requirements, backlog and delivery flow, then name the gaps and recommend practical next steps your team can act on immediately.
End-to-End Delivery
Lead the non-development side of a software project from requirements to go-live, coordinating a trusted development partner when code is needed.
- LocationBrno, Czech Republic
- Emailpeta.ondrouchova@gmail.com
- LinkedInlinkedin.com/in/petraondrouchova
- GitHubgithub.com/petaondrouchova