Job Description

On the surface, it's "send an invoice, collect money."

n

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.

n

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.

n

This is the kind of problem space we find interesting.

n

The 1 to 10 Journey

n

We've built the foundation. Product–market fit exists. Customers are live, running real money, real contracts, and real compliance through the system.

n

Now comes the hard part: scaling without breaking what works.

n

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.

n

The Role

n

We're looking for an Engineering Manager who treats engineering management as a systems problem, not a career milestone.

n

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.

n

What You'll Do

n

Technical & Product Ownership

n

n
- Build and evolve core platform features
n
- Design and ship APIs, services, and integrations that power billing automation, usage metering, invoicing, revenue recognition, and financial reporting.
n
- Model complex financial workflows
n
- 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.
n
- Make architectural trade-offs
n




- Balance "ship it now" against "live with it forever" while scaling systems that process high-volume usage data and real-time financial calculations.
n
- Stay technically fluent
n
- You won't write code every day, but you'll review PRs, catch subtle bugs, and guide design discussions with confidence.
n
- Lead and grow the engineering team
n
- Mentor and manage engineers across experience levels, setting explicit expectations and raising the bar on ownership, execution, and quality.
n
- Create high-output systems
n
- Establish clear problem definitions, focused execution cycles, code reviews that actually catch issues, and enough slack for engineers to think—not just ship.
n
- Debug team dynamics like software
n
- Observe signals, form hypotheses, intervene deliberately, and measure outcomes—whether the issue is delivery, alignment, or collaboration.
n
- Build the team intentionally
n
- Design interviews that surface real problem-solving ability, not just pattern matching. At this stage, every hire shifts the average.
n

n

Cross-Functional Collaboration

n

n
- Work closely with Product, Finance, and Customer Success to translate real-world contract terms into correct, scalable systems
n
- Partner with stakeholders to solve ambiguous problems where requirements evolve and trade-offs are unavoidable
n
- Ensure systems remain accurate, auditable, and compliant as the product scales
n

n

You Should Apply If:

n

n




- You have 8+ years of engineering experience, with 3+ years leading teams or owning technical direction
n
- You've built systems where the hardest part was correctly modeling messy, real-world business logic
n
- You default to first principles when no documented solution exists
n
- You've grown engineers by giving them problems slightly beyond their comfort zone—and supported them through productive struggle
n
- You're energized by constraints, ambiguity, and unsolved problems
n
- Billing, fintech, or payments experience is a plus—but curiosity and depth of thinking matter more than domain checkboxes
n

n

You Should Not Apply If:

n

n
- You need a fully defined problem before you can start working
n
- You moved into management to avoid technical complexity
n
- You optimize for process over outcomes
n
- You find edge cases annoying rather than interesting
n

n

Nice to Have:

n

n
- Experience with financial systems, billing platforms, or fintech applications
n
- Knowledge of SaaS business models and compliance frameworks
n
- API design and integration experience
n
- Prior experience working at a startup
n
- Not taking yourself too seriously
n

n

Location

n

Our interview process is designed to be structured, transparent, and efficient:

n

n
- R0 – Recruiter Screening: Quick conversation to assess basic fit and role expectations.
n
- Round 2 – HLD (High-Level Design): Evaluates your ability to design scalable systems and think through architecture.
n
- Round 3 – LLD (Low-Level Design): Dives into detailed design, code structure, and implementation decisions.
n

n

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.

📌 Engineering Manager (Victoria)
🏢 Keka Technologies Private
📍 Victoria