Architect

The **Principal DevOps Architect** is a senior individual-contributor architect responsible for designing, standardizing, and governing the organization’s DevOps, platform engineering, and operational reliability architecture across product teams. The role establishes reference architectures, reusable delivery patterns, and automated guardrails that accelerate software delivery while improving security, availability, and cost efficiency.

The Principal Data Architect is the senior-most individual-contributor authority for data architecture within a software or IT organization, accountable for the end-to-end design integrity of the company’s data landscape—spanning operational systems, analytics platforms, governance, and data product enablement. The role balances strategy and hands-on technical leadership: setting architecture direction, defining standards, and coaching teams while also solving complex, high-impact data design problems.

The **Principal Commerce Architect** is a senior individual-contributor architecture leader accountable for the end-to-end technical architecture of digital commerce capabilities—such as product catalog, pricing, promotions, cart/checkout, payments, order management, customer identity, and fulfillment integrations—across web, mobile, and API channels. This role designs target-state architectures, governs solution integrity across delivery teams, and ensures that commerce platforms scale securely and reliably while enabling rapid product iteration.

The **Principal Cloud Architect** is a senior individual-contributor (IC) architecture leader accountable for defining and governing cloud architecture strategies that enable secure, scalable, reliable, and cost-effective delivery of software products and internal platforms. This role shapes the target-state cloud operating model, creates repeatable reference architectures, and ensures that delivery teams can move quickly without compromising resilience, security, or compliance.

The Principal Architect is a senior, enterprise-scale technical leader responsible for shaping and governing the end-to-end architecture of critical software platforms and products. This role defines target-state architectures, sets technical direction across multiple teams, and ensures that engineering delivery aligns with business strategy, security standards, reliability expectations, and operational constraints.

The Principal Application Security Architect is a senior, highly influential individual contributor who defines and drives application security architecture across product and platform engineering. The role ensures that security is built into software design, delivery pipelines, and runtime operations—reducing breach risk while enabling teams to ship quickly and safely.

The **Principal Analytics Architect** is the senior-most individual-contributor architect accountable for the end-to-end design integrity of the company’s analytics ecosystem—spanning data ingestion, modeling, semantic/metrics layers, governance, and consumption patterns for BI, product analytics, and operational analytics. This role defines and enforces the target analytics architecture, ensures analytics solutions are scalable and trusted, and enables teams to ship analytics capabilities quickly without sacrificing quality, security, or cost efficiency.

The **Principal AI Architect** is a senior, enterprise-grade architecture leader responsible for designing, governing, and evolving AI-enabled systems across products, platforms, and internal capabilities. The role defines end-to-end AI architectures (data → model development → evaluation → deployment → monitoring) and ensures solutions are secure, scalable, cost-effective, and aligned with business strategy and responsible AI principles.

The Platform Architect defines and governs the technical architecture of the organization’s shared platforms—typically cloud infrastructure, container platforms, internal developer platforms (IDP), CI/CD foundations, runtime standards, observability, and security-by-design patterns that product and engineering teams consume. The role exists to reduce friction for delivery teams while increasing reliability, security, and cost efficiency through reusable, well-governed platform capabilities.

The Payments Architect designs and governs the end-to-end architecture of payment capabilities in a software or IT organization, ensuring secure, compliant, resilient, and scalable payment processing across channels and geographies. This role translates business goals (conversion, acceptance rate, cost, speed to market) into an actionable architecture spanning payment gateways, acquirers/processors, orchestration, ledgering, reconciliation, fraud controls, and operational monitoring.

The **Observability Architect** designs, standardizes, and evolves the enterprise approach to collecting, correlating, and acting on telemetry (metrics, logs, traces, events, and profiles) so engineering and operations teams can reliably detect, diagnose, and prevent service issues. The role establishes observability as a product-like capability—balancing reliability, cost, security, and developer experience—across distributed systems, cloud platforms, and delivery teams.

The Network Architect is a senior individual contributor responsible for designing, evolving, and governing the network foundations that enable reliable, secure, and high-performing delivery of software products and internal IT services. This role translates business and application requirements into scalable network architectures across on-premises, cloud, and hybrid environments, ensuring network capabilities keep pace with product growth, security needs, and operational resilience expectations.

The **MLOps Architect** designs, governs, and evolves the end-to-end technical architecture that enables machine learning (ML) models to be built, deployed, monitored, and improved reliably at scale. This role bridges ML engineering, platform engineering, data engineering, security, and product delivery by defining standard patterns (“golden paths”), platform capabilities, and operating controls that make ML delivery repeatable and safe.

The **Machine Learning Architect** is a senior individual contributor responsible for designing, governing, and evolving the end-to-end architecture that enables machine learning (ML) solutions to be built, deployed, operated, and improved at scale. This role bridges applied ML development and enterprise-grade software architecture, ensuring that models and ML platforms meet standards for reliability, security, cost efficiency, maintainability, and compliance.

The **Lead Workplace Architect** defines and evolves the end-to-end **digital workplace architecture** that enables employees to work securely and effectively across devices, collaboration platforms, identity systems, and corporate networks—whether remote, hybrid, or on-site. This role translates business needs (productivity, security, compliance, cost) into a cohesive workplace technology strategy and implementable architecture patterns that scale across the enterprise.

The **Lead Solutions Architect** designs and governs end-to-end solution architectures that translate business strategy into secure, reliable, scalable, and cost-effective technology implementations. This role leads architecture decisions across multiple product teams or delivery streams, ensuring solutions align with enterprise standards while still enabling rapid delivery.

The Lead Software Architect is the senior technical design authority responsible for shaping, governing, and evolving the software architecture across one or more products, platforms, or major domains. This role translates business strategy and product needs into a coherent architectural direction, ensuring systems are scalable, secure, maintainable, and cost-effective while enabling delivery teams to execute quickly and safely.

The Lead Site Reliability Architect is a senior technical leader responsible for designing, evolving, and governing the reliability architecture of production systems—ensuring services meet availability, performance, scalability, and recoverability targets as the business grows. The role sits at the intersection of architecture, platform engineering, and operations, converting reliability goals into concrete technical standards, platform capabilities, and actionable engineering roadmaps.

The Lead ServiceNow Architect is the accountable technical authority for designing, governing, and evolving an organization’s ServiceNow platform architecture to deliver reliable, secure, scalable enterprise workflows. This role translates business service-management needs (IT, employee, customer, security, and governance workflows) into pragmatic platform designs, integration patterns, and build standards that enable fast delivery without sacrificing operability or compliance.

The Lead Security Architect is the senior architecture practitioner accountable for designing, governing, and continuously improving security architectures that protect the company’s software products, platforms, and internal systems while enabling delivery velocity. This role translates business risk, regulatory expectations, and threat intelligence into pragmatic security patterns, reference architectures, and guardrails that engineering teams can adopt at scale.

The Lead SAP Architect is accountable for designing and governing the end-to-end SAP solution landscape—spanning core ERP, integrations, data, security, and operational readiness—so that SAP platforms reliably enable business outcomes at scale. This role translates enterprise strategy into SAP target architectures and roadmaps, ensures implementations are secure and supportable, and drives architectural consistency across programs, products, and delivery teams.

The Lead Salesforce Architect is accountable for the end-to-end architecture, technical direction, and platform integrity of Salesforce implementations across one or more business domains (e.g., Sales, Service, Partner, or Customer Experience). This role designs scalable solutions, enforces architecture standards, guides delivery teams, and ensures Salesforce capabilities are implemented securely, reliably, and in a way that supports business outcomes and product roadmaps.

The **Lead Quantum Architect** is a senior individual-contributor architecture leader responsible for defining, validating, and operationalizing quantum-computing capabilities within a software or IT organization, with a strong emphasis on **hybrid quantum-classical systems** and realistic near-term value in the **NISQ** (Noisy Intermediate-Scale Quantum) era. The role bridges research-grade quantum concepts and enterprise-grade engineering by producing reference architectures, selecting platforms and tooling, defining integration patterns, and guiding teams to build quantum-ready products, services, or internal capabilities.

The **Lead Privacy Architect** is the senior domain architect accountable for translating privacy obligations and company privacy principles into implementable, scalable **architecture patterns, technical controls, and delivery guardrails** across products, platforms, and data ecosystems. This role ensures privacy-by-design and privacy-by-default are consistently embedded into software and data architectures—from early product discovery through implementation, operations, and incident response.

The **Lead Platform Architect** designs and governs the technical architecture of an organization’s internal and/or customer-facing platform capabilities (e.g., cloud landing zones, Kubernetes platforms, CI/CD, identity, networking, observability, and developer experience foundations). The role ensures platform architecture enables product teams to deliver software quickly and safely while meeting reliability, security, and cost objectives.

The **Lead Payments Architect** designs and governs the end-to-end technical architecture for payment capabilities—authorization, capture, settlement, refunds, chargebacks, reconciliation, and ledger integration—ensuring the platform is **secure, resilient, compliant, and scalable**. This role translates business payment objectives (conversion, cost, risk, global expansion) into **reference architectures, patterns, and concrete implementation plans** that delivery teams can execute.

The Lead Observability Architect designs, standardizes, and evolves the organization’s observability strategy across systems, services, and infrastructure—ensuring engineering teams can reliably detect, diagnose, and prevent customer-impacting issues. This role exists to move observability from fragmented tooling and ad hoc dashboards to a cohesive, scalable, and cost-effective capability that improves reliability, developer productivity, and operational decision-making.

The Lead Network Architect designs and governs the enterprise network architecture that enables secure, reliable, high-performance connectivity across data centers, cloud environments, offices, and remote users. This role translates business and product needs (availability, latency, scale, compliance, cost) into network blueprints, standards, and roadmaps, and leads complex network transformations from concept through implementation and operational handoff.

The **Lead MLOps Architect** designs and governs the end-to-end architecture that enables machine learning (ML) models to be reliably built, tested, deployed, monitored, and improved at scale. This role converts ML experimentation into **repeatable, secure, compliant, and cost-effective production operations** by establishing platform patterns, reference architectures, and engineering standards across teams.

The Lead Machine Learning Architect is a senior technical architecture role accountable for defining, governing, and evolving the end-to-end machine learning (ML) and MLOps architecture used to build, deploy, and operate ML-powered products and internal decision systems. This role translates business and product goals into secure, scalable, observable ML platform and solution designs, enabling multiple delivery teams to ship high-quality models reliably and cost-effectively.