Lead Infrastructure Architect

Role Summary

The Staff Infrastructure Architect is a senior individual contributor reporting directly to the CTO. This role defines the standards for how Fleetworthy's production environments are designed, operate, and connect, covering infrastructure architecture, networking between systems, reliability, observability, and AI infrastructure and platforming. Standards set here are implemented across the organization.

This role is a peer to the Staff Software Architect. One owns how applications are built, the other owns how the environments they run on are designed and operated. Neither owns delivery. Both set the standards the organizations execute against.

Key Areas of Responsibility

• Define and own the infrastructure architecture vision across Fleetworthy's production environments, including how systems are designed, connected, and operated
• Establish centralized observability standards adopted across all teams
• Define standards for how AI workloads are hosted, scaled, and integrated across the organization
• Advise on security architecture, partnering with the security manager to ensure infrastructure decisions align with compliance requirements
• Work alongside embedded architects in Technical Operations, setting standards and providing guidance
• Partner closely with the Staff Software Architect to maintain clear, complementary standards across both domains

What We Are Looking For

• Deep expertise in infrastructure architecture, production systems design, and networking
• Strong background in observability, reliability engineering, automation, and production operations at scale
• Experience with AI infrastructure and platforming, with an eye toward architecture and security alignment
• Ability to define and socialize standards across multiple teams
• Strong prioritization skills, with a track record of focusing on the changes that will have the most meaningful impact
• Ability to influence and align across teams
• Demonstrated empathy for the teams implementing the standards they set, understanding and caring about the cost and impact of architectural decisions on others
• Clear communicator across infrastructure, development, and non-technical audiences

What Success Looks Like

• Production environment standards are clearly defined and consistently adopted across the organization
• Observability is centralized and providing meaningful operational visibility across all platforms
• AI infrastructure and platform patterns are established with clear architecture and security alignment
• The boundary with the Staff Software Architect is clear, with no ambiguity about ownership
• Embedded architects and leadership across the organization view this role as a trusted resource and point of clarity on infrastructure decisions
• Security is embedded in how infrastructure is designed, not addressed after the fact