Head Of Software Architecture

ABOUT POWER FACTORS

Power Factors is a software and solutions provider leading the next generation of clean energy with Unity, one of the most extensive and widely deployed renewable energy management suites (REMS) in the market. With over 300 GW of wind, solar, and energy storage assets managed worldwide across more than 600 customers and 18,000 sites, Power Factors manages 25% of the world’s renewable energy data.*  

Power Factors’ Unity REMS supports the entire energy value chain, from monitoring and controls to market analytics. The company’s suite of open, data-driven applications empowers renewable energy stakeholders to collaborate, automate critical workflows, and make more informed decisions to maximize asset returns. Energy stakeholders receive end-to-end support, including solutions for SCADA & PPC, centralized monitoring, performance management, commercial asset management, and field service management.  

With deep domain expertise, AI-powered insights are delivered at scale so businesses can optimize assets, unlock growth, and make smarter decisions as the world rapidly transitions to clean energy. Power Factors fights climate change with code.  

*Outside China and India

Power Factors is scaling in complexity — more products, more platforms, more sophisticated buyers, and rapidly rising expectations for AI-native capability across our renewable energy software suite. In that context, the absence of a single, accountable technical vision creates real risk: divergent architectural patterns across verticals, inconsistent approaches to AI and data platform investment, and technical debt that compounds faster than it can be paid down.

The Head of Software Architecture exists to close that gap. This is a hands-on, deeply technical leadership role responsible for defining and enforcing enterprise architecture standards across Power Factors' Product & Technology organization — spanning Platform, SCADA, EMS, APM, CloudOps, and CAM/FSM/Product Ops — while personally architecting and prototyping the hardest problems the organization faces, particularly around AI-based product introductions, IoT data acquisition, and multi-tenant SaaS scalability.

This role combines the strategic scope of an enterprise architect with the credibility of a builder who still writes code, reviews pull requests, and is comfortable being the most technical person in the room.

Purpose of the Role

The Head of Software Architecture acts to define, evangelize, and enforce a coherent technical architecture strategy that allows Power Factors to scale product complexity without sacrificing reliability, security, or development velocity.

•        Enterprise-wide architectural coherence: Technical decisions across verticals are grounded in shared architectural principles, not siloed team preferences.

•        AI-native product development: New AI-based product capabilities are architected end-to-end — from data pipeline to model integration to user-facing experience — rather than bolted on.

•        Development velocity multiplication: Engineering teams are equipped with modern AI-assisted development tooling and workflows that materially increase throughput.

•        Deep technical credibility: Engineering leaders and individual contributors alike see this role as a working architect, not a slide-deck strategist.

•        Domain-informed design: Architecture decisions reflect genuine understanding of renewable energy operations — SCADA, EMS, PPC, edge devices, and grid-facing data systems.

This role acts as the connective tissue between the CPTO's organizational strategy and the day-to-day technical decisions made by vertical engineering teams.

Core Responsibilities

1. Enterprise Architecture & Complex System Design

•        Define and maintain Power Factors' enterprise architecture standards, reference architectures, and technical guardrails across all verticals

•        Lead architectural reviews for major initiatives, ensuring consistency, scalability, and long-term maintainability

•        Own the technical roadmap for cross-cutting platform capabilities (data platform, integration layer, identity, observability)

•        Design for complex, high-availability systems where correctness, latency, and data integrity carry real operational and commercial consequences

•        Partner with vertical leaders (SCADA, EMS, APM, Platform, CloudOps) to ensure local architecture decisions align with enterprise direction

2. Technical Team Leadership

•        Build and lead a distributed architecture function that operates as a trusted technical authority across Greece, Montreal, and other regions

•        Mentor senior engineers and engineering leaders on architectural judgm