Search Results for: Jenkins

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 Integration Architect owns the end-to-end architecture and technical direction for how systems connect, exchange data, and expose capabilities across a software or IT organization. This role designs integration patterns and platforms (API, event streaming, messaging, iPaaS/ESB) that enable product teams and enterprise functions to deliver secure, reliable, and scalable integrations with predictable delivery outcomes.

The **Lead Infrastructure Architect** designs, evolves, and governs the target-state infrastructure architecture that powers reliable, secure, cost-effective delivery of software products and internal platforms. This role leads architecture decisions across cloud, on-prem (where applicable), networking, identity, compute, storage, and operational tooling—translating business and engineering needs into practical reference architectures and roadmaps that teams can implement.

The Lead Enterprise Architect (LEA) defines and governs the enterprise-wide technology architecture that enables the company’s business strategy, product strategy, and operational needs. This role aligns platforms, applications, data, integration, security, and delivery practices into a coherent target-state architecture and pragmatic transition roadmap.

The **Lead Digital Twin Architect** defines and evolves the end-to-end architecture for digital twin capabilities—spanning data ingestion, semantic modeling, simulation/analytics, APIs, and operational governance—so that software products and IT platforms can represent, observe, and optimize real-world entities (assets, systems, processes, or environments) in near real time. This role exists in a software company or IT organization to **standardize how digital twins are modeled and delivered**, reduce integration complexity across domains, and accelerate product teams building twin-enabled applications.

The **Lead DevOps Architect** is a senior, hands-on architecture leader responsible for designing, governing, and evolving the enterprise DevOps and platform engineering architecture that enables secure, reliable, and fast software delivery at scale. This role defines reference architectures, CI/CD and Infrastructure-as-Code (IaC) standards, reliability patterns, and observability approaches while partnering closely with engineering, security, and operations teams to drive consistent implementation.

The Lead Data Architect designs, governs, and evolves the enterprise data architecture that enables reliable analytics, product data capabilities, and operational data flows at scale. This role translates business goals and product strategy into robust data platform patterns—covering data modeling, integration, storage, metadata, security, and lifecycle management—while ensuring the architecture is implementable by engineering teams.

The Lead Commerce Architect is accountable for the end-to-end architecture of digital commerce capabilities—spanning storefront, catalog, pricing, promotions, cart, checkout, payments, order management integrations, and post-purchase experiences—ensuring these capabilities are secure, scalable, maintainable, and aligned to business strategy. This role designs and governs a coherent commerce architecture across product teams, integration teams, and platform engineering while enabling fast, reliable delivery.

The **Lead Cloud Architect** is accountable for designing, evolving, and governing the organization’s cloud architecture to enable secure, reliable, cost-effective delivery of software products and internal platforms. This role translates business and product strategy into cloud-native reference architectures, landing zones, patterns, and guardrails that engineering teams can adopt at scale.

The Lead Application Security Architect is a senior, hands-on security architecture leader responsible for designing, governing, and continuously improving the security of application ecosystems across the software delivery lifecycle. The role translates business and product goals into secure-by-design architectures, patterns, and engineering guardrails that reduce risk without slowing delivery.

The **Lead AI Architect** is a senior technical leader responsible for defining, governing, and evolving the enterprise AI architecture that enables reliable, secure, and scalable AI/ML and GenAI capabilities across products and internal platforms. This role translates business strategy into an executable AI architecture roadmap, balancing innovation with operational rigor, cost control, and compliance.

The Integration Architect designs and governs the technical approach for connecting applications, services, data sources, and external partners across a company’s technology landscape. The role ensures integrations are secure, reliable, scalable, and maintainable, enabling business capabilities to flow end-to-end (e.g., order-to-cash, customer onboarding, billing, identity, analytics). This is a senior individual-contributor architecture role focused on integration patterns, API strategy, eventing, middleware, and operational excellence.

The **Infrastructure Architect** designs, guides, and governs the technical infrastructure foundations that applications and platforms run on—across cloud, on‑premises (when applicable), networking, identity, compute, storage, and operational tooling. The role translates business and product needs into resilient, secure, scalable, and cost-effective infrastructure architectures, then partners with engineering and operations teams to implement and continuously improve those designs.

The Enterprise Architect is a senior, cross-domain architecture leader responsible for defining and governing the organization’s target technology landscape, ensuring that platforms, applications, data, integration, and security decisions collectively support business strategy. This role translates business capabilities and strategic priorities into actionable architecture roadmaps, standards, and investment guidance across product and IT portfolios.

The **DevOps Architect** designs and governs the end-to-end technical architecture for software delivery and operations, enabling teams to ship reliably, securely, and repeatably at scale. This role translates business and engineering priorities into a coherent platform and automation strategy—covering CI/CD, infrastructure-as-code, container orchestration, observability, reliability practices, and secure-by-default delivery patterns.

The Data Architect designs and governs the data architecture that enables reliable, secure, and scalable data products across a software or IT organization. This role translates business and analytic needs into durable data models, integration patterns, storage strategies, and governance mechanisms that support operational applications, analytics, and AI/ML use cases.

A Commerce Architect designs and governs the end-to-end architecture of digital commerce capabilities—covering storefront experiences, product and pricing services, cart/checkout, payments, order management integrations, customer identity, and supporting operational processes. The role ensures commerce solutions are scalable, secure, compliant, and aligned to business goals such as revenue growth, conversion improvement, and faster time-to-market.

The **Cloud Architect** designs, governs, and evolves the organization’s cloud platforms and cloud-native solution architectures to ensure they are secure, scalable, cost-effective, and operable. This role translates business and product needs into pragmatic target-state architectures and implementation guardrails that enable delivery teams to ship reliably without reinventing foundational cloud patterns.

The **Chief Architect** is the senior-most architecture leader accountable for the coherence, quality, and evolution of technology architecture across an entire software company or IT organization. The role sets architectural direction, defines standards and guardrails, and ensures that product and platform engineering decisions collectively deliver security, reliability, scalability, and speed of change.

The Application Security Architect is a senior individual contributor within the Architecture function who defines and drives secure-by-design patterns, standards, and controls for software applications and services. The role exists to reduce security risk at the design and build stages—before vulnerabilities reach production—while enabling delivery teams to ship features quickly without compromising security and privacy.