Sr. Staff Backend Engineer

<p>&nbsp;</p> <p>The Senior Staff Backend Engineer owns the core services at the heart of the platform: the data-intensive computation layer that turns curated financial and operational data into correct, reproducible, fully traceable results.</p> <p>This is the structured engineering beneath the product. Not dashboards, not an LLM wrapper. The services that do the heavy computation and stand behind every number the platform produces.</p> <p>The output of this layer sits next to externally reported financials, so correctness is not negotiable. Every result must be traceable to source, reproducible, and auditable, with clear guardrails keeping verifiable results separate from anything that requires human review. Nothing is ever quietly fudged to make the math look complete. That standard is the reason this role exists at this level.</p> <p>The architectural bet is configuration over code. A new customer or a new domain should be a configuration change, not a fork. You build the composable component library and the runtime that executes it, so the platform absorbs variation without accumulating bespoke code paths nobody can safely change two years from now.</p> <p>This role is forward-deployed. You will spend meaningful time working inside enterprise customer environments, embedded with their engineering and finance teams, rather than only in our codebase. Roughly [XX]% of your time is customer-facing engineering work and [XX]% is core platform development, with travel [SPECIFY]. You are an engineer, not a consultant: you own core services in our platform and you are accountable for their correctness whether or not you are on a customer site.</p> <p>We work this way because the gap between a system that works in a test environment and one that works against a real Fortune 500 close cycle is where the hard problems live. On customers specifically: we work with large enterprises whose finance organizations operate at significant scale and complexity. We are not naming them publicly right now, and we will talk through the customer landscape in more detail as conversations progress.</p> <p><strong>Key Responsibilities</strong></p> <p>1. Own the services that perform the platform's core financial and operational computation. Build a composable library of reusable computation components driven by configuration. Produce results that are fully traceable to their source inputs, and compute the supporting quality and confidence signals around each one.</p> <p>2. Express complex logic as correct, performant, set-based computation over the warehouse. Guarantee results reconcile and are reproducible. Own the performance and cost of the core services, not just their correctness.</p> <p>3. Build the runtime that executes per-domain configuration. New domains and use cases onboard as configuration, never as a bespoke cod