QA Engineer (Intern)

About the Role We’re looking for a QA / Automation Engineering Intern who wants to build quality systems—not just run test cases. You’ll work on designing and implementing automated testing across audio pipelines and enterprise workflows in a fast-moving environment where systems evolve quickly and ambiguity is constant. This means creating reliable test infrastructure, improving coverage, and ensuring production quality keeps pace with rapid development. You’ll collaborate closely with founders and engineers to prevent issues before they reach customers. Your work will directly impact system reliability, release confidence, and user trust. If you enjoy breaking systems, automating intelligently, and thinking deeply about edge cases, this role will stretch your skills in the right ways. What You Will Do Design and implement automated tests for audio pipelines and enterprise workflows Build and maintain reproducible test datasets and scenarios Implement API, contract, and UI/E2E tests (Playwright or Cypress) Integrate automated test suites into CI/CD pipelines Define and enforce quality gates for releases Collaborate with engineering to debug distributed system failures Document test strategies, edge cases, and known risks What We’re Looking For Familiarity with a scripting language (Python, JavaScript, etc.) Exposure to test automation frameworks (pytest, JUnit, or similar) Basic understanding of API and contract testing Interest in UI/E2E testing tools like Playwright or Cypress Comfort working with CI/CD tools and pipelines Ability to debug issues across multiple components Founding Mindset You think in terms of user-perceived reliability, not just dashboards You ask “what does good reliability look like?” before adding metrics You take ownership of uptime and graceful degradation You balance speed of change with system stability You proactively identify reliability gaps before they cause incidents Bonus Experience with observability tools like Prometheus, Grafana, or OpenTelemetry Exposure to incident management or on-call workflows Experience with resilience testing or chaos engineering Familiarity with tracing and structured logging What Success Looks Like Within 4–6 weeks, you should be able to: Own monitoring and alerting for a subset of services Reduce noisy alerts and improve signal quality Contribute to incident retrospectives with actionable insights Improve reliability, visibility, or response time in a measurable way What You’ll Get Hands-on experience building reliability practices from the ground up Direct collaboration with founders and core engineering teams Real ownership beyond a typical SRE internship A portfolio of dashboards, runbooks, and system improvements A strong pathway into SRE, platform, or production engineering roles Who This Is Not For If you want predictable systems with no incidents to handle If you avoid ambiguity or cross-team problem solving If you prefer rigid, siloed environments with predefined processes Who Will Thrive Here Builders who want to actively own system reliability Engineers who think in terms of end-to-end systems Calm debuggers of intermittent and complex failures High-agency individuals who care about keeping systems running reliably About the Company We’re building the speech intelligence layer for Southeast Asia—turning real-world, accented, code-switched speech into structured, usable outputs for businesses.