Skip to content

PM + QA at Hazesoft Pvt. Ltd.Kathmandu, Nepal

SibensonGautam

PM + QA

Software Quality & Project Coordination

I bridge software quality and project delivery — testing products, investigating issues, coordinating teams, and helping turn requirements into reliable releases.

  1. QA Trainee2025
  2. QA Associate2025
  3. PM + QA2026
  1. 01Understand
  2. 02Test
  3. 03Investigate
  4. 04Coordinate
  5. 05Verify
  6. 06Deliver

01Selected work

Projects I've worked on

Real, production software — tested and coordinated as QA and PM + QA at Hazesoft. I didn't build these projects; I helped make sure they work.

  • sailracing.com
    Sailracing online store homepage
    Sailracing logo

    Production e-commerce platform

    Sailracing

    Sailracing is a Swedish apparel brand founded in 1977 and re-launched in 1999 that specializes in innovative, high-technical gear, outerwear, and sportswear for high-speed sailing and extreme weather conditions. They supply elite racing teams in major competitions like SailGP and the America's Cup.

    My role
    QA / PM + QA
    Context
    Hazesoft client project

    Worked on

    • Catalog & pricing rules
    • Cart & checkout
    • Regression
    • API testing
    • UAT
    • Production verification

    Postman · Chrome DevTools · ClickUp

    Visit Website: Sailracing (opens in a new tab)
  • dogman.se
    Dogman online store homepage
    Dogman logo

    Customer-facing e-commerce platform

    Dogman

    Dogman AB is the leading pet products brand and company in Sweden, firmly holding the top position in the market.

    My role
    QA
    Context
    Hazesoft client project

    Worked on

    • Product pages (PLP / PDP)
    • Wishlist
    • Checkout
    • Payment gateway flows
    • Functional
    • E2E
  • celestiocloud.com
    Celestio managed WordPress hosting homepage
    Celestio logo

    Cloud platform · API testing

    Celestio

    A single control plane for your WordPress site: SFTP, database, domains, SSL and backup in one console. Plus the server-level controls other Swedish hosts keep behind a support ticket.

    My role
    QA · API testing
    Context
    Hazesoft client project

    Worked on

    • REST APIs
    • Authentication
    • Authorization
    • Permissions
    • Error handling
    • Negative testing

01 / 01

02Hazesoft Pvt. Ltd. · Kathmandu, Nepal

From testing features to coordinating delivery

Three roles at one company, each adding responsibility — and QA stayed hands-on the whole way through.

  1. —Jul 2025

    QA Trainee

    Learned QA methodology on real features — executing test cases and verifying bugs with developers.

    • Manual testing
    • Test case execution
    • Frontend testing
    • API testing assistance
    • Bug verification
    • QA methodologies & process
  2. —Jun 2026

    QA Associate

    Owned day-to-day testing across web applications and e-commerce workflows — from the interface down to the APIs behind it.

    • Functional & regression testing
    • Frontend / UI testing
    • Workflow & API testing
    • Test case design & execution
    • Bug reporting & tracking
    • Issue reproduction
    • Fix verification
    • UAT support
    • Production verification
    • E-commerce workflows
  3. —Present

    PM + QA

    Coordinating project delivery in ClickUp with developers, clients and stakeholders — while staying hands-on with QA through development, UAT and production.

    • Task coordination in ClickUp
    • Requirement clarification
    • Developer coordination
    • Client & stakeholder communication
    • UAT coordination
    • Blocker & issue tracking
    • Fix coordination
    • Delivery follow-up
    • Issue investigation & reproduction
    • Functional, regression, UI, API, UAT & production verification

03About

A tester who also moves the work

I started at Hazesoft as a QA Trainee and grew into a hybrid PM + QA role. Testing is still at the centre of what I do — I've added the work of getting it delivered.

Before testing anything, I want to know what the feature is supposed to do and what “done” looks like. Then I test against that — realistic scenarios, not only the happy path.

When something breaks, reporting the symptom is half the job. I reproduce it, check the API responses behind the interface, and narrow it down so developers start from a likely cause rather than a screenshot.

As PM + QA I also keep delivery moving: tasks and blockers in ClickUp, requirements clarified with clients, fixes coordinated with developers, UAT run with stakeholders — and every fix verified before it's called done.

  • 01

    Hands-on QA

    I still test every day — functional, regression, UI, workflow and API.

  • 02

    Product first

    I learn what a feature is for before I decide how to test it.

  • 03

    Investigation

    I reproduce, compare expected vs actual, and narrow down the cause.

  • 04

    Clear communication

    Bug reports and updates that developers and clients can act on.

  • 05

    Coordination

    Requirements, blockers, fixes and UAT — tracked until they're done.

  • 06

    Always learning

    Currently building automation skills with Playwright and TypeScript.

Hands-on QA experience
1+year
Applications & projects tested
7–10
Frontend & backend developers coordinated with
8–11
Production releases supported
3–5
Career progression
QA → PM + QA

Figures are approximate.

EducationBSc. CSIT · New Summit College · 2021 – 2025

04How I work

Not only “I find bugs” — I follow them through

The same loop shows up whether I'm testing a feature or coordinating a release. Select a step to see what it involves.

01QA + PM

Understand

Clarify the requirement and the expected behaviour before anything is tested or built.

  • Read the requirement end to end
  • Ask what 'done' looks like
  • Note edge cases and open questions

OutputClear expected behaviour

05QA investigations

Finding out why, not only what

Real issues I worked on, from requirement to verified behaviour. Client names, data and code are left out; diagrams are simplified.

01E-commerce · Production

A product discount that leaked across the cart

A catalog/cart pricing rule meant for specific products was also discounting other products in the same cart.

  1. Requirement

    The discount should apply only to the specific products the rule targets.

  2. Test

    Built carts mixing matching and non-matching products at different quantities.

  3. Issue

    Once a matching SKU reached quantity 2 or more, other products in the cart were discounted too.

  4. Investigation

    The old logic checked whether the cart contained a matching SKU with quantity ≥ 2 — then applied the discount to every product, not just the matching ones.

  5. Fix

    Developers changed the logic to be product-specific, so the discount applies only to matching products.

  6. Verification

    Retested matching-only, non-matching-only and mixed carts in UAT, then verified in production.

Simplified illustrationVerified in UAT and production

Before

  • Product Amatching · qty 2− discount
  • Product Bnot in rule− discount
  • Product Cnot in rule− discount
if cart.has(sku, qty >= 2)
  discount(every item)

After

  • Product Amatching · qty 2− discount
  • Product Bnot in rulefull price
  • Product Cnot in rulefull price
for item in cart
  if item.matches(sku, qty >= 2)
    discount(item)
  • Pricing rules
  • Cart
  • UAT
  • Production verification
02Web application · Roles & permissions

Admin couldn’t duplicate pages

An admin account didn’t have the page-duplication permission — it had only ever been enabled for super-admin.

  1. Requirement

    Admin users need to be able to duplicate pages.

  2. Investigation

    Reproduced with an admin account and compared it with super-admin. Duplication was only enabled for the super-admin role.

  3. Permission configuration

    Enabled the permission for the admin role through Configuration Menu → Role. No code change needed.

  4. Verification

    Confirmed the admin account could now duplicate pages successfully.

Simplified illustrationAdmin can duplicate pages

Configuration Menu→Role

PermissionSuper-adminAdmin
Duplicate page→

Admin can duplicate pages — no code change

  • Roles
  • Permissions
  • Configuration
03E-commerce · Product pages

Parent product, child data, blank image

A parent product without an image opened from the listing page (PLP) into a product page (PDP) that mixed parent and child data.

  1. Observe

    Opening the parent product from the PLP led to a PDP with an incorrect, blank image state.

  2. Investigate

    The PDP displayed the child SKU and its price, while the image stayed associated with the parent product — which had no image.

  3. Price check

    Also found a pricing/discount display discrepancy — verified the displayed total price against the price after discount.

  4. Report

    Documented both behaviours with reproduction steps and shared them with the developers.

Simplified illustrationReproduced and reported

PLP

no image

Parent product

PDP

blankparent image

SKUchild

Pricechild

total price
vs. after discount?
  • PLP → PDP
  • Variants
  • Pricing display

06Cloud platform & API testing

Testing what sits behind the interface

QA and API-level testing for cloud platforms in Postman — access control, tenant isolation and resource workflows. My role was testing, not building or operating the infrastructure.

Celestio

Hazesoft client project

Cloud hosting platform QA and API testing — checking users can only do what their role allows.

  • REST APIs
  • Authentication
  • Authorization
  • Permissions
  • Error handling

Kepler Hosting

Parent-company project

API-level testing of core cloud resources, focused on tenant isolation and invalid / boundary input.

  • Tenant isolation
  • Networks
  • Security groups
  • Block storage
  • API / database validation
  • Positive

    Valid requests return the expected resource and status.

  • Negative

    Invalid, unauthorised or malformed requests fail safely.

  • Boundary

    Limits, empty values and edge-of-range input.

  • Error handling

    Clear status codes and messages — no leaked detail.

api-test-matrixillustrative · not real endpoints
Illustrative examples of API test cases by type
RequestConditionExpectType
POST /networksvalid payload201Positive
POST /networksmissing required field400Negative
GET /volumes/:idno auth token401Authentication
DELETE /security-groups/:idrole lacks permission403Authorization
GET /volumes/:idanother tenant's resource404Tenant isolation
POST /volumessize at / beyond limit400Boundary

Also validated

  • Status codes
  • JSON payloads
  • Error messages
  • Backend state via API / database

Toolkit Postman · REST APIs · JSON · Auth / AuthZ · Tenant isolation · Issue investigation

07Skills

What I use at work

Professional skills I use in my role today — and, kept separate, what I'm currently learning.

Quality Assurance

14

Day-to-day testing work

  • Manual Testing
  • Functional Testing
  • Regression Testing
  • Exploratory Testing
  • UI / Frontend Testing
  • End-to-End Testing
  • API Testing
  • Test Case Design
  • Test Scenario Design
  • Bug Reporting
  • Issue Reproduction
  • Issue Investigation
  • UAT Verification
  • Production Verification

Project Coordination

09

Moving work to delivery

  • ClickUp
  • Task Planning
  • Requirement Clarification
  • Developer Coordination
  • Client Communication
  • UAT Coordination
  • Blocker Tracking
  • Fix Coordination
  • Delivery Follow-up

Tools

09

What I use at work

  • Postman
  • REST APIs
  • JSON
  • Chrome DevTools
  • ClickUp
  • Slack
  • Microsoft Teams
  • Git
  • GitLab

In progress

Currently learning

Personal learning — not part of my professional experience yet.

  • Playwright
  • JavaScript
  • TypeScript
  • Newman
  • API Automation
  • CI/CD

08Contact

Working together, talking QA, or building better delivery?

Recruiters, teams and clients — email me directly, or use the form; it goes straight to my inbox.

sibensongautam@gmail.com