Staff Software Engineer

• Drove AI-tooling adoption across Yoco. Designed and delivered the company-wide Claude Code masterclass to the full ~50-engineer org, and coached engineers and colleagues from various departments one-on-one, including helping non-engineers integrate Claude into Google Slides and Sheets. The aim was leverage, not novelty: getting more shipped per engineer, not more demos per quarter.
• Owned Yoco's L3 scheme certification programme: Visa, Mastercard, and Amex across 5 card machines and 3 manufacturers. End-to-end ownership covers EMV configuration, Fime/UL test execution, acquirer-log triage, scheme submission, and failure remediation. Certification is the gate that puts a card reader in a merchant's hand and unlocks new markets; owning it means owning that gate.
• Cross-org technical interface for the payment chain. Contact point with manufacturer engineers on transaction debugging and new integrations, with acquirer counterparties during scheme certification, and with the switch team on the card machine cloud integration: often the named person on the call when an issue spans an org boundary.
• Active on both sides of team growth: interviewing and onboarding for the team. Most recently interviewed and onboarded my current EM, a Staff engineer, and a Senior engineer through one of Yoco's most demanding stacks (payments-critical paths, scheme certification, multi-manufacturer firmware), with explicit positive feedback on the onboarding.
• Shipped a customer-facing payment-screen messaging feature solo, from ideation through implementation, with MCP-driven Jira flow as the connective tissue. A working example of what an AI-accelerated single-engineer delivery loop looks like in production.