Prakhar Lakhera User

I am a Software QA Engineer who likes figuring out exactly why things break, and then making it harder for them to break again.

I started in manual and API testing on a live product: tracing edge cases with Postman, browser DevTools and network logs, and writing Jira defect reports clear enough that developers could fix things without a follow-up call. I worked daily with a Los Angeles-based team across a 12+ hour time difference, so I am used to working independently and keeping written updates clear.

Lately I have been moving into test automation and using LLMs where they actually help. I write end-to-end suites in Playwright (JavaScript) on GitHub Actions CI, and I built FlakeRadar, a Playwright reporter that explains CI failures on pull requests using simple rules first and an LLM only for what the rules can’t decide. When I measured it, my first score was 100%, until I found the model could see the answer in the test title. The honest number was 93%. Lesson: check your own results before you trust them.

Before QA, I worked as a freelance frontend developer and a volunteer teacher, and I have a BSc in Chemistry. Together they gave me habits I still use: record things precisely, explain technical details in plain English, and don’t assume a fix worked just because a build went green.

What I work with:

• Automation & CI: Playwright, JavaScript, Node.js, GitHub Actions, custom reporters and fixtures

• API & core QA: Postman, REST APIs, browser DevTools, Jira, regression and smoke testing, basic SQL

• AI in testing: LLM-assisted test design, LLM API integration, rule-based failure classification

Looking for full-time or remote roles in QA Automation or SDET (also open to API support), where I can help a team ship more reliably. Always happy to talk Playwright pipelines, flaky tests, or strange edge cases. Feel free to connect.