About the Role
We are building the next generation of the financial core behind a travel operations platform.
This is not a traditional accounting software role.
This is not a consumer product management role.
The platform already supports:
However, the financial model evolved organically over time inside a monolithic operational system and now requires a dedicated financial core with:
-
deterministic financial behavior
-
auditable history
-
reconciliation workflows
-
period close support
-
reliable profit calculation
-
source-of-truth ownership
We are looking for someone who can own this evolution operationally and conceptually.
What You Will Work On
You will help define and evolve:
-
financial lifecycle modeling
-
revenue and cost recognition rules
-
reconciliation workflows
-
financial event models
-
append-only history and auditability
-
accounting-period close behavior
-
profit calculation semantics
-
operational vs financial source-of-truth boundaries
The system already exists and is actively used in production.
This is not a greenfield rewrite.
Part of the financial core architecture is already implemented and currently being expanded into production-ready workflows.
Your role is to:
-
take ownership of the domain direction
-
help drive V1 safely into production
-
work closely with engineering and finance
-
evolve the model further without breaking operational workflows
-
become the long-term owner of this financial systems domain
What Makes This Role Different
This role sits between:
-
financial operations
-
systems modeling
-
platform evolution
-
accounting logic
-
engineering execution
You will work on problems like:
-
how profit should be recognized
-
how mutable supplier costs affect closed periods
-
how to reconcile operational reality with financial truth
-
what should be immutable
-
how adjustments should work
-
how finance can trust system-generated numbers
-
how to evolve legacy workflows safely
This role is heavily focused on:
-
correctness
-
explainability
-
reconciliation
-
domain modeling
-
operational realism
—not just feature delivery.
What We Are Looking For
Strong candidates usually have experience with some combination of:
We are especially interested in people who understand:
-
liabilities vs revenue
-
delayed/mutable financial truth
-
period close workflows
-
append-only financial history
-
adjustments and corrections
-
source-of-truth design
-
operational vs accounting boundaries
You do NOT need:
-
CPA background
-
formal accounting certification
-
deep distributed systems expertise
-
microservices architecture obsession
Important
This role is not about:
This is a systems ownership role centered around financial correctness and operational trust.
Team & Environment
Current constraints:
-
existing monolithic platform
-
PostgreSQL + GraphQL backend
-
low-to-medium operational volume
-
heavy operational workflows
-
partially manual finance reconciliation
-
evolving financial core architecture already in progress
You will work closely with:
Success in This Role
In the first months, success looks like:
-
understanding the current operational and financial model deeply
-
safely driving Financial Core V1 toward production readiness
-
helping finance trust system-generated numbers
-
reducing spreadsheet-based reconciliation
-
improving the explainability of the financial state
-
establishing clear ownership and invariants around financial behavior
-
helping evolve the platform toward a reliable long-term source of truth