Principal, Enterprise Technology Architect

About Us

Mercedes-Benz USA, headquartered in Atlanta, GA, is responsible for the sales, marketing, and service of Mercedes-Benz and Maybach products in the United States. Our people demonstrate a strong commitment to our corporate values, customer experience, operational excellence, and continuous improvement. We are looking for diverse, top-notch individuals to join the Mercedes-Benz team and uphold these hallmarks.

Job Overview

The Enterprise Technology Architect owns the technology foundation of CodeCraft, the NAFTA shared engineering platform — the runtime, cloud infrastructure, developer tooling, and security controls that application teams across the region build on. Where the Enterprise Solution Architect defines what is built and why, the Enterprise Technology Architect defines the technology stack and platform capabilities that make it real\: the EKS-based cloud-native runtime, infrastructure as code and GitOps delivery, the CodeCraft common libraries, Gradle plugins and managed dependency baseline (BOM), the CodeCraft CLI/forge developer tooling, the API gateway and centralized configuration, observability, and the DevSecOps controls that keep it compliant.

The role is accountable for the technical currency, reliability, and cost efficiency of the platform across a ~40-repository ecosystem — runtime and dependency version baselines, container and Kubernetes patterns, vulnerability and license remediation cadence — and for the automation, increasingly agentic, that sustains it without manual toil.

CodeCraft serves multiple NAFTA entities. The Enterprise Technology Architect works across Mercedes-Benz USA (MBUSA), Mercedes-Benz Financial Services (MBFS), and other NAFTA entities, designing platform capabilities that accommodate differing regulatory, data-residency, cloud-account, and isolation requirements from a shared core rather than entity-specific forks.

This is a hands-on architecture role\: expect to prototype, review Terraform and platform code, and pair with engineers, alongside producing designs and standards.

Responsibilities

Platform & Enterprise Technology Architecture

· Own the CodeCraft technology reference stack\: JVM and Node runtimes, container and Kubernetes (EKS) patterns, ingress/service mesh, caching, messaging (Kafka), and data-access patterns.

· Architect the cloud-native runtime and its delivery model — Helm charts, GitOps (ArgoCD), environment topology, and multi-account/multi-entity segregation for MBUSA, MBFS, and other NAFTA entities.

· Own infrastructure as code architecture\: Terraform/Terragrunt module design, state and environment layout, drift detection, and reusable infrastructure building blocks consumed by entity teams.

· Own the technical design of CodeCraft's shared engineering assets\: common-* libraries, Gradle plugins, versions BOM and dependency baselines, API gateway, config-server, and the CodeCraft CLI/forge developer tooling.

· Define developer golden paths — project templates, scaffolding, and platform SDKs — so the compliant path is the easiest path for teams in every entity.

· Architect the observability stack (metrics, logs, traces, dashboards, SLOs) and drive platform reliability, capacity, and cloud cost engineering.

DevSecOps, Governance & Standards

· Embed security into the platform by design\: container image hardening and signing, secrets management and rotation, workload and agent identity, least-privilege IAM, and software supply-chain integrity.

· Own the vulnerability and license remediation cadence across the ecosystem (SAST/SCA findings, dependency currency, EOL runtimes) and the platform-level automation that drives it down.

· Define and steward technology standards — approved runtimes and base images, dependency currency and deprecation policy, Kubernetes and infrastructure baselines — and drive adoption across NAFTA entity teams.

· Lead technical design reviews, contribute to architecture governance forums, and record decisions as ADRs.

· Ensure platform controls satisfy enterprise and entity-specific compliance obligations (TISAX, ISO 27001, and the additional regulatory requirements applicable to MBFS), with evidence and traceability.

Automation, AI & Innovation

· Evaluate emerging technologies and deliver proofs of concept that reduce toil, shorten lead time, or lower run cost; drive adoption of what proves out.

· Apply Generative AI and Agentic AI to platform engineering and operations\: autonomous agents for dependency upgrades, vulnerability and finding remediation, test and documentation generation, infrastructure diagnostics, and code review — with human-in-the-loop approval gates.

· Design the technical enablement for agents on CodeCraft\: scoped agent identities and credentials, tool/MCP integrations, agent-ready repository conventions, sandboxed execution environments, and observability over agent actions.

· Apply AI governance and responsible-AI principles to automated changes\: autonomy boundaries, auditability, review requirements, and rollback paths.

· Define and manage by platform metrics — reliability, remediation lead time, version currency, cost per workload, agent success and intervention rates.

Collaboration & Enablement

· Partner with the Enterprise Solution Architect, Security, and IAM architects to keep target architecture and delivery reality aligned.

· Work directly with engineering teams across MBUSA, MBFS, and other NAFTA entities\: onboarding to platform standards, troubleshooting runtime and infrastructure issues, and raising engineering maturity.

· Build alignment across entities on shared technology baselines, balancing central standardization against entity-specific needs.

· Communicate technical trade-offs, risks, and roadmaps clearly to both engineering and management audiences.

· Operate within Agile/SAFe/SCRUM delivery\: contribute to PI planning, the architectural runway, and enabler backlogs.

Success Measures — First 12 Months

· Standardized runtime, Kubernetes, and IaC baselines adopted across CodeCraft repositories and consuming applications, with measurable conformance.

· Platform capabilities consumed by teams in more than one NAFTA entity (e.g. MBUSA and MBFS) from a shared core, without entity-specific forks.

· Version currency and vulnerability/license posture demonstrably improved against a defined remediation cadence, with no critical/high findings past SLA.

· Observability and SLOs in place for platform services, with actionable rather than noisy alerting, and a measured reduction in cloud run cost per workload.

· At least one agentic automation in production use on the platform (e.g. dependency upgrade or finding remediation) operating within approved guardrails, with impact measured.