Financial Systems Engineer

The role

Legora is growing fast, and we’re building a Financial Systems team that owns the systems behind our billing, revenue and accounting, and we’re looking for a Financial Systems Engineer to build the integrations that connect them.

Your job is to make our financial data flow reliably between CRM, CPQ, ERP and whatever comes next. That means replacing manual and fragile processes with systems that Finance can trust.

This is a hands-on engineering role with a lot of autonomy, close to the business. You’ll work directly with Finance, Accounting and RevOps, and you’ll understand not just how the systems connect but why: how we book transactions, how revenue is recognised over time, and what the accounting team needs to close the books with confidence.

What You Will Be Doing

• Build and own the integration platform that keeps our financial systems in sync: CRM, CPQ, ERP and more to come. Correctness is non-negotiable, and every bug has a number attached to it.

• Design and ship event-driven services end to end: APIs, reconciliation pipelines, queues and more.

• Write idempotent, resumable sync logic against third-party SaaS APIs you don’t control, handling partial failures, retries, out-of-order events and concurrency.

• Work in Python and Azure, with infrastructure as code in TypeScript (Pulumi).

• Own the deployment path: GitHub Actions CI/CD across dev, test and prod with gated environments, plus the observability that goes with it.

• Write the tests that make the system safe to change, including unit and contract tests against recorded fixtures.

• Work directly with Finance and RevOps to turn billing and revenue requirements into systems they trust, and debug with them when reality disagrees with the data.

• Contribute to architecture decisions as the integration surface grows (new systems, entities and flows) without turning the codebase into a pile of special cases.

Who You Are

• You have 3+ years of experience building and operating backend systems in production, not just shipping features into one.

• You’re strong in Python, and comfortable enough in TypeScript to own infrastructure code (or keen to learn).

• You have hands-on experience integrating with REST APIs from SaaS applications, and you’ve moved and transformed data between them. You know what idempotency, retries, eventual consistency and reconciliation mean in practice.

• You have experience with a cloud platform, ideally Azure (AWS or GCP translates fine), and with infrastructure as code.

• You’re genuinely interested in how a business makes and books money. Experience with financial systems (billing, revenue, ERP) is a plus.

• You’re proactive, self-directed and hungry. You take ownership of a system and thrive with a lot of autonomy in a fast-moving, high-growth company.