On the surface, it's "send an invoice, collect money."
Then reality shows up: usage-based pricing with committed minimums, quarterly true-ups, mid-cycle plan changes with prorated credits across multiple currencies, and revenue recognition that stands up to ASC 606 audits.
Every edge case creates two more. "Correct" depends on contract language written by lawyers who've never seen a database schema. A small modeling mistake today becomes a painful migration six months later.
This is the kind of problem space we find interesting.
The 1 to 10 Journey
We've built the foundation. Product–market fit exists. Customers are live, running real money, real contracts, and real compliance through the system.
Now comes the hard part: scaling without breaking what works.
This is the 1 to 10 phase—where early architectural decisions compound, hiring mistakes are expensive, and the right people have disproportionate impact. You won't inherit a playbook. You'll help write it.
The Role
We're looking for an Engineering Manager who treats engineering management as a systems problem, not a career milestone.
You'll lead engineers while staying close to the technical core—owning architecture, modeling decisions, and execution quality in a domain where correctness matters as much as velocity.
What You'll Do
Technical & Product Ownership
* Build and evolve core platform features
* Design and ship APIs, services, and integrations that power billing automation, usage metering, invoicing, revenue recognition, and financial reporting.
* Model complex financial workflows
* Work deeply on pricing logic, proration, true-ups, multi-currency handling, approval workflows, and event-driven billing pipelines—where small decisions have long-term consequences.
* Make architectural trade-offs
* Balance "ship it now" against "live with it forever" while scaling systems that process high-volume usage data and real-time financial calculations.
* Stay technically fluent
* You won't write code every day, but you'll review PRs, catch subtle bugs, and guide design discussions with confidence.
* Lead and grow the engineering team
* Mentor and manage engineers across experience levels, setting clear expectations and raising the bar on ownership, execution, and quality.
* Create high-output systems
* Establish clear problem definitions, focused execution cycles, code reviews that actually catch issues, and enough slack for engineers to think—not just ship.
* Debug team dynamics like software
* Observe signals, form hypotheses, intervene deliberately, and measure outcomes—whether the issue is delivery, alignment, or collaboration.
* Build the team intentionally
* Design interviews that surface real problem-solving ability, not just pattern matching. At this stage, every hire shifts the average.
Cross-Functional Collaboration
* Work closely with Product, Finance, and Customer Success to translate real-world contract terms into correct, scalable systems
* Partner with stakeholders to solve ambiguous problems where requirements evolve and trade-offs are unavoidable
* Ensure systems remain accurate, auditable, and compliant as the product scales
You Should Apply If:
* You have 8+ years of engineering experience, with 3+ years leading teams or owning technical direction
* You've built systems where the hardest part was correctly modeling messy, real-world business logic
* You default to first principles when no documented solution exists
* You've grown engineers by giving them problems slightly beyond their comfort zone—and supported them through productive struggle
* You're energized by constraints, ambiguity, and unsolved problems
* Billing, fintech, or payments experience is a plus—but curiosity and depth of thinking matter more than domain checkboxes
You Should Not Apply If:
* You need a fully defined problem before you can start working
* You moved into management to avoid technical complexity
* You optimize for process over outcomes
* You find edge cases annoying rather than interesting
Nice to Have:
* Experience with financial systems, billing platforms, or fintech applications
* Knowledge of SaaS business models and compliance frameworks
* API design and integration experience
* Prior experience working at a startup
* Not taking yourself too seriously
Location
Our interview process is designed to be structured, transparent, and efficient:
* R0 – Recruiter Screening: Quick conversation to assess basic fit and role expectations.
* Round 2 – HLD (High-Level Design): Evaluates your ability to design scalable systems and think through architecture.
* Round 3 – LLD (Low-Level Design): Dives into detailed design, code structure, and implementation decisions.
The process may vary slightly depending on the role and whether we feel it would be useful for you to connect with additional members of the team.
#J-18808-Ljbffr