01
Financial truth before impressive demos
We start with what the system can support and explain. A compelling interface cannot substitute for correct financial boundaries.
Careers
Build financial software people can actually understand and act on.
RunwayCal is building a connected financial planning operating system for growing businesses. We care about making complex financial relationships understandable without making the underlying logic less rigorous.
We are not actively hiring right now. We are always interested in meeting thoughtful people working across financial systems, product engineering, design, and operational finance.
What we are building
The problem is bigger than another dashboard.
RunwayCal connects Commitments, Cash, Revenue, Teams, Budgets, and Scenarios into one financial picture. The work reaches across deterministic financial systems, explainable calculations, scenario modeling, financial UX, data ingestion and validation, multi-location planning, and finance workflows for people who are not finance specialists.
That also means building an architecture that can support useful assistance without handing deterministic calculations or approval decisions to AI. Some of these are continuing areas of work, not a promise that every possible capability is already live.
Working principles
How we build matters.
02
Explainability over magic
Important calculations should trace to explicit inputs and rules. AI can assist a workflow, but it should not silently own deterministic financial logic.
03
Small, deliberate releases
We prefer a bounded improvement that people can understand over a broad promise the product cannot yet keep.
04
Interfaces can change. Financial logic should remain dependable.
The product should become easier to use without making the meaning of recorded, planned, and hypothetical values unstable.
Stay in touch
Who we want to hear from.
These are areas of interest, not open job descriptions. An introduction helps us understand the kind of work you do and what you care about.
Product engineers
People who care about the behavior behind the interface, not only the visible layer.
Financial systems and FP&A practitioners
People who understand how planning, actuals, timing, and operating decisions meet.
Product designers
Designers with strong information-design instincts and respect for financial meaning.
Data and integrations engineers
Engineers who can make ingestion, validation, review, and source boundaries understandable.
Finance and software translators
People who can move between financial practice, product decisions, and clear language.