Nikolay L.

I've been doing QA for over 10 years across all kinds of web projects. SaaS, CRM systems, e-commerce, internal tools, marketplaces, landing pages with complex logic. If it runs in a browser, I know how to break it. I go through the app the way a real user would, but also looking for the edge cases users would never think to try. Billing flows, form validation, role permissions, third-party integrations, API behaviour behind the UI. Lately I've been testing AI-powered products too, chat interfaces, LLM-based features, where the challenge is less about clicks and more about how the system behaves under unexpected input. When the team needs to know how the app holds up under load, I use JMeter. When a project grows to the point where running regression by hand every sprint stops making sense, I can build automation. Playwright or Cypress, TypeScript, wired into CI/CD. On one project, automation brought regression from 3 days down to 2 hours. Bug reports come with exact steps, network traces, and video. Devs don't have to guess what happened, they just fix it. My stack: Postman, Chrome DevTools, Burp Suite, JMeter, SQL, Jira, TestRail, Azure DevOps for manual testing and test management. Playwright, Cypress, TypeScript, JavaScript for automation when the project needs it. Manual, automation, or both. Just message me, and we'll figure it out.