About the training program
The Structure.fi Engineering Residency is a 3‑month, paid, full‑time, in‑office program for ambitious software engineers who want to go deep on AI + algorithmic trading. You’ll join our team in Paris and work on the same infrastructure, codebase, and problems as everyone else — no toy projects, no simulations. We design this phase like an elite sports camp: high intensity, constant feedback, ruthless focus on fundamentals and output. At the end of 3 months, we decide whether you join the core engineering team or walk away with a sharper toolkit and a much steeper career trajectory.
What you actually get
Our operating principles
01
Intensity
We treat engineering like a competitive sport, not a cozy desk job. Sunday–Thursday in the office, with nights and weekends when the mission demands it. We move fast, break down problems, and expect you to keep up. If you want autopilot mode, this isn’t it.
02
Mastery
We care about fundamentals: systems design, performance, correctness, and clear thinking under pressure. You’ll get direct feedback on your code, architecture, and communication — constantly. The goal is to leave you unrecognizably better than when you arrived. Not just “more experienced,” but genuinely world‑class in the making.
03
Ownership
There are no spectators here. Everyone owns problems end‑to‑end: design, implementation, testing, and production. You’ll be trusted with real surface area and held accountable for outcomes, not tickets closed. We expect you to see around corners, flag risks, and drive decisions. “That’s not my job” doesn’t exist inside this team.
By the numbers
Days in residency
Annualized pay
Chances to earn a spot on the core team
Possible upside
Your 3-month progression
01
Learn the Arena
You ramp into our stack, tools, and trading context. You’ll read code, ship small but real changes, and learn how AI‑driven strategies flow from design to live execution. The goal of this phase is simple: prove you can learn fast, ask sharp questions, and handle real responsibility quickly — without being handheld.
02
Ship to Production
You move from small tasks to owning meaningful features or infra components. That might mean touching data pipelines, backtesting tools, risk checks, or monitoring. You’re expected to spec changes with teammates, implement them, write tests, and help get them into production. We start to see how you handle deadlines, uncertainty, and the tradeoff between speed and safety.
03
Own a System
You take responsibility for a specific slice of the platform — a service, a set of workflows, or a key tool. You’re now the first line of defense when something breaks and the person driving improvements in that area. We watch how you coordinate with others, manage complexity, and think a few steps ahead. This is where we see whether you think like a core team member, not just a contributor.
04
Prove You Belong
In the final stretch, you’re operating as close to a core engineer as possible. You’re expected to propose improvements, lead small projects, and help newer teammates or trialists. We’ll give you direct, unfiltered feedback about your trajectory and let you respond. At the end, we decide: core role with upside — or a clean, well‑paid, high‑learning exit.
Who this program is built for
Backers & Backgrounds
MIT
Jump Trading
Polychain Capital
Investors of Coinbase
Chicago Trading Company
Investors of Solana
KCG Holdings
Skills you will master
Core CS
Data structures, algorithms
Distributed systems
Messaging, partitions, failures
Concurrency
Threads, async, locks
Latency & throughput
Profiling, tuning, bottlenecks
Trading architecture
Orders, fills, risk limits
Backtesting
Simulation, P&L, slippage
Reliability
On-call, SLOs, incidents
Observability
Metrics, logs, traces
Execution habits
Deep work, hard deadlines
Ownership
End-to-end systems
Team practice
Reviews, feedback, pushback
Market reaction
Fast, informed decisions