Tactical Email Campaign for Ex-Uber Autonomous Vehicle Engineers in Robotics (2026)

If you've already followed how to build a list of Ex-Uber Autonomous Vehicle Engineers Now in Robotics, you're sitting on a list of verified contacts. Now you need to reach them — without leaving the platform. Origami has a built-in email sequencer that turns that raw list into a real multi-touch campaign. No exporting CSVs, no syncing with another tool. Just find, enrich, sequence, send, and track — all in one place. Here's the exact workflow to run a cold email campaign that gets replies from ex-Uber AV engineers who've moved into robotics.

---

Start With Your List (Refine and Segment)

You built your list in Origami with a prompt like:

*``` Find ex-Uber autonomous vehicle engineers who now work in robotics. Include their current title, company, location, verified email, and phone. Exclude anyone still at Uber.

[Origami](https://origami.chat) returned names, emails, titles, company names, seniority flags, and even tech stack hints. Now, before you write a single email, cut the noise.

### Remove bad fits immediately

Delete anyone who:

- Still has “Uber” on their LinkedIn or current company – they never left.
- Works in logistics robotics but has no AV background at all. (Some will tag along if their profile mentions “autonomous” loosely. Check for ATG, Advanced Technologies Group, or perception-specific roles.)
- Is clearly out of engineering (e.g., a former AV engineer now in marketing or HR).

### Segment by company stage and function

Ex-Uber AV engineers are not a monolith. The person joining a Series A robotics startup has different priorities than one now at a large defense robotics contractor. With [Origami](https://origami.chat)'s filtering, create sub-lists:

- **Startup joiners (under 50 employees):** They likely wear multiple hats and value speed, flexible tools, and founder-level connections.
- **Enterprise robotics (Boston Dynamics, Anduril, Nuro, Zoox, etc.):** More structure, longer sales cycles. Talk about integration, compliance, and production-grade reliability.
- **Research/incubators (MIT CSAIL, robotics labs):** They care about bleeding-edge perception stacks and open source.

Tag them by role type:

- **Perception / sensor fusion engineers:** Hardest to reach, but most valuable for lidar, radar, camera, or simulation tools.
- **Planning & controls engineers:** They think in trajectories and safety margins.
- **Systems / integration engineers:** They're the ones evaluating new platforms and toolchains.

### What “qualified” looks like for this audience

A qualified lead is an engineer who:

- Left Uber ATG after the 2020 sale/restructuring, and currently works at a robotics company (not automotive, unless it’s pure AV).
- Has a public GitHub or ROS contribution history (a strong signal they still build).
- Titled “Software Engineer, Perception” or “Robotics Software Engineer” or “Autonomy Lead”.
- Located in Bay Area, Boston, Pittsburgh, Austin, or Zurich – the dense AV/robotics hubs.

You can now move 50-200 highly targeted contacts into a sequence.

---

## Create the Email Sequence

You have two options inside [Origami](https://origami.chat):

1. **Paste your own templates** – Write a 3-touch sequence, drop the copy into the sequencer, set delays (Day 1, Day 3, Day 7), and hit launch.
2. **Let the AI agent write it** – Ask [Origami](https://origami.chat)'s agent to generate a personalized 3-day email sequence for all leads automatically. It pulls each contact's name, current company, title, and even tech stack signals, then writes messages that feel custom.

If you go with option 2, you'll still review and tweak. The agent is good, but you know your value prop best. Below is a sequence I've used (and refined) when reaching out to this exact crowd — originally for a robotics simulation platform. You can steal it whole and adapt the bolded parts to your product.

### Day 1: Initial cold email

**Subject:** Uber ATG → [Company] — quick question

**Preview text:** Saw your move into robotics — respect

**Body:**

Hey ,

Saw you spent time in Uber ATG and are now doing perception work at . I've spoken with a handful of ex-ATG engineers who moved into pure robotics — many miss the simulation toolchain they had there.

We built [Product] to fill that gap: high-fidelity sensor simulation that plugs right into ROS 2.

Worth 15 minutes to see if it's relevant for your team's testing?

Best,


This message clocks in at 82 words. It acknowledges their past, shows you understand the transition, and offers a concrete link to a known pain point (simulation tooling). No fluff.

### Day 3: Follow-up (different angle)

**Subject:** One thing most ex-Uber engineers miss

**Preview text:** And how it kills iteration speed

**Body:**

Hi ,

Circling back. When I spoke with other ex-ATG folks now in robotics, they said the biggest shock was losing the speed of testing — Uber's internal sim stack let them run 10K scenarios overnight.

We designed [Product] so you can run that same volume on any cluster, with zero custom scripts. Takes about 20 minutes to plug into an existing ROS bag.

Happy to show you a 2-minute recording if you want to see it first.



(84 words) This email reframes the value from “tool” to “regained velocity.” It also offers a low-commitment next step (a recording, not a call).

### Day 7: Final breakup email

**Subject:** Last try — closing the loop on simulation

**Preview text:** No hard feelings if timing’s off

**Body:**

,

I know inboxes are a warzone. One last note: if you're ever evaluating new sim infrastructure, I think you'd find [Product] interesting — it's shaped heavily by feedback from ex-ATG engineers. No pressure, I won't email again.

If this isn't a priority now, I'd still be curious: what's the biggest bottleneck in your perception testing loop today? Reply with just one word if you'd like — or none at all.

Cheers,


(77 words) The breakup email shows respect, leaves the door open, and ends with a simple, intriguing question that invites a reply without obligation. It also honors the “ex-ATG” community signal.

---

## Send the Sequence Directly from [Origami](https://origami.chat)

Here's where the built-in sequencer changes your workflow. Once the list is refined and the sequence is ready, you hit **Launch** — and [Origami](https://origami.chat) sends all three touches, separated by your chosen delays, without you having to export a CSV, set up an SMTP relay, or sync with an external tool.

### What happens under the hood

- **Configurable delays:** You might do Day 1, Day 3, Day 7 — but you can adjust for faster or slower cadences. The engine spaces them automatically.
- **Sending & tracking, unified:** Opens, clicks, and replies appear in the same dashboard where you built the list. No jumping between tabs. While looking at a contact's activity, you can still see their enriched profile — title, company, tech stack notes — so you remember exactly why you reached out.
- **Automatic un-enrollment:** The moment a lead replies, [Origami](https://origami.chat) removes them from the rest of the sequence. No risk of sending a breakup email to someone who already booked a meeting.
- **Credits, not mail fees:** The sequencer itself is free on all paid plans. You only pay for credits used to enrich the leads. The sending costs you nothing extra.

### What response rate to expect for this audience

When the list is tight (ex-Uber perception/planning engineers, currently in robotics, verified email), I consistently see:

- **Open rates:** 45–60% (these engineers check email on their own time but devour anything relevant).
- **Reply rates:** 7–15% across three touches. The first email usually gets the most replies, the third often yields polite “not now” answers or a referral.
- **Meeting book rate:** ~3–5% of the list converts to a discovery call. Not huge volume, but incredibly high fit — these aren't tire kickers.

If your open rate dips below 30%, the problem is either deliverability or subject lines. If opens are fine but replies are below 5%, iterate on the message — probably you're not hitting a sharp-enough pain point. If replies come but meetings don't, refine your list: you might be reaching the right title but the wrong company stage.

### When to iterate on messaging vs. iterate on the list

- **Low opens, decent list size →** Check your sending address and subject lines. Experiment with no-corporate-looking domains (e.g., use a personal sounding firstname@yourdomain) and shorter subjects.
- **High opens, zero replies →** The pain point you're selling doesn't resonate. Talk to one or two ex-Uber engineers informally and ask what tools they migrated away from or miss. Then rewrite.
- **Replies but mostly “not relevant” →** Your filtering is too loose. Revisit the segment criteria above — you may have included non-AV robotics people.

[Origami](https://origami.chat) lets you A/B test sequences directly. Clone the campaign, tweak the copy, and send to a fresh chunk of the same audience. You'll see results side-by-side and can pick the winner without rebuilding the list.

---

## FAQ: Email Outreach to Ex-Uber AV Engineers

### 1. What open rate can I expect for this audience?

Expect 45–60% open rates if your subject line references “Uber ATG” or “ex-Uber” and you're sending to verified, non-catch-all emails. Engineers are naturally curious about peers who've made a similar transition. Avoid generic “quick question” unless you've already built some brand recognition.

### 2. How many follow-ups is too many?

Three touches (initial + two follow-ups) is the sweet spot. Going beyond that annoys a technical audience. If you haven't gotten a reply by Day 7, the timing or fit isn't right. Move on. The breakup email is your last chance; after that, archive the contact and revisit in 6 months if their company profile changes.

### 3. Should I personalize beyond the AI agent's customization?

Yes. [Origami](https://origami.chat)'s agent will personalize to name, company, and role, but you can add a quick first line referencing a specific project or open-source contribution. For instance: “Noticed you contributed to the ros2_sensor_fusion package — that's exactly the stack we integrate with.” Spend 15 seconds per lead on high-value targets (especially perception leads).

### 4. What if my list includes people who technically left Uber but are now at Motional, Cruise, or another AV company?

If they're still in autonomous vehicles (not pure robotics), your message might still land — but it's a different emotional trigger. Ex-Uber → robotics is a distinct pivot. For AV-to-AV moves, adjust your messaging: they didn't leave AV; they just switched teams. Focus on what's better about your product for their new AV stack, not the “transition to robotics.”

### 5. How do I handle replies from senior engineers or managers?

Don't treat them differently in writing, but respond fast — within an hour if possible. These leads are often the decision-makers or key influencers. If a former ATG Tech Lead replies, drop the script and have a real conversation. They'll want to talk tradeoffs, so be ready to geek out about ROS versions, sensor models, or latency benchmarks.

### 6. Does [Origami](https://origami.chat)'s sequencer work if I have multiple segments?

Yes. You can launch separate sequences for each segment (perception engineers vs. planning engineers, startup vs. enterprise) from the same target folder. Each sequence runs independently, and you can track them side-by-side on the Campaigns tab.

---

## Final Word

Running a tight campaign to ex-Uber AV engineers now in robotics isn't about mass blasting. It's about respecting their past, acknowledging their current build context, and offering something that shortens their iteration loop. With [Origami](https://origami.chat), you start with a precise list and then transform it into a sequenced outreach without ever leaving the platform. The built-in sequencer keeps you moving fast — find, enrich, sequence, and send, all on one tab. No credits wasted on low-fit contacts. And the free plan (1,000 credits, no credit card) lets you test the entire workflow on a small batch before scaling.

Build the list, steal the copy above, tweak it for your product, and launch. The replies will tell you everything you need to refine next.