QA Engineer

Manual & Functional Testing Focused (NOT A REMTOTE POSITION)

About The Role

Invessio is building the infrastructure for modern investment management. Quality here isn’t a final gate. It’s baked in from day one. We’re looking for a QA Engineer who brings systematic, intentional skepticism to every sprint: someone who reads the PRD before dev picks up the ticket and treats vague acceptance criteria as a blocker, not a to-do.

This role is primarily manual and functional, but “manual” doesn’t mean clicking through happy paths. It means deep exploratory testing, business logic validation, and being the person who asks the question no one else thought to ask.

This role is also deeply embedded in the software development lifecycle and plays a critical role in stabilization, release readiness, and ensuring system behavior aligns with both technical intent and business expectations.

What You’ll Do

Test Planning & Execution

Write structured, detailed test cases that a stranger could execute exactly with no ambiguity
Develop test plans from PRDs, user stories, and acceptance criteria
Execute functional, regression, integration, and exploratory testing
Document bugs with clear reproduction steps, environment info, and expected vs. actual behavior
Re-test fixes and verify no regressions were introduced

Business Logic & Data Validation

Validate calculations, servicing logic, and workflow outputs against expected behavior
Cross-check data against source of truth datasets to catch inconsistencies and drift
Validate system outputs against defined calculation models and expected business logic
Identify edge cases that only surface under specific data conditions

Early Lifecycle QA

Join sprint planning and design reviews to give testability feedback before dev begins
Flag requirements that are vague, contradictory, or untestable before anyone builds the wrong thing
Collaborate with product to sharpen acceptance criteria
Ensure quality considerations are addressed early, not after development is complete

Release Readiness

Validate feature completeness and stability before go/no-go decisions
Maintain test results, defect trends, and coverage documentation
Contribute to release readiness criteria: “done” is defined, not assumed
Provide clear input into go/no-go decisions based on risk, known issues, and system confidence levels

Stabilization & Risk-Based Testing

Prioritize testing efforts based on risk, impact, and known system instability areas
Focus validation on high-risk workflows, calculations, and data dependencies
Support stabilization efforts by identifying patterns in defects and recurring failure points
Operate effectively in environments where not everything is fully defined or fully stable

Collaboration

Work with engineers to understand what changed and where regression risk is highest
Partner with product to ensure what’s built matches what was specified
Communicate blockers clearly and early, no surprises at the end of a sprint
Help create alignment between product intent, engineering implementation, and production behavior
Participate actively in ADO-driven sprint workflows, ensuring QA visibility and traceability across requirements, defects, and releases

What We’re Looking For

Required

3+ years QA experience in SaaS or web applications
Strong test case writing skills: structured, clear, executable
Experience with functional, regression, and integration testing
Experience working within Azure DevOps (ADO) for test case management, defect tracking, sprint collaboration, and release validation workflows
Ability to clearly document defects, test execution results, and validation status within ADO
Solid understanding of SDLC and Agile methodology
Basic SQL skills to independently validate and investigate data without always needing engineering support

Preferred

Experience in fintech, financial platforms, or calculation-heavy systems
Exposure to API testing (Postman or similar) for backend validation
Familiarity with exploratory testing techniques and session-based testing
Experience providing testability feedback on PRDs or specifications
Experience working in stabilization phases or partially mature product environments
Exposure to test automation or interest in building automated test coverage over time

Mindset

Thinks like a user, breaks like an adversary
Knows the difference between “no bugs found” and “no bugs exist”
Shows up in planning, not just at the end of the pipeline
Treats reproducibility as everything
Understands that QA owns the question: does this actually do what we said it would, under real conditions?
Understands that not all areas carry equal risk and knows how to prioritize testing accordingly
Comfortable operating in ambiguity and helping create clarity where it doesn’t exist
Show more Show less