Automation QA Lead (.NET)

O projekcie

The work

We’re scaling engineering to match a growing business and a full commitment to AI. The platform is in active transformation across performance, architecture, and AI, and quality has to keep pace with it. As Automation QA Lead you’ll be the technical heart of our testing. You’ll be a hands-on engineer first and a lead second. You’ll write tests in C#, break things, and build the automation that lets us ship with confidence. You’ll also lead our QA Guild and help two Testers grow into stronger engineers.

What you get

• Competitive salary + equity: B2B, 24-29k PLN + VAT, + ESOPs
• Hybrid: 2 days in office, 3 remote
• Private healthcare, fitness, meal and phone allowance
• A team where technical opinions are welcomed, not managed
• Software that runs inside real global banks, used by millions of people every day
• Real influence over how quality is done at Meniga

Zakres obowiązków

• Generate tests at scale with AI. Use Claude Code, Cursor and similar tools to produce meaningful functional, API, integration and regression coverage quickly, and to ramp up fast on highly complex .NET codebases you’ve never seen before.
• Put quality into the pipeline. Build and own test automation in CI/CD so that every change is verified automatically, and failures tell you something useful.
• Own performance and load testing. Find the bottlenecks in database-heavy, high-volume systems before our clients’ customers do.
• Cover the full spectrum. Functional, regression, integration, API, performance and exploratory testing, with the judgement to know which one matters for a given risk.
• Lead the QA Guild. Set the technical standard, share practices across squads, and make sure testing knowledge compounds instead of living in one person’s head.
• Grow two Testers. Coach them, pair with them, give honest feedback, and show them a clear path from manual testing toward automation and engineering depth.
• Work shoulder to shoulder with engineers. Join squad discussions early, review code, challenge designs for testability, and push back when shortcuts threaten reliability. Not as bureaucracy, but because you care what ships.
• Treat Support tickets as signal. Turn production issues into better tests so the same bug never ships twice.

Wymagania

What we’re looking for

• Strong, production-hardened C#/.NET. You write real code, read complex services, and work out where they will break. You’re as comfortable in the codebase as the engineers you work with.
• AI-native. AI tools are a natural part of how you work, and you use them to multiply your output, not just to autocomplete.
• Test automation experience. You’ve built frameworks and pipelines, not just maintained scripts. You know how to keep suites fast, stable and trusted.
• Performance testing experience. You’ve designed and run load and stress tests and can interpret what the results mean.
• Database-aware. You understand data-heavy systems and can test them properly (MSSQL or PostgreSQL). This is not CRUD territory.
• A bias for tests over paperwork. You care about coverage, signal and confidence, not test plans nobody reads. Process exists to serve quality, never the other way around.
• A natural mentor. You enjoy making other people better and can inspire a small team without needing a large title.
• Can-do under constraints. On-premises bank environments are demanding. You find a way, not an excuse.
• Business-minded. You understand what’s at stake for our clients and can weigh risk sensibly.

Oferujemy

• Sport subscription
• Private healthcare
• Flat structure
• Lunch card
• Small teams
• International projects
• Free coffee
• Canteen
• Bike parking
• Free snacks
• Free beverages
• Modern office
• Startup atmosphere
• No dress code
• Mobile phone
• Free lunch

Etapy rekrutacji

• Screening (30 min call): Real projects, real decisions, real trade-offs.
• Meet the CTO (15 min): We want to understand how you think and what you care about. So does he.
• 90 min interview (onsite or call): One real quality problem (C# test automation + test strategy + AI), a discussion of performance and pipeline testing, and a conversation about how you’d lead and grow a small QA team. AI tools are welcome.