QA that feeds automation
- SDLC, STLC, Agile/Scrum
- Jira sprints, epics, stories
- Test design: BVA, EP
- Traceability; what to automate
- Defects: severity vs priority
- Smoke, sanity, regression
TypeScript-first training with AI as a weekly accelerator — not a last-week crash course. Target role: QA Automation Engineer, junior SDET track.
API, SQL, flake control, and GitHub Actions are taught on the same e-commerce app — then Week 8 is a scored capstone, not a new AI dump.
Students automate one e-commerce product for all eight weeks. The certificate is a DutyTap Program Certificate. Recruiters judge the GitHub repo, the pipeline, and the demo.
Live technical drills that get harder each week, with written feedback.
One interview question each morning: TypeScript, Playwright, or SQL.
A typed Playwright framework recruiters can clone and run.
Fact-based QA resume. Full 1:1 branding sits in Premium.
JS/TS, Playwright, API, SQL, CI, and scenario questions.
Practice as QA Engineer, Automation Engineer, and junior SDET.
8-week Playwright accelerator
Career acceleration + mentorship
A clear sequence: demo, doubts, live classes, recordings, community, plan-based support, weekly practice, and placement assistance.
What last-batch students said after finishing the 8-week Playwright QA Automation Engineer program — TypeScript, e-commerce capstone, Saturday mocks, and a public GitHub portfolio.
I came from a non-IT background. Week 2 TypeScript and the same e-commerce app every week made automation feel possible, not random tools.
After a career gap I had no confidence in interviews. Saturday mocks and the scored capstone demo gave me a script I could actually defend.
As a fresher I needed projects, not slides. The GitHub Actions pipeline on my e-commerce repo is what recruiters opened first.
Mentors actually reviewed PRs. Paste-and-run AI scripts were rejected — that discipline is why my framework looks like real work.
Resume shortlisting was my blocker. Tying the Playwright portfolio to facts on the resume — not keyword stuffing — got replies.
API + UI + DB on one product finally clicked. Login API into storage state is the flow I still use in interviews.
Switching from mechanical, I needed a map. Eight weeks, one e-commerce app, Git from week 1 — I always knew what to practise next.
Mock interviews were harder than the first company round. That was the point. I stopped freezing on framework-design questions.
Daily prompts plus Sunday optional kept me consistent without burnout. The flake-triage AI lab taught me to read traces, not guess.
I was lost on what “SDET” even meant. This batch made the junior SDET track concrete: POM, CI, a demo, and a certificate I can explain.