QA Engineer

Location:

Centennial, CO (In-Office)
Company:
Refi Jet

Reports to:

Director of Product

Refi Jet 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 My Yes Go  (our agent CRM), Connex (our call center platform), and Refi Me Now  (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. Not administer it, own it. 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. That is the work. This role sits in Product rather than Engineering, and that is deliberate.

Half of what you own is whether we built the thing right. 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.

You are not a second pair of hands on the developers' testing. They keep writing unit tests and stay accountable for them. Your job is to determine whether that coverage is actually adequate,. You are also not a manual regression queue. Where automation pays for itself, we expect you to build it. And you are not a downstream inspector. You are in the room when requirements are written, because the cheapest defect to fix is an acceptance criterion that could never have been verified in the first place.

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

Define what "adequately tested" means at Refi Jet, in terms specific enough that a developer can tell whether they have met it before they open a pull request

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

Build and maintain a regression suite, automating where automation pays for itself and…