How Ford is Driving Cloud‑Native Transformation: Tools, Culture, and Lessons Learned

In today’s digital‑transformation era, Satya Nadella says every company is becoming a software company, and Ford is no exception, having run cloud‑native software for six years.

Ford’s senior technologists Beckie Riss (Chief Architect, Developer Relations, Tools & Support) and Satish Puranam (Head of Cloud Technology) shared how their teams support internal platforms, tools, and processes for cloud‑native development, and how they attract talent with an advanced cloud strategy.

Team introductions Riss’s team is part of enterprise architecture, building internal platforms and tooling. Puranam’s team belongs to IT Operations, focusing on public and private cloud, product evaluation, service launch, and incident response.

Why work at Ford? Riss highlighted Ford’s comprehensive digital transformation, a strong product portfolio (second only to Tesla in EV sales), and the ability to use connected‑vehicle data to deliver over‑the‑air software updates such as BlueCruise for F‑150 and Mustang Mach‑E, improving driver experience.

When did the transformation start? In 2016, Ford’s CIO of Intelligent Mobility, Marcy Klevorn, launched a program to adopt cloud‑native application development, creating the Cloud & DevOps Growth and Software Acceleration (CDGM) team to accelerate cloud‑native apps and upskill engineers.

Puranam noted that as cloud‑native technologies become mainstream, Ford’s digital strategy evolves to reduce barriers for end‑users and enable rapid innovation.

What does success look?​ Puranam: delivering business features quickly with high satisfaction. Riss: giving engineers freedom to choose technologies and tools, fostering an “opinionated stack.”

Key tools and technologies Public cloud and open‑source stack: Kubernetes, Knative, Istio, Tekton, ArgoCD, KubeVirt, Prometheus, SigStore, Terraform, plus data platforms like Airflow, Kubeflow, Seldon. Riss’s team also builds a Backstage‑based developer portal.

Cultural transformation Ford redefined roles, educated colleagues, and embraced values of “curiosity,” “doing the right thing,” and “creating tomorrow.” Initiatives such as “PowerUp Time” give engineers four hours weekly for skill development or innovation projects.

Challenges of cloud‑native adoption Riss emphasized the need for self‑service platforms with built‑in guardrails, documentation, videos, FAQs, and one‑on‑one training. Puranam added that the rapid pace of change increases cognitive load for developers.

Ford leveraged KubeByExample tutorials to create reference applications for learning Kubernetes and Tekton.

Adoption of Tekton and CI/CD Initially using Jenkins in 2016, the team migrated to Tekton over the past 18 months, enabling developers to use reusable tasks without being CI/CD experts, and integrating Terraform for infrastructure changes.

They follow DORA‑recommended best practices such as Infrastructure as Code and incremental releases with thorough testing.

Knative and serverless experience Knative abstracts Kubernetes complexity, reducing the need for developers to manage thousands of objects and allowing them to focus on code.

Future outlook Riss believes Ford will continue adopting emerging technologies to enhance software development, though the exact future is hard to predict.