Senior Frontend Developer

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, and AI-assisted processing.

Be clear about what the frontend work is. Submission portals, monitoring and analytics interfaces, enterprise navigation, and a growing workflow and case management experience. These are dense, form-heavy applications that professionals sit in all day to run complex regulatory processes. Conditional fields, validation rules, big tables, multi-step flows. There is no marketing site here.

If you have ever shipped an internal tool with sixty fields on one screen and a validation rule that depends on four of them, you know the genre. Skip to the stack list below if that is all you needed to hear.

Delivery is about ten people. You would work with our frontend lead, backend engineers, delivery colleagues, founders, and clients.

The role

You will own whole user-facing areas of CORA and help shape frontend architecture across a multi-module platform. Delivery on your own surfaces, plus shared patterns and technical direction worked out with the frontend lead. Senior individual contributor.

What you will do

• Own frontend delivery end to end: requirements, interaction decisions, implementation, testing, deployment, client sign-off.
• Build and evolve the workflow and case management interfaces: task forms, case lists and details, comments, files, rich text, drag-and-drop.
• Work across CORA's submission, monitoring, enterprise portal, analytics, and workflow surfaces, following current product and client priorities.
• Shape shared component and design patterns with the frontend lead. Ant Design is the current default.
• Improve frontend architecture and build tooling where it pays off, including dependency and component library upgrades.
• Set up automated testing with Playwright or comparable end-to-end tooling, plus unit and integration tests where they earn their keep.
• Work with backend engineers on OpenAPI-generated clients, identity flows, and integration behaviour.
• Talk to clients about visible behaviour and UX trade-offs. Decide inside agreed scope; escalate the wider product choices.
• Raise the frontend standard through review, documentation, and working alongside other engineers.

What you bring

• 5+ years of frontend development with substantial production React and TypeScript.
• Complex, form-heavy business applications: conditional fields, validation, tables, files, multi-step workflows.
• Production experience with a mature component library. Ant Design especially.
• Server-state tooling such as TanStack Query, and at least one client-state approach: MobX, Zustand, Redux, Jotai.
• Real understanding of component boundaries, state ownership, error handling, and performance.
• Vite, plus enough familiarity with older tooling like Webpack or Create React App to survive what you find.
• API integration, ideally through OpenAPI-generated clients.
• Localisation and internationalisation you have done for real.
• A workable approach to frontend testing, and the ability to add coverage to an application that has none.
• Accessibility and usability, including keyboard-only operation.
• Comfort explaining UX and implementation trade-offs to clients and non-frontend colleagues.
• Croatian and English, written and spoken. We use both every day.
• A considered view on AI-assisted tooling, including where it does not help.

You will not have used every library in our stack.

Useful additional experience

• fintech, regtech, or suptech
• workflow designers or drag-and-drop interfaces with dnd-kit or comparable
• Elsa, Camunda, Flowable, or other workflow products
• TipTap, Slate, or another rich text editor
• Storybook, Vitest, MSW, visual regression testing
• Tailwind, Emotion, Less, or other styling used alongside component libraries
• Wijmo, ComponentOne, ActiveReports, AG Grid, or comparable enterprise components
• Keycloak or browser-side OIDC flows
• moving a multi-module frontend toward shared design-system patterns

Our environment

Several React and TypeScript applications, built at different times, with different frontend patterns. They share .NET backends, generated API integrations, central identity, and a common delivery process. Part of the job is making them more consistent without triggering rewrites nobody asked for.

First 90 days

Understand your area, ship with less and less supervision, and own the day-to-day architectural and client decisions in that scope.

Working at CRT

• Remote anywhere in the EU, with occasional trips to Zagreb.
• Flexible hours. Zagreb time is when most of us overlap.
• Some client engagements need temporary overlap with client hours during delivery phases.
• 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: a real frontend problem, then a conversation about the decisions and trade-offs.
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. A portfolio, GitHub profile, or links to relevant work are welcome, not expected.