Your mission with us is to establish Architecture Governance for our products, shape a robust and future-proof software architecture, and introduce effective engineering practices that enable our teams to deliver faster, safer, and more reliably.

You lead primarily through influence rather than hierarchy: by creating clarity, defining standards, facilitating alignment, and enabling teams to succeed. In this role, you work closely with our COO and act as a key sparring partner for Product and Engineering Leads.

Three major areas will define your impact:

• Design and operate a pragmatic governance model (e.g., Architecture Council, Design/Architecture Reviews, ADR/RFC processes)
• Define and maintain architecture principles, standards, and guardrails (patterns, integration standards, NFRs)
• Establish clear boundaries within which teams can make autonomous decisions (decision rights), while ensuring structured escalation and resolution of cross-cutting topics
• Guide target architectures and modernization paths (legacy/monolith to modular or service-based architectures, strangler pattern, stabilization and decoupling)
• Create architectural transparency through clear communication and visualization, enabling Product, Engineering, and Operations to speak the same language (C4 models and ADRs instead of “PowerPoint archaeology”)

• Establish and evolve shared engineering practices (Definition of Done, QA gates, release and rollback standards, observability basics, incident and post-mortem standards)
• Focus on enablement rather than control: introduce templates, “golden paths,” practical guidelines, mentoring, and communities of practice
• Build a repeatable improvement cycle based on measurement, feedback loops, and continuous adaptation

• Embed security and compliance considerations directly into architecture and delivery standards (e.g., OSS/license hygiene, SBOM approaches, audit requirements in software delivery)
• Collaborate closely with Security, Legal, and Compliance teams without becoming the formal audit owner

• Architectural decisions are transparent and traceable (e.g., through ADRs), conflicts are resolved more quickly, and defined standards are actively applied across teams
• Teams deliver with less rework and fewer production incidents 
• Clear release and rollback processes are established and consistently followed
• Modernization and product development follow defined architectural paths, with technical debt actively managed rather than merely documented
• Practice Management is perceived as enablement and support — not as gatekeeping