Developer Productivity

Title: AV Developer Productivity Duration :12+ Months (Possible extension ) Work Location: Remote / West Coast Hours Fully remote but must work West Coast Hours Core Hours: 8AM-4:00PM or 9AM-5PM PDT Even if they are on the east coast, must work west coast hours Top 3 Skills: 1. Basic networking literacy. SSH (key auth, ssh-agent, port forwarding), DNS resolution, VPNs, HTTP(S) proxies, and the ability to reason about a connectivity or latency problem between a client and a remote host 1. Cross-platform comfort. Working knowledge of macOS, Windows (including WSL), and Linux: enough to follow a setup process on any of them and recognize where they differ 1. Command-line fluency. Comfortable living in a terminal: navigating a shell, reading logs, running diagnostic commands, editing config files Education – Bachelor Degree would like to see in Engineering field (Mechanical, Computer, Aerospace, does not matter) Years of experience - 2-4 years experience required What We're Looking For Git and GitHub basics. Clone, branch, diff, and read a pull request. A debugging instinct. Able to take a vague "it doesn't work," reproduce it, narrow it down, and describe it precisely. Customer-facing communication. Clear, calm, professional written communication with engineers, and good ticket hygiene (status, severity, repro steps, resolution). What Will Give You a Competitive Edge (Preferred) Prior experience in a developer support, DevOps support, or IT/platform support role. Familiarity with build and CI systems: Bazel, Buildkite, remote build execution, or comparable tooling. Exposure to the Python or C++ development ecosystems. Experience with VS Code or Cursor, and with remote / cloud-based development environments. Comfort with a public cloud (GCP preferred) and light scripting (Bash, Python) for diagnostics and automation. Soft skills: customer-facing communication, personality that likes solving problems • • • huge on communication since this will be a big part of the role – if they are a great communicator this will stand out a lot in the SSV • • • Who We Are AV Developer Productivity builds and operates the systems GM's autonomous-vehicle developers use every day to write, build, test, and ship software: the CI and build platform, remote development environments, source-hosting integrations, and the language and toolchain ecosystems underneath all of it. Our charter is to continuously improve the macro + micro productivity of the entire AV organization. Our customers are professional software engineers, and they hit us across a wide surface: different operating systems, different repos, different IDEs, different language ecosystems. This role is the first point of contact when one of them is stuck. What You'll Do Own first response. Monitor customer support channels, acknowledge incoming requests, and set the tone for a fast, professional support experience. Triage. Reproduce the issue, categorize it, assign severity, and either resolve it or route it to the right team with a clean, well-documented hand-off. Resolve the long tail. A large share of requests are niche environment or configuration issues (e.g., connectivity, setup, client-side misconfiguration) that you can solve directly without escalation. Escalate well. When an issue needs deep engineering work, escalate to the owning team with a tight reproduction and the context they need to start immediately. Improve the runbooks. Turn what you see repeatedly into documentation, FAQ entries, and runbook updates so the next customer self-serves. Cover the rotation. Participate in a shared on-call rotation for high-severity (P0/P1) escalation paths, alongside standard US-business-hours coverage. You will start focusing on a specific, concrete problem: helping customers resolve issues connecting to our remote development environments. The Windows connection path is the immediate driver for this role, and it is fundamentally a client setup, authentication, andnetworking problem. As the team's intake playbooks are handed off, the role may expand to other services and scenarios: GitHub intake, CI, Buildkite, bazel, etc. What We're Looking For (Required) Basic networking literacy. SSH (key auth, ssh-agent, port forwarding), DNS resolution, VPNs, HTTP(S) proxies, and the ability to reason about a connectivity or latency problem between a client and a remote host. Cross-platform comfort. Working knowledge of macOS, Windows (including WSL), and Linux: enough to follow a setup process on any of them and recognize where they differ. Command-line fluency. Comfortable living in a terminal: navigating a shell, reading logs, running diagnostic commands, editing config files. Git and GitHub basics. Clone, branch, diff, and read a pull request. A debugging instinct. Able to take a vague "it doesn't work," reproduce it, narrow it down, and describe it precisely. Customer-facing communication. Clear, calm, professional written communication with engineers, and good ticket hygiene (status, severity, repro steps, resolution). What Will Give You a Competitive Edge (Preferred) Prior experience in a developer support, DevOps support, or IT/platform support role. Familiarity with build and CI systems: Bazel, Buildkite, remote build execution, or comparable tooling. Exposure to the Python or C++ development ecosystems. Experience with VS Code or Cursor, and with remote / cloud-based development environments. Comfort with a public cloud (GCP preferred) and light scripting (Bash, Python) for diagnostics and automation. Engagement Details Starting scope: RDE customer support, with possible expansion across our service portfolio over time.