Head Of Software Architecture

Core Responsibilities

• Enterprise Architecture & Complex System Design
• Technical Team Leadership
• AI-Based Product Architecture & Delivery
• IoT, Edge, and Industrial Systems Architecture
• Cloud, SaaS, and Multi-Tenant Architecture
• Engineering Productivity & AI-Enabled Development

Reporting & Operating Model

• Reports to: Chief Product & Technology Officer (CPTO)
• Embedded collaboration with: Vertical engineering leaders (Platform, SCADA, EMS, APM, CloudOps, CAM/FSM/Product Ops)
• Product Management and Product Marketing on AI-based product introductions
• CloudOps and Security on infrastructure and compliance posture

Operating Principles

• Architecture in service of the business, not architecture for its own sake
• Pragmatic standardization — enough consistency to scale, not so much it stifles teams
• AI-first thinking applied responsibly, with attention to data quality, safety, and reliability

Skills & Profile

• Required Experience

• 15-20 years of progressive experience in software engineering, with significant time spent in architecture and technical leadership roles
• Enterprise Architecture & Complex System Design: demonstrated experience architecting large-scale, high-complexity systems with significant operational stakes
• Technical Team Leadership: proven ability to lead and mentor senior engineers and architects across distributed teams
• Trading/Transactional Systems: experience building high-throughput, high-integrity trading or transactional systems where correctness and performance are non-negotiable
• AI Product Delivery: track record architecting and shipping end-to-end AI-based product introductions, from concept to production launch
• Hands-On Development: an architect who still codes — genuinely enjoys building, not just designing
• IoT Data Acquisition: experience with systems that ingest and process high-volume telemetry from distributed physical assets
• Edge Devices & Power Plant Controllers (PPC): familiarity with edge computing architectures and industrial control systems
• Renewables / Energy Industry Experience: ideally direct experience in renewable energy or broader energy sector software (strongly preferred, not required)
• Machine Learning & Data Science: solid working knowledge sufficient to make informed architectural and platform decisions
• MCP & LLM-Based Products: hands-on experience with Model Context Protocol, development LLMs, and building LLM-based product features
• Cloud Platforms: deep experience with GCP and/or AWS at an architectural level
• AI Development Tooling: experience selecting and rolling out AI dev tools that meaningfully increase engineering team productivity
• SaaS & Multi-Tenant Architecture: advanced experience designing and scaling multi-tenant SaaS applications
• Mobile App Development: working knowledge of mobile architecture and delivery, sufficient to guide teams building mobile experiences

Core Capabilities

• Strong systems thinking with the ability to zoom between enterprise strategy and line-level code
• Executive-level communication — able to translate architectural tradeoffs into business terms for the CPTO and executive team
• Comfortable operating with significant technical authority while remaining collaborative and low-ego
• Genuine enthusiasm for staying current with the fast-moving AI and LLM landscape

Background Fit

• Principal Engineer, Distinguished Engineer, VP of Engineering, or Chief Architect background
• Experience operating in a scaling, multi-product SaaS organization
• Comfortable being both the enterprise architecture authority and an individual contributor when the problem demands it
• Success Metrics (KPIs)

• Number of AI-based product capabilities architected and shipped to production per year
• Measured productivity gains (velocity, cycle time) attributable to AI development tooling rollout
• Reduction in cross-vertical architectural inconsistency and duplicated platform investment
• System reliability and performance metrics for enterprise-critical and transactional systems
• Adoption rate of architectural standards and reference designs across engineering teams

Qualitative 360° Feedback from Engineering Leaders on Technical Leadership Effectiveness

• This role is not a purely strategic or advisory position removed from the codebase, and it is not a people-management role focused primarily on process and reporting.
• The Head of Software Architecture is expected to remain a credible, hands-on technical contributor throughout their tenure.
• The role also does not own product roadmap prioritization or commercial strategy — those remain with Product Management and the CPTO — but it directly shapes what is.