[Hiring] Staff Software Engineer, Golang @Block Labs

Role Description

We build distributed, transactional backend platforms across crypto, fintech, and real money gaming. High volume, multi-tenant, real-time. Balances, payments, and player-facing decisions depend on them, so correctness is not negotiable and mistakes are visible immediately. The work spans several products and follows business priorities, so what you own will change over time. You will build and own distributed, transactional backend services in Go, as an individual contributor.

Ownership has a specific meaning here:

• You receive an outcome and its constraints, not a decomposed backlog.
• You identify the decisions nobody has made and gather the context to make them.
• You define scope and sequencing.
• You make the architectural and implementation decisions.
• You implement the system rather than delegating it.
• Others will contribute to it, and you own the conditions that let them do so without degrading it.
• You ship it, and you remain responsible for how it behaves in production.

Agents are the normal means of production here, not an optional aid. That does not reduce the need for engineering judgement, testing, or operational ownership; it increases how much of each one engineer carries.

You will collaborate with product, engineering, infrastructure, and QA throughout, and you will need to be good at it, because nobody will be coordinating it on your behalf.

Qualifications

• Deep proficiency in Go on high volume, transactional systems.
• Strong judgement on multi-tenancy, event-driven architecture, queues, and the failure modes each brings.
• A repeatable agentic engineering system you built deliberately.
• Evidence of carrying the whole chain yourself, from incomplete objective to a system you shipped and then owned in production.
• Judgement under ambiguity.

Requirements

• Background in fintech, real money gaming, or other high traffic consumer products where money is at stake.
• Experience with rules engines, real-time scoring, or decisioning systems.
• Prior experience designing APIs for multi-tenant or white label products.

What this role is not

• Not a management or tech lead role. There is no team reporting to you and no plan to create one.
• Not an architecture or advisory role. You will not set direction for others to implement.
• Not a squad role. There is no prioritised backlog and no one assigning you work.
• Not a role where you own one layer of somebody else’s implementation, or where someone else owns verification and production readiness on your behalf.
• Not a role where agents are an optional productivity aid you reach for occasionally.

What kind of culture can I expect?

Mature, mission-driven, and low-ego. We value clarity over noise, outcomes over theatrics, and pace without chaos. If you’re one of the smartest minds in your craft and want to build with other experts, you’ll feel at home here.