Platform Engineer - Backend & API Infrastructure

SCRYPT is a Swiss-based institutional digital asset partner behind firms starting or scaling their digital asset journey. Headquartered in Zug, we combine market access, proprietary technology, and Swiss regulatory oversight to enable institutions trade, custody, and invest in digital assets with confidence.

We serve banks, brokers, fintechs, payment service providers, family offices, asset managers, hedge funds, crypto projects, and commodity traders, institutions that require high-performance execution and a trusted partner for digital assets.

We're building the infrastructure layer that powers multiple crypto and trading products, and we're looking for a backend engineer who thinks in systems, not just features. You'll own the design and development of our core APIs and platform services, from how we model financial transactions to how internal and external products consume data. This isn't a ticket‑taking role. You'll be expected to question requirements, push back on shortcuts, and make opinionated decisions about how the platform should be structured for the next two to three years, not just the next sprint.

The work spans a modular backend architecture built primarily in Java or Go, with Python in the mix for data pipelines, scripting, and tooling. Postgre

SQL‑based data modelling, async job processing, and integrations with exchanges, wallets, and compliance systems are core to the role. You care deeply about correctness, especially in a financial context where an off‑by‑one error or a missing audit trail has real consequences.

You bring strong analytical instincts to everything you touch. When a system is slow, you instrument and measure before you optimize. When a data model feels off, you trace it back to the business logic before you redesign the schema. You're comfortable reading through raw logs, writing ad‑hoc queries to understand system behaviour, and translating what you find into clear technical decisions with documented tradeoffs.

You've worked in environments where things were moving fast and you've seen what happens when shortcuts compound, and you know how to make the case for doing it right without stalling delivery. You're comfortable using AI coding tools (Copilot, Cursor, or equivalent) as a force multiplier, but you know the difference between generated code that's good and generated code that just looks good, you review AI output with the same critical eye you'd apply to a junior engineer's PR.

Experience in crypto, fintech, or any regulated industry is a strong plus, particularly if you've worked with event sourcing, immutable ledgers, or exchange API integrations.

You have enough Dev Ops exposure to be dangerous, you can write a Docker file, reason about a CI/CD pipeline, and configure infrastructure without needing a dedicated ops person to hold your hand. But more importantly, you ask good questions about it: why is this deployed this way, what happens when this service goes down, who gets paged and why. You don't need to be a cloud architect, but you should be someone who takes operational ownership of what you build, monitoring, alerting, and reliability are part of the job, not someone else's problem.

We run on AWS and use standard tooling; what matters more than specific stack knowledge is the mindset that infrastructure decisions are engineering decisions, and you're willing to own them.

• Design and develop core APIs and platform services powering multiple crypto and trading products
• Own Postgre
  
  SQL‑based data modelling for financial transactions, ensuring correctness and auditability
• Build and maintain integrations with exchanges, wallets, and compliance systems
• Implement and manage async job processing, queues, and event‑driven workflows
• Instrument, measure, and optimize system performance based on data, not assumptions
• Write ad‑hoc queries, read raw logs, and translate findings into clear technical decisions with documented tradeoffs
• Review all code, including AI‑generated output with a critical eye before it reaches production
• Take operational ownership of what you build: deployment, monitoring, alerting, and reliability
• Collabora…