Engineering at Galoy

What you would work on

We build Bitcoin-native core banking infrastructure. Most of it is Rust.

Most work sits in two connected areas:

Our technology

The stack is built around a few foundational principles:

• Rust across the stack.
• Event sourcing for every entity (yes, every single one).
• Event-driven communication.
• Double-entry accounting.
• Modularity, with a strict dependency graph.
• Domain Driven Design.
• Hexagonal Architecture.
• Emergent Design.

What the process looks like

We keep it short and conversational. Expect:

1. First interview with our CTO. We discuss your background and technical knowledge.
2. Take-home task. You solve a realistic coding exercise.
3. Team interviews. We review your solution together and you get to know the people you would work with.
4. CEO interview. We discuss culture fit.

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. Experience in banking or financial domains is very valuable to us. This is a highly regulated and complex domain which requires knowledge beyond coding.

How to prepare

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

• Review the main work areas. Explore Lana, our Bitcoin-native core banking platform, read the docs, and browse our supporting open-source projects.
• 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. You don't need prior exposure to our specific libraries; if you've solved problems in this domain before, 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 be paid in Bitcoin, and optional relocation to El Salvador with visa support is available.