Engineering at Galoy

What you'd work on

Galoy builds Bitcoin-native core banking infrastructure that financial institutions run alongside their existing systems. Most of it is Rust. The most direct way to understand the work is to read it: much of what we build is public, from open-source libraries to source-available platforms.

Day to day, the engineering centers on a handful of things:

• Rust across the stack, from the accounting ledger to the job runner.
• Event sourcing on PostgreSQL, where correctness and auditability are first-class.
• Double-entry accounting that has to reconcile every time, because real money depends on it.
• Bitcoin and Lightning, on-chain UTXO management, and GraphQL APIs that institutions integrate against.

Browse our open-source projects →

How we think about hiring

We care more about how you reason than what you have memorized. The strongest signal for us is watching someone take an open-ended problem, ask good questions, and talk through the tradeoffs honestly. We would rather hear "I haven't done this, but here's how I'd approach it" than a confident answer that papers over the gaps.

We also read your public work. Pull requests, side projects, and the way you write about engineering tell us as much as a conversation does.

Each role still has real requirements. For our engineering roles that usually means strong systems experience, Rust proficiency (or a systems-language background you can bring to Rust quickly), and genuine Bitcoin fluency. Read the posting you're applying to; beyond that bar, what sets candidates apart is how they think.

What the process looks like

We keep it short and conversational rather than a multi-week gauntlet. Expect:

• A first conversation to get to know each other and walk through your background.
• One or two technical conversations with engineers: a working session on a real problem, and a discussion of a system you've built and the decisions behind it.
• A chance to meet the people you'd work with day to day.

We move at a pace that works for you, and we'll be clear about where you stand at each step.

What we look for

• Reasoning and tradeoffs. Every design decision has costs. We want to hear you weigh them, and know when not to reach for a given tool.
• Systems thinking. Well-developed intuition for how systems behave in practice, and what changes as requirements grow.
• Communication. Think out loud. The clearest signal is reasoning we can follow, especially when you're uncertain.
• Ownership. We're a small team with high autonomy. We look for people who find problems, scope them, and drive them forward.
• Product sense for financial software. Money systems fail in specific, costly ways. We value engineers who think about the user and the failure modes, not just the happy path.

How to prepare

If you're interviewing with us, the best preparation is:

• Skim our public repositories. The accounting ledger (cala), the Bitcoin wallet infrastructure (bria), and our event-sourcing framework (es-entity) are good places to start. You don't need to study them; just get a feel for how we build.
• Be ready to talk about systems you've built. What worked, what broke, what you'd change. Honest reflection on past work is one of the strongest signals we see.
• Practice thinking out loud. Walk us through your process, uncertainty included.
• Brush up on fundamentals, not trivia. Understand the building blocks and when to reach for them. You won't be quizzed on configuration flags or low-level protocol details.

What not to worry about

• Having used our exact tools. Nobody arrives with experience in Bitcoin-native core banking. You don't need prior exposure to our specific libraries; if you've built and reasoned about production systems, that carries over.
• Memorizing trivia. We care that you understand how the building blocks work and when to reach for them, not that you recall configuration flags or low-level protocol details.
• Getting the "right" answer. Our problems are open-ended on purpose. A thoughtful wrong turn you recover from tells us a lot.
• Sounding polished. Genuine thinking beats a rehearsed pitch. "I'm not sure, but here's how I'd find out" is a good answer.

Working here

We're a globally distributed, remote-first team that works async. We build in the open, contribute to the Bitcoin ecosystem, and ship production software that institutions depend on. Compensation can include a Bitcoin component, and optional relocation to El Salvador with visa support is available.