QA Engineer

About First Principles

First Principles is a product consultancy that builds radical value for ambitious, emerging technology startups. We provide product leadership and strategic support, blending modern technology with thoughtful design to shape tomorrow's products. We were founded by startup and enterprise leaders who have built and scaled products across many industries.

We work with clients in four ways: AI-first PM training and certification, product coaching, fractional product leadership through CPOs and PMs who set vision and keep roadmaps on track, and AI-first product squads that go from concept to prototype in days instead of months. Our team runs on curiosity, empathy, and continuous improvement.
The Product

You'll be working on a text fundraising application that helps political and non-profit groups raise money for their campaigns and causes. It handles the full lifecycle: registration with carriers, phone number provisioning and management, message building and sending, and detailed metrics and tracking.

The product is at an inflection point. We spent the last year and a half building the first version and running it as an internal tool. Our client is a texting firm, and we built this to replace their existing platform with something that costs half as much and does exactly what they need. We're now building differentiating features and engineering for scale as we prepare to launch it as a standalone SaaS product over the next year, with plans to roll it out to our client's own clients so they can run campaigns themselves by the end of 2026.
The Role

We're looking for someone who sits at the intersection of QA, engineering, and product: an expert in test automation who also has the product sense to understand how the application actually gets used, not just how it works mechanically.

In practice, you and the product manager should become the two people who understand real customer flows and what correct results look like better than anyone else on the team, including the engineers. The engineers know how their features work. You'll know how the system is supposed to behave end to end, and you'll be the one who can tell a genuine defect apart from expected behavior.

You'll start by testing things manually, because that's how you'll learn the system deeply and figure out exactly what needs to be checked. From there you'll automate it, ideally writing down the manual steps clearly enough that AI tooling can help you build out the scripts while you move on to testing the next thing. Manual testing never fully goes away, especially for brand new features, but the goal is a first-class automated suite that frees you and the team from re-checking the same ground every release.
Responsibilities

Manual and release testing. This is a big part of the role, shared closely with the product manager rather than owned outright. Manually test new features before release, focusing on the full range of scenarios including the unhappy paths, not just the happy path. Help drive release preparation and post-release testing: running code freezes, identifying what's changed and what needs checking, building and running smoke and regression tests, and making sure new work is genuinely ready to ship. A lot currently goes untested each release, including phone numbers, brands, campaigns, user auth, and messaging reports, and closing that gap is a big part of why this role exists.

Test automation. Build and maintain automated test suites across API, web UI, and service-to-service layers, choosing the right level of test rather than defaulting to brittle UI tests. The web interface is a natural place to start building automation early. Use AI tooling to accelerate this wherever it helps, but be able to review and write and modify the code yourself when the tooling needs it.

Own the test / proxy API. Take ownership of the proxy and test environment that simulates message sending. Right now different engineers have each bui