QA Engineer

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 RefiJet, 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 keeping the manual coverage deliberate rather than accidental

Test the failure paths, not only the happy paths. Lender integrations fail, partners time out, data arrives malformed. Those cases are where our real risk lives.

Write defects that a developer can reproduce without asking you a follow-up question, and verify fixes rather than accepting them

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

Review requirements, user stories, and acceptance criteria before development begins, and send back anything that cannot be objectively verified

Validate features against intent, not only against the ticket. If the story is satisfied and the borrower or agent problem is not solved, that is a finding and you raise it.

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

Work directly with operations partners, who are the people your UAT process exists to serve and the people who feel a defect first

Partner with the Director of Product and the product managers on acceptance criteria from refinement through release, and push back when a requirement is written in a way that cannot be verified

Support release and deployment activity, including validation windows that occasionally fall outside normal hours

Establish internal standards for test documentation, defect tracking, and release validation, since none currently exist

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.

Work with Security and Compliance on the evidence our SOC 2 and PCI obligations depend on, including test records, change control, and release approvals that hold up when an auditor asks for them

None of the following is required, and their absence will not remove you from consideration.

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 validating analytics and event instrumentation (GA4, Amplitude, Mixpanel, Segment, or similar)

Experience in a SOC 2 or PCI environment, including contributing evidence to an audit

Experience testing internal or agent-facing tooling, where your user is a colleague you can walk over and watch

Yield Solutions Group is an Equal Opportunity Employer. We are committed to creating an inclusive environment for all employees and applicants.