> Markdown version of [/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story?t=1791](https://www.wearedevelopers.com/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story?t=1791). 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).

---

# How I Built QA from Scratch in a Scaling Startup - no fluff real life story

Building QA from scratch in a chaotic startup isn't about rushing to automate. Learn how to map risks, build developer trust, and transform testing into a shared team culture.

- **Speakers:** [Basia Karaagac](https://www.wearedevelopers.com/@basia-karaagac)
- **Event:** World Congress 2026 Europe - Virtual Stage
- **Published:** July 2, 2026
- **Duration:** 34:35
- **URL:** https://www.wearedevelopers.com/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story

## Summary

Entering a chaotic, fast-scaling startup as the sole QA engineer requires resisting the urge to immediately write code or launch tools like Playwright or Selenium. Instead, the process must begin with passive, human, and technical reconnaissance. By analyzing historical tickets to build a risk map, performing exploratory testing to challenge initial assumptions, and communicating directly with the engineering team, QA professionals can understand actual system behavior versus documented intent. This foundational context prevents automating the wrong things and shifts the focus toward identifying the system boundaries and user workflows that truly matter to the business.

A sustainable testing strategy carefully balances front-end automation, which serves as a safety net for critical user journeys, with API testing that probes extreme values, confusable data, and underlying cyclomatic complexity. However, automated test suites operate strictly under controlled lab conditions. Because production is a hostile environment filled with distracted users and unstable connections, continuous exploratory testing remains essential for discovering unpredictable operational edge cases. To build and maintain developer trust, the automation framework must prioritize stable selectors, adaptable test design that expects shifting business rules, and actionable, high-signal feedback that minimizes false positives and eliminates noisy pipeline retries.

Ultimately, software quality is not defined by defect elimination or the impossible pursuit of bug-free applications; it is an ongoing exercise in risk management. True success in a scaling environment occurs when regression testing stops acting as a bottleneck and the CI/CD pipeline transforms from an isolated QA project into a shared operational tool that developers proactively utilize. As the primary quality advocate, it is crucial to remember that caring about quality and carrying quality are not the same thing. Fostering a culture of shared team ownership naturally reinforces the core principle that tools do not test software—testers do.

**Keywords:** startup QA strategy, risk-based software testing, technical reconnaissance, front-end test automation, API boundary testing, exploratory testing techniques, CI/CD pipeline integration, sustainable test frameworks, test false positives reduction, managing test flakiness, shared quality ownership, agile regression testing, system risk management, developer test adoption, business-critical workflows validation

## Chapters

1. **Understanding a chaotic system before writing automated tests** (00:10) — Delaying framework setup to prioritize understanding business risks and system behavior prevents wasted automation effort.
1. **Uncovering historical risks through passive reconnaissance and probing** (02:28) — Analyzing documentation and past incidents reveals the gap between intended system design and actual failure points.
1. **Gathering contextual knowledge through human reconnaissance and shadowing** (06:16) — Short conversations and shadowing sessions with product owners and support teams quickly build foundational system knowledge.
1. **Conducting technical reconnaissance to reduce system unknowns** (07:35) — Using gathered context to ask developers targeted questions reduces unknowns before making strategic testing decisions.
1. **Designing a frontend automation strategy around critical workflows** (08:53) — Targeting frontend automation at highly depended-upon user journeys provides a safety net without over-engineering.
1. **Validating system boundaries with an API automation strategy** (11:03) — Testing boundary values, extreme data, and cyclomatic complexity at the API layer complements UI coverage.
1. **Capturing unpredictable edge cases using exploratory testing** (13:34) — Manual exploration uncovers how imperfect network conditions and distracted multitasking degrade system behavior.
1. **Building an adaptable automation framework for changing requirements** (15:15) — Using stable selectors and expecting business rule shifts prevents the need to constantly rebuild test cases.
1. **Eliminating test flakiness to generate clear actionable signals** (18:03) — Removing duplicate checks and prioritizing readable test code builds developer trust in pipeline alerts.
1. **Integrating automated feedback loops into the deployment pipeline** (20:58) — Running automated checks overnight transforms the test suite from a validation tool into operational visibility.
1. **Shifting focus from defect elimination to effective risk management** (21:52) — Accepting that bug-free software is impossible allows sole QA engineers to share quality ownership with the broader team.
1. **Measuring automation success through team adoption and trust** (25:14) — True QA success occurs when developers proactively run automated sanity tests and release surprises decrease.
1. **Key principles for establishing sustainable quality assurance practices** (29:51) — Effective testing relies on understanding business risks, utilizing shared feedback loops, and acknowledging that testers matter more than tools.

## Related Moments

- [Introduction to the speaker and visual testing journey](https://www.wearedevelopers.com/videos/540-let-s-get-visual-visual-testing-in-your-project) (from "Let's get visual - Visual testing in your project")
- [The shifting mindset of modern quality assurance engineers](https://www.wearedevelopers.com/videos/1984-ai-as-a-test-designer-transforming-experience-into-automated-testing) (from "AI as a Test Designer: Transforming Experience into Automated Testing")
- [Transforming software quality from assurance to enablement](https://www.wearedevelopers.com/videos/100184-self-service-quality-qa-without-qa) (from "Self-service Quality: QA Without QA")
- [Establishing a company-wide approach to software quality assurance](https://www.wearedevelopers.com/videos/428-automated-code-quality-checks-with-custom-sonarqube-rules) (from "Automated Code Quality Checks with Custom SonarQube Rules")
- [Elevating the QA engineering role for complex challenges](https://www.wearedevelopers.com/videos/100184-self-service-quality-qa-without-qa) (from "Self-service Quality: QA Without QA")
- [Using test automation as a catalyst for team collaboration](https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly) (from "How to add test automation to your project: The good, the bad, and the ugly")

## Related Articles

- [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing)
- [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)

## Related Jobs

- [Qa Engineer (Mobile & Web), Broker](https://www.wearedevelopers.com/jobs/ext/1987685-qa-engineer-mobile-web-broker) at **Bitpanda**
- [Senior Process Architect - Electronic Testing & System Integration](https://www.wearedevelopers.com/jobs/ext/1667721-senior-process-architect-electronic-testing-system-integration) at **ZEISS Group**
- [Software Tester](https://www.wearedevelopers.com/jobs/ext/1209689-software-tester) at **BWI GmbH**
- [Machine Learning Engineer](https://www.wearedevelopers.com/jobs/ext/1597388-machine-learning-engineer) at **ZEISS Group**
- [Head of AI Applications](https://www.wearedevelopers.com/jobs/ext/1456210-head-of-ai-applications) at **ZEISS Group**
- [Staff, Analytics Engineer](https://www.wearedevelopers.com/jobs/ext/569504-staff-analytics-engineer) at **Twilio**