Search Results for: SRE

The **Senior AI Architect** designs and governs enterprise-grade AI solution architectures—spanning classical ML, deep learning, and increasingly LLM-based systems—so that AI capabilities are **secure, reliable, scalable, cost-effective, and aligned to product strategy**. This role exists to translate fast-moving AI innovation into **repeatable architectural patterns, platform capabilities, and delivery standards** that product and engineering teams can implement consistently.

The Security Architect is a senior individual contributor responsible for designing, governing, and continuously improving the security architecture of a software or IT organization. This role translates business objectives and product/engineering realities into secure-by-design patterns, reference architectures, and enforceable security controls across cloud, application, identity, data, and infrastructure domains.

The **Quantum Architect** is a senior individual contributor (IC) architect responsible for designing, validating, and governing **hybrid quantum–classical solution architectures** that can be productized or operationalized inside a software company or IT organization. This role translates emerging quantum computing capabilities (hardware, algorithms, and SDK ecosystems) into **practical, secure, maintainable architectures** that integrate with enterprise platforms, data, and delivery pipelines.

The Privacy Architect designs and governs privacy-by-design and privacy-by-default architectures across products, platforms, and internal systems, ensuring personal data is processed lawfully, minimally, securely, and transparently. The role translates regulatory and policy requirements into scalable technical patterns, reference architectures, and engineering guardrails that enable teams to build and operate privacy-preserving software without slowing delivery.

The **Principal Workplace Architect** defines and governs the end-to-end architecture for the **digital workplace**—the technologies, patterns, standards, and roadmaps that enable employees and contractors to work securely and productively across devices, collaboration platforms, identity, and endpoint services. This role exists in a software or IT organization to ensure workplace technology decisions scale, remain secure-by-design, and deliver a consistent employee experience across regions, business units, and operating models (remote, hybrid, on-site).

The **Principal Solutions Architect** is a senior individual contributor who designs and drives end-to-end solution architectures that align customer or internal business needs with the company’s product capabilities, engineering standards, and operational constraints. This role converts ambiguous requirements into secure, scalable, cost-effective reference solutions and adoption plans, while influencing product direction and architecture standards across the organization.

The **Principal Software Architect** is a senior individual-contributor (IC) architecture leader accountable for shaping, governing, and evolving the software architecture that enables the company’s products and platforms to scale safely, reliably, and cost-effectively. This role translates business strategy into technical strategy, sets architectural direction across multiple teams, and ensures solution designs align with enterprise standards while enabling high delivery velocity.

The **Principal Site Reliability Architect** is a senior individual-contributor architecture role accountable for defining, governing, and evolving the reliability, scalability, and operational excellence of critical software platforms and services. This role creates enterprise-grade reliability architectures (SLOs/SLIs, observability, incident response, capacity, resilience engineering, and automation standards) and ensures those architectures are adopted consistently across product and platform engineering teams.

The Principal ServiceNow Architect is the accountable technical authority for the enterprise ServiceNow platform architecture, ensuring the Now Platform is secure, scalable, cost-effective, and aligned to business service outcomes. This role designs and governs the platform’s target architecture across ITSM, ITOM, CMDB, SecOps, HRSD, CSM, and custom app development, balancing speed of delivery with platform integrity.

The **Principal Security Architect** is a senior individual-contributor architect responsible for defining, governing, and evolving security architecture across products, platforms, and enterprise technology landscapes. This role translates business goals, risk posture, and regulatory requirements into practical security designs that engineering teams can implement at scale without degrading developer velocity or customer experience.

The Principal SAP Architect is the senior-most individual contributor (IC) architecture role accountable for end-to-end SAP solution architecture across business domains, ensuring SAP platforms are secure, scalable, integrated, and aligned to enterprise standards. This role translates business strategy into a cohesive SAP roadmap and governs architectural decisions spanning SAP S/4HANA, SAP BTP, integration patterns, data, security, and operations.

The **Principal Salesforce Architect** is the accountable technical authority for the end-to-end architecture of Salesforce solutions across one or more business domains (e.g., Sales, Service, Partner, Field Service, Revenue/CPQ), ensuring platforms are scalable, secure, operable, and aligned to enterprise architecture standards. This role translates business strategy into platform architecture, governs solution integrity across multiple delivery teams, and sets patterns for integration, data, identity, DevOps, and environments.

The **Principal Quantum Architect** is a senior individual contributor (IC) who designs, validates, and operationalizes **quantum and hybrid quantum-classical architectures** that can be safely adopted within an enterprise-grade software or IT organization. The role translates quantum computing capabilities (near-term NISQ and early fault-tolerant roadmaps) into **practical solution patterns**, platform choices, and engineering standards that enable teams to build credible pilots and scalable products.

The Principal Privacy Architect is the senior individual-contributor authority responsible for designing, governing, and evolving privacy-by-design architecture across products, platforms, and internal systems. This role ensures that personal data is collected, processed, stored, shared, and deleted in ways that meet regulatory requirements, reduce privacy risk, and preserve product velocity through reusable patterns and enabling controls.

The Principal Platform Architect is a senior individual-contributor architecture leader responsible for the end-to-end technical blueprint of a company’s platform capabilities—typically including cloud foundation, container platforms, internal developer platform (IDP) components, shared runtime services, CI/CD patterns, observability standards, and security-by-design controls. The role exists to create a coherent, scalable, secure, and cost-effective platform architecture that accelerates product delivery while reducing operational risk and fragmentation across teams.

The **Principal Payments Architect** is a senior individual-contributor architect who defines and governs the end-to-end technical architecture for payment capabilities—covering payment acceptance, routing, authorization/capture, settlement, refunds, reconciliation, and payment risk controls—across products and platforms. This role ensures payment systems are secure, resilient, compliant, cost-effective, and adaptable to new payment methods, providers, and regulatory requirements.

The **Principal Observability Architect** is a senior individual contributor who designs and governs the enterprise observability strategy—spanning telemetry collection, storage, analysis, visualization, and operational workflows—to ensure software and IT services are measurable, diagnosable, and reliable at scale. This role builds the technical and operating-model foundations for proactive reliability management, faster incident resolution, and data-informed engineering decisions across product teams and shared platform teams.

The **Principal Network Architect** is the enterprise-level technical authority responsible for designing, governing, and evolving the company’s network architecture across data centers, cloud environments, and edge connectivity to enable secure, reliable, and scalable product delivery. This role translates business strategy and platform requirements into cohesive network designs, standards, and roadmaps, and ensures that network capabilities keep pace with software delivery velocity, resilience expectations, and security posture.

The **Principal MLOps Architect** is a senior individual-contributor architect responsible for designing, standardizing, and evolving the end-to-end systems and operating patterns that reliably take machine learning from experimentation to production at scale. This role ensures ML services are **secure, observable, cost-effective, compliant, and repeatable**, enabling multiple product teams to deliver and operate ML capabilities with predictable quality and velocity.

The **Principal Machine Learning Architect** is a senior, enterprise-grade individual contributor responsible for defining and governing the end-to-end architecture that enables machine learning (ML) capabilities to be built, deployed, operated, and evolved safely at scale. This role bridges data science, software engineering, platform engineering, and security to ensure ML systems are reliable products—not fragile experiments.

The **Principal Integration Architect** is a senior individual-contributor architect responsible for defining and governing the enterprise integration strategy across applications, data platforms, and external partners. This role designs scalable, secure, and observable integration patterns (API, event-driven, batch/ETL, and hybrid) that enable product teams to deliver capabilities faster while reducing operational risk and integration cost.

The **Principal Infrastructure Architect** is a senior individual contributor who defines and governs the target-state infrastructure architecture for a software or IT organization, ensuring platforms are secure, scalable, resilient, cost-effective, and operable. The role aligns infrastructure strategy with product and engineering goals, translating business requirements into actionable reference architectures, standards, and roadmaps while enabling teams to deliver reliably.

The **Principal IAM Architect** is the enterprise-level technical authority responsible for designing, governing, and evolving identity and access management (IAM) capabilities across workforce and customer-facing systems. This role establishes the target-state IAM architecture, security patterns, and adoption plan that enable secure, scalable access to applications, data, APIs, and infrastructure—while improving user experience and reducing operational risk.

The Principal Enterprise Architect is a senior, enterprise-level architecture leader responsible for shaping and governing the target-state architecture of a software or IT organization while enabling product teams to deliver securely, reliably, and efficiently. This role aligns business strategy, operating model needs, and technology capabilities into actionable architecture roadmaps, standards, and reference architectures that guide delivery at scale.

The **Principal Digital Twin Architect** is a senior individual contributor architect responsible for defining, governing, and evolving the enterprise architecture for digital twins—virtual representations of physical assets, systems, or processes synchronized with real-world data to enable monitoring, simulation, optimization, and autonomous operations. This role exists in software and IT organizations to ensure digital twin initiatives are built on scalable, secure, interoperable, and product-ready foundations rather than bespoke prototypes that cannot be industrialized.

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.