QA Engineering in Testing

Centennial, CO (In-Office)
RefiJet processes a high volume of auto refinance applications every month across a network of 30+ lending partners. The software running that operation spans borrower-facing applications, lender integrations, and internal tools used by our operations teams, including MyYesGo (our agent CRM), Connex (our call center platform), and RefiMeNow (our lender marketplace). The quality, reliability, and usability of that software directly affects real financial outcomes for real people.
You would own software quality for the organization. In your first year, most of what you produce will not exist yet: the integration test plans, the UAT process, the coverage standards our developers write against, the regression suite, the definition of what "tested" means before a release goes out. This role sits in Product rather than Engineering, and that is deliberate. The other half is whether we built the right thing, and whether it still holds up for the borrower and the agent once it is live.
We are deliberately stack and platform agnostic. We care that you can reason about risk, learn a system quickly, and tell the difference between a test that proves something and a test that runs.
Plan on five days per week on site in Centennial, Colorado. One or two remote days per week may become available once you are established and performing well.
You are the quality function. Leadership here is not managing people, it is defining a practice and getting an organization to adopt it.

Own software quality strategy for the department, and put it in writing so it can be argued with rather than assumed
Assess the adequacy of developer-written unit test coverage, and raise gaps as findings with evidence rather than as opinions
Bring release risk to the Director of Product and Technology Leadership with a clear recommendation and a clear statement of what you are uncertain about, and accept the decision when it goes the other way
Report on quality in terms leadership can act on: what broke, what would have caught it, what it would cost to catch it next time
Own the definition of done jointly with Product, covering product acceptance as well as engineering acceptance, so nothing closes until someone has confirmed it does what it was written to do
Bring quality debt into roadmap planning as prioritized, sized work rather than a standing complaint, and defend the trade-offs with the Director of Product
Write and execute integration test plans across borrower-facing applications, backend services, internal operations tools, and lending partner integrations
Design and run the User Acceptance Testing process, including coordinating operations partners who will actually use what we build and translating their feedback into defects a developer can act on, separating genuine defects from change requests and routing change requests to Product instead of absorbing them into scope
Lender integrations fail, partners time out, data arrives malformed. Those cases are where our real risk lives.
Run release validation, including post-release verification that what shipped works in production
Own the test data problem, including how we test realistic scenarios without moving production borrower data into non-production environments
Use AI-assisted tools as part of normal daily work, including for test case generation and exploratory coverage, and remain fully accountable for what you sign off on
Product Quality

Own cross-product journey testing across MyYesGo, Connex, RefiMeNow, and the borrower-facing application. Most of our real defects live in the handoffs between systems rather than inside any one of them.
Verify that analytics and event instrumentation ships correctly and fires accurately, so the product decisions we make afterward rest on data we can trust
Validate feature flags, phased rollouts, and experiment configurations before and during release, including the off state and the rollback path
Run post-release outcome validation with Product: did the metric move, did the funnel behave, did operations and support volume go the direction we predicted
Triage production issues reported by operations and sales, separate defect from design gap from training gap, and route each one accordingly
Partnership & Compliance

Work directly with operations partners, who are the people your UAT process exists to serve and the people who feel a defect first
Support release and deployment activity, including validation windows that occasionally fall outside normal hours
Handle borrower and lender data under our security, privacy, and data handling requirements. Production data never moves to a non-production environment, credentials are never shared, and security controls are never worked around for speed. You own the legitimate alternative, which is why the test data problem is yours.
Five or more years of hands-on software quality assurance experience is the floor for this role. You would be the only quality person in the organization: no QA team to learn from, no one to shadow, and no established practice to work inside. Five or more years of professional experience in software quality assurance, including designing test plans rather than only executing plans written by someone else
Demonstrated experience testing integrated systems, including at least one integration with an external party you did not control
Experience designing and running a User Acceptance Testing process with non-technical business users, one you built rather than one you inherited and ran
Ability to read application and test code well enough to judge whether coverage is meaningful, in at least one modern language
Working knowledge of SQL, sufficient to verify data outcomes and construct test scenarios
At least one release where quality was yours end to end and the go/no-go recommendation was yours to give, including having been wrong about one and knowing what you changed afterward
This role produces documents that other people have to act on, and unclear ones fail silently.
Legally authorized to work in the United States, and able to work on site in Centennial, CO five days per week
A computer science degree, a bootcamp, an ISTQB or similar certificate, and self-directed learning are all equally acceptable here, and none of them substitutes for the hands-on years described above. A certificate tells us you studied testing. We are hiring for what you have caught, shipped, and been accountable for.
This is a mid-level individual contributor role, roughly five to eight years in quality assurance. Above it, the scope may feel too hands-on: you will be writing and running tests yourself, not directing anyone who does. We are not considering entry-level, junior, or career-change applicants for this position.
Experience in a regulated industry and testing against a compliance requirement
Experience testing high-volume transaction processing, including reconciliation and data integrity scenarios
Experience building an automated regression or integration suite from nothing
Experience with CI pipelines and getting tests to run in them reliably
Experience with auto lending, auto refinancing, or consumer credit products.
Experience testing internal or agent-facing tooling, where your user is a colleague you can walk over and watch
Bonus:
Eligible for an annual performance-based bonus with a defined target percentage of base salary, tied to company and individual goals.
Comprehensive benefits including health, dental, vision, life insurance, 401(k), PTO, career development opportunities, and the chance to join Denver's Best Place to Work (2024 & 2025) with a dynamic culture focused on internal promotion and employee growth.