Skip to content
HomeCareers

Build the rails of tomorrow’s finance.

We are a small, focused team engineering institutional-grade financial platforms and elite blockchain services. We are always interested in talking to exceptional engineers, auditors, designers, and operators.

Built for what comes next.

How we work. How we hire.

Three rules. Every brief, every engagement, every hire passes through them.

Craft over churn

We optimise for the long horizon — clean architecture, exhaustive review, and durable systems.

Security, always

Every line of code is written knowing real money depends on it.

Convergent thinking

We hire engineers who can move between Web2 and Web3 contexts without losing rigor.

No active listings. Our inbox is always open.

If your work meaningfully overlaps with what we do — financial systems engineering, smart-contract auditing, protocol design, or institutional infrastructure — send us a note. We read every introduction and reply within two business days.

  • Tell us what you've built, reviewed, or operated.
  • Include a portfolio, repo, or post we can read.
  • Mention which of our products or services resonate.

Tell us about your work.

Sent directly to Mozaca.
Response within 2 business days.

Working on something where we could be useful in another way — press, partnerships, co-investments? Use the partner inbox.

Email the team
THE WORK BEHIND THE PRODUCTTHE DETAILS THAT MATTER

Build things that deserve trust.

Financial infrastructure brings engineering, product design, security, and operations together. Here are the problems that shape the work.

01

Engineering

Reason about accounting state, asynchronous events, integration boundaries, retries, and failure recovery.

Systems with predictable behavior
02

Product and design

Make complex money movement understandable to customers and usable by the teams operating it.

Clarity across every workspace
03

Security and operations

Make access, review, evidence, incident response, and support context part of the product conversation.

A stronger operating foundation
What should an introduction include?

Share the problems you work on, your area of expertise, and a concrete example of your contribution. Explain the decisions you made and the outcome rather than sending only a list of technologies.

Are all of these areas open roles?

These are areas of work, not a list of advertised vacancies. Use the contact path on this page to discuss relevant opportunities with the team.