Technical Lead

Technical Lead

Payments only work when they are fast, trusted, and invisible. You will lead the engineering that keeps card, contactless, mobile, and e-commerce payments reliable for millions of customers and the retailers who depend on them. This role exists to turn complex payment problems into products people can use without thinking twice—and to make the team around you faster and sharper while you do it.

Performance Objectives

• Own delivery of one or more payment platforms end to end, shipping measurable improvements in authorization success, latency, and incident recovery.
• Set the technical direction for card, contactless, mobile, and e-commerce flows so new features reach production without weakening security or compliance.
• Raise engineering quality: cut defect escape, shorten lead time, and leave every critical path with clear ownership, tests, and runbooks.
• Lead a squad of engineers through design, build, and release—unblocking decisions, coaching seniors, and holding the bar on code and design reviews.
• Partner with product, risk, operations, and retail stakeholders to turn commercial goals into sequenced, outcome-based roadmaps.
• Reduce operational risk by designing for failure: observability, graceful degradation, and rehearsed incident response on payment-critical services.
• Retire or simplify legacy paths that slow change, replacing them with services the next team can extend without tribal knowledge.

Environment & Resources

You report to an engineering manager within a large payments technology organization and lead a cross-functional squad. You will have access to established platforms for issuing, acquiring, and digital wallets, plus shared platform, security, and data teams. Delivery is supported by modern CI/CD, production observability, and a change budget tied to customer and merchant outcomes—not vanity projects.

Essential Qualifications

• Proven record leading engineers who ship payment, banking, or similarly regulated, high-volume transaction systems.
• Deep experience designing resilient services: APIs, event-driven flows, idempotency, and failure handling under real traffic.
• Hands-on fluency in at least one mainstream backend stack, plus the judgment to review designs you did not write.
• Evidence of improving delivery metrics—lead time, reliability, or incident burden—not just managing a backlog.
• Comfort translating scheme rules, fraud constraints, and audit expectations into practical engineering choices.
• Clear communication with non-engineers when a trade-off affects customers, merchants, or risk.

Role Selling Points

• Work on rails people actually use: credit, contactless, mobile, and online checkout at national scale.
• Influence architecture where uptime and authorization quality are the product.
• Lead people, not a title-only “lead” who only codes in isolation.
• Late-stage stability with room to modernize how payments are built and run.
• A domain where craft shows up in fewer failed payments and calmer on-call weeks.

Call to Action

If you have led teams that made payments more reliable and easier to change, apply with a short note on a system you owned and the outcome you moved.