Software Engineer - Database

• Build, test, and ship well-typed, well-reviewed features and fixes in Haskell services across the exchange, clearinghouse, and brokerage
• Understand the order, trade, clearing, and settlement flows end to end
• Design schema, constraints, and indexes for new features, using exact numeric types and audit trails so financial values cannot drift
• Write migrations that are lock-safe and reversible on large tables, and review the migrations of other engineers
• Read execution plans, find slow queries from production metrics, and fix the cause in the query, the index, or the access pattern
• Monitor systems, respond to alerts, and support daily operations such as settlement cycles
• Fix the cause of production issues and write down what you learned

What you bring

• 3+ years of professional software engineering experience with a functional or strongly typed programming language such as Haskell, Rust, or C++
• Strong SQL and PostgreSQL skills, including transactions and isolation levels
• Solid computer science fundamentals, including data structures, concurrency, and distributed systems: replication, consistency, retries and idempotency, and how services keep shared data correct when parts fail
• Willingness to take part in on-call and operational shifts
• Care and rigor with code and data that move money. You measure before you tune
• Good judgment with AI tools. You use them to work faster, and you read, test, and understand what they produce before you ship it
• A habit of asking why before changing something
• Sound judgment under pressure, with a calm and methodical approach when production is live
• Collaboration across engineering, operations, risk, and compliance, with a habit of documenting

Nice to haves

• Financial knowledge or experience in trading, markets, or financial services
• Bachelor's degree in computer science or a related field, or equivalent experience
• Haskell experience, particularly with PostgreSQL-backed services
• Production experience with AWS Aurora PostgreSQL
• Experience with time series or market data at volume, such as tick data, order books, or event streams
• Experience with Atlas or another declarative schema management tool