Technical Architect

Technical Architect

The right candidate will have built and operated a product of reasonable scale. You should bring strong hands-on experience with JavaScript (TypeScript), Node.js, and AWS CDK. You'll need deep AWS experience, particularly in developing large multi-account serverless architectures using cloud-native features. Knowledge of web-based authentication systems, specifically OAuth and OIDC, is important.

Please do not apply without this experience.

This is a hands-on technical architecture role, not a traditional enterprise architecture position. You must have a strong development background - someone who has progressed from developer through to architect and is still comfortable writing code daily. You will be expected to write code alongside engineers, not just produce diagrams and documentation. If your experience is primarily in enterprise architecture, this role is not the right fit.

What you'll do

You'll lead the architectural direction for platform services used by other development teams, designing and building internal tooling and platforms whose primary users are developers. Day to day, you'll work across three engineering teams, providing technical leadership while remaining close to the code. You'll design technical services and plan system integrations, selecting platforms and technologies to meet project requirements. You'll undertake structured analysis of technical issues and translate that analysis into practical, implementable designs. You'll identify deeper systemic issues, look for opportunities to reuse components, and contribute to the development of architectural and engineering practices, principles, and standards. You'll communicate your vision and architectural decisions clearly to a wide range of internal and external stakeholders, both technical and non-technical.

Strong communication skills are essential. You'll need to articulate architectural decisions and design patterns to audiences ranging from senior stakeholders to junior developers.

Job titles we'd expect to see in your background

Technical Architect, Lead Developer, Principal Technologist, Senior/Lead Engineer, or similar roles where you combined architectural thinking with active development.

The right candidate will have built and operated a product of reasonable scale. You should bring strong hands-on experience with JavaScript (TypeScript), Node.js, and AWS CDK. You'll need deep AWS experience, particularly in developing large multi-account serverless architectures using cloud-native features. Knowledge of web-based authentication systems, specifically OAuth and OIDC, is important.

Please do not apply without this experience.

This is a hands-on technical architecture role, not a traditional enterprise architecture position. You must have a strong development background - someone who has progressed from developer through to architect and is still comfortable writing code daily. You will be expected to write code alongside engineers, not just produce diagrams and documentation. If your experience is primarily in enterprise architecture, this role is not the right fit.

What you'll do

You'll lead the architectural direction for platform services used by other development teams, designing and building internal tooling and platforms whose primary users are developers. Day to day, you'll work across three engineering teams, providing technical leadership while remaining close to the code. You'll design technical services and plan system integrations, selecting platforms and technologies to meet project requirements. You'll undertake structured analysis of technical issues and translate that analysis into practical, implementable designs. You'll identify deeper systemic issues, look for opportunities to reuse components, and contribute to the development of architectural and engineering practices, principles, and standards. You'll communicate your vision and architectural decisions clearly to a wide range of internal and external stakeholders, both technical and non-technical.

Strong communication skills are essential. You'll need to articulate architectural decisions and design patterns to audiences ranging from senior stakeholders to junior developers.