aveni - Technical Lead (Core Services)

• Significant software engineering experience, with a strong track record of technical leadership and architectural decision-making. • Deep production experience with Node.js, particularly across backend, API and distributed systems. • Strong experience designing and operating cloud-native systems on AWS. • Experience building event-driven architectures and an understanding of the challenges that come with asynchronous distributed systems. • Experience designing production systems with complex multi-tenancy, data isolation or data lifecycle requirements. • Strong experience integrating with third-party APIs and designing for rate limits, partial failures, retries and reconciliation. • A strong understanding of reliability, observability, security and operational ownership. • Experience making architectural trade-offs and communicating technical decisions clearly to engineering teams and stakeholders. • A track record of mentoring engineers and raising engineering standards. • The ability and desire to remain hands-on while providing technical direction to a team. • Production experience with Python alongside Node.js. • Experience with identity and access management technologies such as Auth0, AWS Cognito or similar. • Strong understanding of OAuth 2.0 and authentication/authorisation patterns. • Experience building software within financial services or another regulated environment. • Experience handling data residency, retention and GDPR erasure requirements at scale. • Experience contributing to Architecture Review Boards or similar technical governance forums. • Experience establishing or improving AI-assisted software engineering practices. • The Kind of Technical Lead We’re Looking For • We’re not looking for someone who has moved completely away from engineering. • You’ll still design systems, review code, solve difficult technical problems and contribute to production software. At the same time, you’ll create leverage by helping the engineers around you make better decisions and take greater ownership. • You’ll be comfortable asking questions before reaching for a solution, thinking through failure modes as carefully as the happy path, and balancing architectural quality with the realities of delivering software in a fast-growing business. • You don’t need to have used every AWS service or technology in our stack. What matters more is that you understand the underlying engineering problems, can explain the trade-offs behind your decisions, and have successfully operated the systems you’ve helped design.