Engineering Manager II

Requirements:

• 9+ years of backend engineering experience with at least 2+ years of leadership experience, including designing fault-tolerant systems and working on high-scale platforms.
• Deep expertise in distributed systems, event-driven architectures, and asynchronous job processing.
• Demonstrated ownership of systems with strict consistency and correctness requirements, such as billing, payments, ledgers, metering, or comparable transactional domains, with fluency in idempotency, exactly-once semantics, reconciliation, and audit trails.
• Proven experience optimizing availability, performance, and reliability in real-world systems under load, especially where the system is on a critical path that other products depend on.
• Strong experience with relational and NoSQL data models, especially involving complex transactional data.
• Experience leading and earning the trust of a team of experienced senior engineers, including driving rigorous technical debate to a decision.
• Familiarity with monitoring, SLOs, and root-cause analysis in production environments.
• Familiarity with hallucination mitigation strategies, such as code constraints, test scaffolding, embeddings, and context injection.
• Excellent communication and cross-functional collaboration skills, including working with finance, risk, and support stakeholders.
• A pragmatic, hands-on leader who balances long-term vision with iterative execution.

Nice To Have:

• Experience building fraud, abuse, or risk-control systems, including rules and scoring engines, velocity checks, anomaly detection, or spend and rate governors.
• Experience with payment provider integrations such as Stripe, Adyen, PayPal, or regional PSPs, as well as dunning and recovery flows, chargebacks, or PCI-scoped systems.
• Experience with multi-tenant reselling, marketplace, or platform billing, including markups, revenue share, agency or sub-account hierarchies, or white-label monetization.
• Experience working with AI tools and communication APIs such as Twilio or Plivo.
• Contributions to open-source tools, internal platforms, or engineering blogs.