Forward Deployed Engineer - Platform

We are a diverse team of free thinkers, and fast movers united to help investors and creators energize the global economy. We are looking for individuals who thrive in a culture of builders and overachievers and embrace high performance, transparent feedback, and a mission-first approach. Our culture shapes our way of working and gets us where we want to be.

• Seek Excellence.
• Be Selective To Be Effective.
• Be Highly Aligned, Loosely Coupled.
• Disagree Transparently.
• Encourage Independent Decision-Making.
• Build Dream Teams.

As a Forward Deployed Engineer — Platform, you'll work across two modes.

When embedded with a client, you're writing code on their problem — integrating against their systems, shipping the glue between our modules and theirs, sitting alongside their engineers and ours. Tier-1 engagements look less like SaaS adoption and more like joint engineering.

When at home base, you're hardening the shared platform that every engagement runs on — compute, networking, observability, CI/CD, validator clusters, the foundation underneath the modules. The work spans Kubernetes (EKS, GitOps with FluxCD), AWS, Kafka, secrets and key management (KMS/HSM, MPC), Postgres, and the observability stack.

Engineers rotate between the two. The deployments keep the platform honest; the platform makes the deployments scalable.

This is a senior-to-staff level role. We're open on exact level — the bar is the same, scope and influence scale with it.

• →Embrace and champion the thoughtful adoption of AI to improve team performance and business outcomes.
• →Leverage AI tools (e.g., generative AI, automation platforms, data copilots) to improve productivity, decision-making, and output quality in your day-to-day work.
• →Embed with clients on real integration work across staking, tokenization, DeFi, validators, and Edge engagements. Translate their constraints into platform requirements and ship the code that closes the gap.
• →Own and harden parts of the shared platform between deployments: validator clusters, observability, deployment tooling, the EKS environment, the data plane.
• →Generalize patterns that emerge from client work into reusable platform capabilities — so the next engagement doesn't start from zero.
• →Operate production systems where the failure mode is institutional money and reputation. On-call, incident response, postmortems
• →Contribute to architecture decisions across modules — staking, MPC quorum coordination, policy engine, vaults

• Substantial experience building and operating distributed systems in production, ideally where reliability and security are first-class concerns.
• Deep comfort with the modern infrastructure stack: Kubernetes, AWS (or equivalent), infrastructure-as-code, GitOps, observability tooling, CI/CD.
• Strong software engineering fundamentals in at least one systems-capable language (Go, Rust, Python, TypeScript — what you've shipped matters more than which).
• Experience operating systems that hold or move value — custody, payments, exchanges, key management, HSMs, MPC — or a clear track record in adjacent high-stakes domains.
• Comfort being customer-facing. You'll sit with client engineers, understand their constraints, and ship into their environment. Strong written and verbal communication.
• High agency. We operate decentralized command — squad leads own within their mandate. You should be the kind of engineer who finds the work, not the kind who waits for it.
• For staff candidates: a track record of setting technical direction across multiple teams or engagements, and of growing the engineers around you.