Senior QA Engineer

About CRT and CORA

CRT builds CORA, a supervisory technology platform used by central banks and financial regulators in more than 20 jurisdictions: regulatory reporting, supervisory workflows, analytics, AI-assisted processing. Our customers work in regulated environments and expect documented proof that a release is ready.

Delivery is about ten people. QA cuts across all of it: developers, the technical leads, client delivery, and the regulators themselves. Automated testing, test management, and release evidence are all still taking shape here, so the tooling and the working practice are yours to set.

The role

You will own how we plan, automate, execute, and demonstrate quality across product development and client releases. Hands-on test engineering, test management, and client-facing release work, in roughly that order of volume.

The authority is real. Once the agreed release evidence and controls are in place, QA can block a release here, and overriding that requires a named person in leadership taking the accountability.

What you will do

• Define how test management works in Jira and Xray: test cases, executions, evidence, release readiness, client tagging, defect traceability.
• Build automated regression coverage across backend integration tests, API contracts, and frontend smoke and end-to-end tests.
• Get test execution and useful quality gates into CI, with engineering and DevOps.
• Own the strategy for test data and shared QA environments. Developers help with implementation and upkeep.
• Lead release-readiness reviews and keep an evidence trail that stands up to internal and client sign-off.
• Run UAT conversations, triage client defects, and be clear about test scope and residual risk.
• Set the QA approach for the new workflow and case management capabilities alongside the existing CORA modules.
• Help developers improve testability and pick the right level of testing for a given change.
• Say no to process that does not make a release safer, including process we already run.

What you bring

• 5+ years in QA, test engineering, or SDET work with substantial automation responsibility.
• Strong C#/.NET test engineering: xUnit, NUnit, MSTest, or comparable.
• API and integration testing against real or containerised dependencies.
• WebApplicationFactory, Testcontainers, contract testing, or equivalent patterns.
• Frontend automation with Playwright, Cypress, or similar.
• SQL Server or strong relational fluency: queries, migrations, seeding, test data design.
• Tests, results, and coverage wired into GitLab CI or another CI/CD platform.
• Jira and Xray, or another structured test management system you have run properly.
• Identity testing across OIDC flows, tokens, realms or tenants, and machine-to-machine access.
• A reliable instinct for what is release-critical and what can wait.
• Comfort leading client-facing testing, defect, and release discussions.
• Croatian and English, written and spoken. We use both every day.
• A considered view on AI-assisted tooling for test design and analysis, including where it does not help.

You will not know every tool we use.

Useful additional experience

• fintech, regtech, or suptech
• performance and load testing with k6, JMeter, Gatling, or comparable
• security testing, DAST, SBOM, SCA
• Pact or another contract testing framework
• Storybook and visual regression testing
• test data anonymisation or synthetic data generation
• standing up a QA function in a smaller engineering organisation
• XBRL, regulatory reporting, RabbitMQ, distributed-system testing

First 90 days

Understand the main product and delivery risks, take over day-to-day QA direction, and give us a prioritised plan for test management, automation, data, environments, and release evidence.

One thing we have not settled: what the release policy should actually say, and how much evidence is enough for a client sign-off versus an internal one. We have opinions and no agreement. We would rather hire someone who argues with us about it than inherit our first draft.

Working at CRT

• Remote anywhere in the EU, with occasional trips to Zagreb.
• Flexible hours. Zagreb time is when most of us overlap.
• Direct access to developers, technical leads, founders, and clients.
• Laptop and phone provided.
• Time off above the statutory minimum is negotiable.

How we hire

Three weeks from first call to offer is the target.

1. Screening call. Fit, scope, working arrangement.
2. Technical interview or a representative case: real test code, a test strategy for a defined module, or both, followed by a conversation.
3. Psychological assessment. We explain the format and purpose before this stage.
4. Founder meeting, usually CEO and CTO.
5. Offer.

How to apply

Use the application link with this ad and include your CV. No cover letter. Links to public work are welcome, not expected.