Hello, I'm

Dipak Bist
Software QA Engineer

I have 4+ years of experience testing web applications and multi-tenant SaaS platforms — designing risk-based test suites, automating regression paths with Playwright and Python, and verifying REST APIs with Postman.

View My Work Contact Me

import os
import pytest
from playwright.sync_api import Page, expect

@pytest.fixture(autouse=True)
def setup(page: Page):
    page.goto("https://app.com")

def test_login(page: Page):
    page.get_by_label("Email").fill(os.getenv("USER_EMAIL"))
    page.get_by_label("Password").fill(os.getenv("USER_PASSWORD"))
    page.get_by_role("button", name="Sign in").click()
    expect(page).to_have_title("Dashboard")
    # ✓ Test passed!

Scroll Down

0+ Years in QA Manual, automation, API and performance
0 Companies Sterling Wells, E-Signature, Moru
0 Public repositories github.com/DipakBist08
0 Published articles blog.dipakbist.com.np

Requirements

I read the requirement before the ticket, and write down what is ambiguous.
Risk analysis

Which failures would cost the most? That ranking decides where the effort goes.
Test planning

Scenarios and cases mapped back to requirements, so coverage is arguable.
Manual testing

Exploratory passes first — scripted cases only find what they were written for.
API validation

Contract, auth and error paths checked at the service layer before the UI.
Automation

Regression-critical journeys move into Playwright so they run every time.
Performance

JMeter against the paths that carry load, watching where latency turns.
Regression

The automated suite runs on every change; failures are triaged, not muted.
Release validation

UAT and a smoke pass against the release build before sign-off.
Continuous improvement

Every escaped defect becomes a new case and a question about why.

4+ Years Experience Kathmandu, Nepal Open to Opportunities

I am a Software Quality Assurance Engineer with over four years of experience ensuring the quality, reliability and performance of modern web applications and SaaS platforms. My expertise spans manual testing, test automation, API validation and performance testing, with a strong focus on building efficient testing processes that help teams deliver high-quality software faster.

Currently, I work on FigsFlow, a multi-tenant SaaS platform for accountancy firms, where I validate complex business workflows including proposal generation, client onboarding, user roles and permissions, subscription management, billing, document generation and system integrations. Working in a multi-tenant environment has strengthened my ability to identify issues that arise from feature interactions, permission models and data isolation rather than focusing solely on individual functionality.

My testing approach is risk-based. I begin by understanding the business requirements, analysing potential failure points and designing test scenarios that target the areas with the greatest impact. This enables me to identify defects early while maintaining efficient test coverage throughout the development lifecycle.

Alongside manual testing, I design and maintain automated regression suites using Playwright with Python, following the Page Object Model (POM) and Behaviour-Driven Development (BDD) principles to create scalable, maintainable and reliable automation frameworks. I focus on reducing repetitive testing, improving regression confidence and ensuring automated tests remain stable as applications evolve.

I also perform comprehensive API testing using Postman, validating request and response structures, authentication, business logic, error handling and data integrity before changes reach the user interface. My experience includes database validation, log analysis and end-to-end testing across multiple integrated systems to ensure consistency throughout the application.

Performance and reliability are equally important aspects of my work. I use Apache JMeter to assess application performance under different workloads, helping identify bottlenecks and ensuring the system performs reliably as user demand increases.

Beyond testing execution, I actively collaborate with developers, product managers and stakeholders throughout the Software Development Life Cycle. I create clear defect reports with detailed reproduction steps, severity assessment and supporting evidence, enabling development teams to resolve issues efficiently. I also contribute to test planning, release validation and continuous quality improvement across projects.

I continuously invest in expanding my technical skills and improving testing practices. My current focus includes advanced automation framework architecture, CI/CD integration, API automation, performance engineering and scalable quality assurance processes. I believe quality is not achieved through testing alone — it is built through collaboration, automation and continuous improvement.

Associate QA Engineer
Current

Sterling Wells · Feb 2024 – Present · Product: FigsFlow
- I build end-to-end automation for the FigsFlow platform in Playwright with Python, structured around the Page Object Model
- I cover the platform's REST endpoints with Postman collections
- I use Claude Code to speed up QA work — generating test cases, improving automation scripts, debugging test failures and assisting with code reviews
- I write the test plans, test scenarios and automated test cases
- I run functional, regression, smoke, integration, end-to-end, UAT and exploratory testing
- I manage the defect queue in Jira and work in an Agile Scrum team
- I mentor junior QA engineers on manual testing, automation, defect management and Agile QA practice
QA Analyst

E-Signature Pvt. Ltd. · Aug 2023 – Feb 2024
- I built the test documentation for each release straight from the functional requirements, including the execution reports that went back to the team
- I ran the release test cycle end to end, from smoke checks through to user acceptance
- I logged defects in Jira, then tracked and verified each fix with the developer who made it
Quality Assurance Intern

Moru Digital Wallet · Mar 2023 – Aug 2023
- I tested the web and mobile apps by hand against the business requirements
- I prepared and executed the test cases for each feature I picked up
- I validated UI and UX behaviour, not just whether a feature worked
- I took part in sprint planning, daily stand-ups, sprint reviews and defect triage

Manual & Functional Testing
Core

I own the manual coverage for a platform that accountancy practices run their client work through. The judgement call is where to go deep and where a quick check is enough.
- Risk-based test design — I rank features by how much damage a failure does, and test the expensive ones hardest
- Charter-driven exploratory sessions, to catch what scripted cases never look for
- Requirement-to-test traceability, so I can show which case covers which requirement
Read: when to automate and when not to
Test Automation
Core

Playwright with Python is my primary stack, and Selenium with Behave covers my earlier BDD work. I lean on fixtures and shared selectors so a suite stays cheap to maintain as the product moves.
- Pytest fixtures for setup, teardown and pre-authenticated sessions
- One source of truth for selectors, so a UI change is a one-line fix
- Allure reporting, and the same suite run across Chromium, Firefox and WebKit
See the BDD framework on GitHub
API Testing
Core

I work at the service layer as well as in the browser. In practice that means Postman collections per environment, plus Python Requests for the checks I want living inside the automated suite.
- Auth and refresh-token flows, including expiry and re-issue
- Status code, header and JSON Schema response validation
- Environment-driven runs, so one collection covers dev and staging
Read: testing REST APIs with Playwright
Test Management & Agile QA
Core

I keep the QA side of a Scrum team legible — what is under test, what is blocked and what is ready. Defects live in Jira or Azure DevOps Boards depending on the project.
- Defects triaged, prioritised and driven through to verified, not just logged
- I take the QA slot in refinement so testability is agreed before build starts
- Confluence for test documentation the rest of the team can actually find
Read: writing a bug report that gets fixed
Performance Testing
Growing

The area I am actively building. I use JMeter to find where response times start to degrade, rather than assuming a page is fast because it feels fast on my machine.
- Load and spike scenarios modelled on realistic concurrent usage
- Response time, throughput and error-rate analysis
- Reports that show where the ceiling actually is
Databases & Version Control
Working

I use SQL to confirm that what the interface claims actually reached the database, and I work in Git the same way the developers on my team do.
- SQL queries to check a workflow wrote what it was supposed to write
- Feature branches for automation work, merged through pull request
- Code review on test code, in both directions

I use Claude Code as a working tool, the same way I use an IDE or a debugger. It is good at breadth — drafting cases, scaffolding page objects, reading a stack trace back to me. It is not good at deciding what matters, and I do not ask it to.

Everything it produces gets reviewed before it reaches a suite or a ticket. If I could not defend a generated test in review, it does not go in. The engineering judgement stays mine; the typing is what I delegate.

Test case generation

I describe a feature and its edge cases, then edit the output down. It is faster at breadth than I am; the judgement about what matters stays mine.
Automation scaffolding

Page objects and fixtures get drafted, then reviewed line by line before they enter the suite.
Debugging failures

Pasting a stack trace and the surrounding code shortens the loop between a red test and a root cause.
Code review support

A second read on my own test code before I raise the pull request.

SaaS Platform

FigsFlow

The practice-management platform I test day to day. My coverage runs across proposal generation, engagement workflows, client onboarding and the compliance steps behind them, along with the permission boundaries that keep one practice’s data away from another’s. Automated end-to-end journeys in Playwright, API suites in Postman, work items tracked in Azure DevOps Boards, and UAT before a release goes out.

Playwright Python Postman Azure DevOps Boards UAT

Active Current Project

Visit FigsFlow

API Testing

REST API Testing Framework

A reusable framework for testing REST services in Python. It exercises sign-in and token renewal, validates response bodies against a schema instead of eyeballing them, and reads its base URL and credentials from configuration so a single suite serves every environment. Postman collections cover the exploratory work alongside it.

Python Requests JSON Schema Postman

Fintech

Digital Wallet QA (Mobile & Web)

Hands-on QA for a digital wallet, covering both the mobile app and the web side. I wrote and ran the functional cases, checked the interface against the designs at several screen sizes, and joined the triage sessions where incoming defects were prioritised. All manual work — no automation on this one.

Manual QA Mobile Web Jira

BDD

BDD Test Framework

Selenium, Python and Behave driving the Swag Labs demo shop. Feature files describe the behaviour in plain language, step definitions do the driving, and each run leaves a report behind. It is the shape I would use to make acceptance criteria executable on a real product.

Selenium Python Behave Gherkin

View the code

Community

Dreamer's Youth Club

I founded Dreamer's Youth Club, a community organisation in Kanchanpur working on youth civic engagement, education and community action — and I built and maintain its website. It is a vibe-coded React build: I set the structure, content and design direction, leaned on AI for the implementation, and did the cross-device and accessibility checks myself before it went live.

React Vibe-coded Responsive SEO

Founder Community organisation

Visit the site

Bug Reporting 08/01/2025

How to Write a Good Bug Report: The Complete QA Guide

A vague bug report gets ignored. A precise one gets fixed the same day.

API Testing 10/12/2024

Playwright API Testing Guide: Test REST APIs Without a Browser

Playwright is not only for driving browsers — its request layer makes fast, reliable REST tests.

Manual Testing 15/11/2024

Manual Testing vs Automation Testing: When to Use Which

The real strengths and trade-offs of each, and a practical way to decide.

Let's Connect

Get in Touch

I am open to QA roles, remote or Kathmandu-based. If you want to talk about testing on your product, I would like to hear from you.

Send Email Connect on LinkedIn

Or copy my address directly: dipakbeest@gmail.com

Dipak Bist

Software QA Engineer

Available Worldwide (Remote)

4+ Years Experience

Dipak Bist Software QA Engineer

By the numbers

My Quality Engineering Workflow

Requirements

Risk analysis

Test planning

Manual testing

API validation

Automation

Performance

Regression

Release validation

Continuous improvement

About Me

Professional Experience

Associate QA Engineer

QA Analyst

Quality Assurance Intern

Skills & Expertise

Manual & Functional Testing

Test Automation

API Testing

Test Management & Agile QA

Performance Testing

Databases & Version Control

How I Use AI in Quality Engineering

Test case generation

Automation scaffolding

Debugging failures

Code review support

Projects