Senior Software Engineer — DevOps & Platform, AI Systems
Read straight from Ford's careers page, verified 13h ago.Seekless can tailor your résumé to it.
Seekless can write your résumé for this posting first.
Before you apply
LocationDearborn, MI, United States
SenioritySenior
Company size10,000+ people
First seenOct 18, 2026 · 2w ago
Verified live13h ago
At a glanceSummarised by Seekless from the posting.
A software engineer who chose infrastructure
An agent orchestrator, not a typist
Productively lazy
Fundamentals first
First-principles thinker with vision
High agency
Skills
Linux
networking
distributed systems
Who You Are
A software engineer who chose infrastructure. You write real code — not just glue scripts. You’d be dangerous on a product team, but you’d rather build the systems that make every product team faster. Platforms, not tickets.
An agent orchestrator, not a typist. You don’t want to be a faster keyboard. You manage agents to do the heavy lifting — generating IaC, triaging alerts, writing the first draft of the runbook — while you keep your hands on the architecture and the judgment calls. The terminal is a cockpit for orchestration.
Productively lazy. Your instinct is to eliminate toil at the root. If a human is clicking through a console or babysitting a deploy, you replace them with code or an agent. Your biggest bottleneck should be deciding what to automate next — while the automation runs itself.
Fundamentals first. Linux, networking, distributed systems, how things actually fail under load. You understand the machine, not just the tool that wraps it. When the pipeline breaks at 2am, you can read the trace and fix the cause — and when an agent proposes a fix, you can tell whether it’s right.
First-principles thinker with vision. You design for the failure mode, not the happy path. You question the assumptions, simplify the system, and build for the next order of magnitude — not just today’s load.
High agency. You don’t wait for perfect specs or permission. You find a path, propose it, and move. Large organizations have walls; you figure out which ones to go through, around, or remove — and you do it constructively.