QE Automation Lead
- Market p25–p75
- $177k–$222k
- Opened · 30d
- +0
- Closed · 30d
- −0
- Opened · 7d
- +4775% of open
- All software engineering
- 75,155open
Attention: Kapitus is aware that individuals posing as recruiters may be communicating with job seekers about supposed positions with Kapitus. Kapitus has received reports that the content and method of communication can vary, but messages may contain requests for payment (e.g., fees for equipment or training) and/or for sensitive financial information.
Kapitus will never ask a candidate for employment for payment or financial information during the initial application or interview process. All open positions are posted in location specific employment portals available at www.kapitus.com/careers All legitimate Kapitus job postings on employment sites will direct candidates to complete an application through these portals before completion of the hiring process.
Candidates with additional questions or concerns regarding any recruiting communications or Kapitus’ recruiting process in general should email recruiting@kapitus.com
Kapitus has helped small and midsize businesses access capital for two decades, funding roughly $2 billion to date and building toward $6 billion and beyond. We originate, decision, fund, and service financing every day across a growing set of products and partner channels. As we scale, we are investing in the technology and quality foundation that growth depends on.
We are standing up a modern quality-engineering practice built on automated regression, and we are hiring a hands-on QE Automation Lead to own the strategy, the framework, and the team that delivers it. You will set the automation standards, architect and govern the framework, mentor the engineers, and make release readiness measurable, in close partnership with Product, Development, DevOps, and Architecture. You will also lead the shift from a largely manual regression model to reliable, pipeline-gated automation, the change that lets Kapitus release faster with higher confidence.
What You Will Do:
- Lead the strategy. Own the automation strategy and technical direction across multiple QE teams, products, and delivery streams.
- Partner across the org. Align quality priorities, delivery risks, and release-readiness expectations with Product, Development, DevOps, Architecture, and Leadership.
- Build and govern the framework. Design, evolve, and govern scalable automation frameworks and reusable components using Playwright with TypeScript.
- Set the standards. Establish automation standards for test design, code quality, reviews, branching, test data, maintainability, reporting, and framework adoption.
- Stay hands-on. Develop, review, debug, and optimize automated tests across UI, API, integration, end-to-end, and data-validation layers.
- Wire quality into CI/CD. Integrate automated tests and quality gates into CI/CD pipelines for fast, reliable feedback across the delivery lifecycle, and move toward automation in the Definition of Done.
- Make quality measurable. Define and report actionable quality and automation metrics: coverage, pass rate, defect trends, escape rate, flaky-test rate, execution time, and automation effectiveness.
- Prioritize by risk. Use data and risk-based analysis to prioritize automation investment, identify quality gaps, and communicate product risk and release readiness to technical and non-technical stakeholders.
- Lead root-cause analysis. Lead root-cause analysis for complex failures and recurring defects, separating application, environment, test-data, integration, and automation issues.
- Mentor and grow the team. Guide, review, pair with, and grow the QE engineers, raising engineering standards across the team.
- Coordinate distributed delivery. Coordinate work across distributed teams, remove roadblocks, and drive consistent execution and accountability.
- Champion shift-left quality. Improve story testability, acceptance criteria, test planning, and in-sprint automation so quality moves earlier.
- Lead the shift to automation. Lead the transition from manual regression to automated regression, retiring manual effort as automated coverage proves out and runs green in CI, and capturing manual test cases into automation as you go.