We are a fast-growing SaaS company in the EduTech space, operating mainly in Singapore, Vietnam, and Malaysia, with almost 2000 schools as customers. Our mission is to revolutionize early childhood education through technology and provide innovative, scalable solutions to our customers. With a team of 60 talented individuals, we are committed to transforming the way education is delivered in the Southeast Asian region and beyond.

Our DNA: What We Need From You

To thrive in this developing environment, you must live by our code:

High Agency & Accountability: Don't Blame, Solve. Since we are still figuring things out, things will break. You spend zero energy pointing fingers and 100% on finding the cure. You Own it all as the Directly Responsible Individual.
Simplicity with Depth: Design for ease, think with depth. You apply band-aids for immediate support, but you never lose sight of resolving the root cause for long-term stability.
Sense of Urgency: Feel the heat. When a customer struggles, you own that pressure until the pain is gone.
One LittleLives: Cover your team. Be a supporter, not an observer. Flag the blockers, then pass the ball.

About The Position

Title: Senior QA Lead (Stabilization Mission)

Location: Hanoi or Ho Chi Minh City

Department: Engineering

Reports to: Engineering Lead

The mission

Eliminate recurring production incidents
Rebuild regression foundations
Design system-level quality controls
Strengthen transactional and data integrity
Turn QA from reactive to preventive

If you've stabilized a messy ERP, finance system, or workflow-heavy SaaS before — this will feel familiar.

The Reality Check: We are looking for a battle-tested Senior QA Lead to lead a system stabilization mission.

Our platform powers 10=600+ schools across multiple countries. It handles student lifecycle, operations, billing, payments, reporting, and complex data flows.
We are past the early-stage chaos. Now we need to rebuild quality foundations properly.
This is not a maintenance role. This is a stabilization leadership role.

What You Will Be Doing

Stop Production Incidents at the Root

Identify systemic defect patterns
Design invariant checks (data consistency, transaction integrity)
Build reconciliation validation
Prevent recurrence, not just detect bugs

Own End-to-End Platform Quality

Student enrollment & lifecycle
Class & attendance management
Billing & payments
Reporting & analytics
Integrations & webhooks
Data migration & legacy imports
This role sees the whole system — not just UI.

Hands-On Technical Validation

Write SQL to validate data integrity
Test transactional atomicity
Verify idempotency of background jobs
Test edge cases that break real operations
Participate in root cause analysis during incidents

Elevate the QA Team

Mentor and upgrade team capability
Introduce structured test matrices
Move QA from manual execution to system thinking
Build quality metrics leadership can rely on

What We Are Looking For

Having 5+ years QA experience
Experience stabilizing a finance-heavy or workflow-heavy system
Having strong understanding about below areas:

Data consistency
Transactional systems
Complex state transitions

Confidence reading logs, querying DBs, and challenging assumptions
Experience designing regression automation, not just executing tests

Interview Process

Round 1: Role Challenge

Round 2: Team Interview with Engineering Lead and CPO

Role challenge - 4 hours

Question 1: What kind of reports/ validation system you will recommend to check financial data accuracy of the system.

Scenario 2: Payment gateway sends webhook twice due to timeout.

System behavior:

First webhook: marks invoice paid
Second webhook: creates another payment record
Balance becomes negative

Questions:

What is the architectural issue
How would you test idempotency
What invariant checks should exist
What automated detection would you implement

Question 3: The system has had recurring finance incidents for 4 months.You are asked to design a 90-day stabilization plan.

Questions:

What would you stop immediately
What automated controls would you build first
What metrics would you track weekly
How would you define release readiness