QA Engineer

We need someone to own quality at Eisen. The whole thing, not a piece of it.

We’re processing billions of financial records for major banks, scaling fast, and shipping often. Quality can’t be something everyone sort of thinks about. It needs a person whose whole job is making sure what we ship actually works, and building the systems that make that repeatable.

This is one of those roles where you touch everything. You’ll work across the engineering team, sit in on architecture decisions, and have real say over what’s ready to go out the door. If quality is the thing you care most about in software, this is a good place to do that work.

About Eisen

Eisen is the first account offboarding platform for financial institutions. We handle escheatment, disbursement, and customer outreach for banks and fintechs, helping them close the loop on inactive accounts and get people back to their money.

We process billions of records daily. SSNs, account numbers, financial data. If we get something wrong, a bank’s customers are affected and regulators notice.

The Situation

Our peak ingestion hits about 2,500 records per second across MongoDB, Kafka, Bull, Redis, and Snowflake. We need to scale that 10x. We’re SOC 2 compliant, onboarding bigger financial institution customers, and adding new products to the platform constantly.

We’re building fast with Claude Code and shipping a lot of PRs. The deployment pipeline is feeling it. Increasing velocity shouldn’t mean decreasing quality, but someone needs to make sure that’s actually true.

Right now, nobody is thinking about this full-time.

What You’ll Do

Test Infrastructure

• Design and maintain automated tests across unit, integration, and E2E layers

• Own CI/CD quality gates in GitHub Actions. If a pipeline is slow or unreliable, that’s your problem to fix

• Build regression suites that catch real issues early in the development cycle

• Set up performance and load testing. We need to know what breaks at 100M+ accounts before our customers find out

• Figure out test data management so tests are reproducible across environments

• Use AI tools (Claude, Cursor, Copilot) where they help. We’re not dogmatic about how you get there

Data Integrity and Compliance

• Design testing around PII handling, encryption, and audit trails

• Build quality gates that maintain SOC 2 compliance as we scale

• Make it hard to ship a data integrity bug. Prevention over detection

• Validate financial data transformations at every stage of the pipeline

Release Confidence

• Define release certification so deploys feel safe, not nerve-wracking

• Track defect escape rate, rollback rate, change failure rate. Make quality visible

• Build dashboards and alerting so the whole team can see where we stand

• Work with product and platform engineers to move testing earlier in the cycle

Leadership

• Say “this isn’t ready” when it isn’t ready. Have people take you seriously when you do

• Sit in architecture reviews and flag risks before they become incidents

• Help engineers get better at testing their own code. The goal is shared ownership, not a QA bottleneck

About You

• 5+ years building test automation and CI/CD pipelines, with increasing responsibility for quality outcomes

• You’ve worked in fintech, banking, or a similarly regulated environment. You know what compliance looks like day-to-day, not from a textbook

• Strong with JavaScript/TypeScript testing tools (Jest, Cypress, Playwright, or similar)

• You’ve built and maintained CI/CD pipelines in GitHub Actions or equivalent. You’ve written the YAML, debugged the failures, optimized the runtimes

• Experience with performance testing (k6, Artillery, Locust, or similar)

• You understand how distributed systems fail and can spot architectural risks before they show up in production

• People listen to you. You can explain a quality concern to engineers and to leadership and get both to care

• You’re pragmatic about tradeoffs between speed and quality. You don’t chase 100% coverage for its own sake

• You’re comfortable figuring things out. We’re building this function from scratch