Senior Software Engineer (Calculations & Allocations)

What We’re Looking For

We're looking for a senior engineer to join our Calculations & Allocations team - the team that builds the core primitives the entire Maybern platform runs on. We own three systems: a custom expression language (MXL) that lets clients define any financial calculation without writing code, a workflow engine that orchestrates multi-step fund operations, and the allocation and waterfall models that determine how every dollar flows through a fund structure. The problems here are genuinely unusual - part language design, part financial modeling, part distributed systems. You should be someone who gets energized by building foundational abstractions that hundreds of downstream features depend on.

What You'll Do

To thrive in this role, you must be an entrepreneurial engineer who enjoys getting into the weeds.

Extend a financial expression language: MXL is Maybern's formula system — with its own parser, execution engine, type system, and audit framework. You'll add new functions and calculation contexts, optimize execution, and build tooling that makes complex financial logic composable and debuggable

Build workflow orchestration: Fund operations involve multi-step, stateful processes — capital calls, closings, fee postings — that must execute correctly across distributed systems. You'll design the runtime that coordinates these workflows

Model fund mechanics: Allocations, waterfalls, carry calculations, equalization — the financial primitives that determine how money moves through a fund. You'll translate intricate fund structures into configurable, auditable models that work across every customer's unique setup

Who You Are

You've built systems where correctness is non-negotiable — financial calculations, billing engines, trading systems, or similar domains where a rounding error is a production incident

You're drawn to abstraction design — building configurable primitives that generalize across use cases without collapsing under edge cases

You have strong opinions about how domain logic should be modeled and can translate a 30-minute conversation with a fund accountant into a clean data model