Engineering leader • builder of teams • keeper of humans

Andrew Lloyd Watkins

I build teams where people actually want to work.

Current Staff Engineer @ Depot
Previously ServiceNow • EraDB • InfluxData
Location Remote

Zero attrition through an acquisition? That’s not luck—that’s giving a shit.

Previously kept humans happy at ServiceNow, EraDB, and InfluxData.

Email LinkedIn GitHub

Impact

Outcomes and priorities (no fluff).

Experience

Expandable details. Fast to scan, easy to go deep.

Staff Software Engineer Depot 2025—Now

Scope

[Add scope: team/area, mission, what you own end-to-end.]

Highlights

  • [Add 3–6 outcome bullets. Use outcomes you can stand behind (no invented metrics).]
  • [Add a people-first leadership bullet.]
  • [Add a systems/architecture bullet.]

Tech

[Add technologies, platforms, and domains.]

Leadership

  • [Add coaching, hiring, process, or cross-team alignment examples.]
  • [Add a “how you lead” highlight.]
Sr. Engineering Manager ServiceNow 2022—2025

Also: Engineering Manager (2022—2024)

Scope

Led teams through acquisitions. Focus: delivery + retention + team health.

Highlights

  • Led teams through acquisitions with a strong “keep the humans happy” posture.
  • [Add 2–5 more specifics: org size, products, operational wins.]

Tech

[Add stack if you want it on the resume site.]

Leadership

  • Built a culture of kind, thorough feedback.
  • [Add hiring/coaching/career ladders/process work.]
Engineering Manager EraDB 2021—2022

Scope

[Add scope: team, product area, and core responsibilities.]

Highlights

  • [Add 3–6 bullets.]

Tech

[Add technologies and domains.]

Leadership

  • [Add 2–4 people/process/cross-team bullets.]
“Senior” Engineer InfluxData 2015—2020

Also: Pretty Good Engineer (2015—2018)

Scope

[Add scope: products, systems, and core ownership.]

Highlights

  • [Add 3–6 bullets.]

Tech

[Add languages, infra, databases, and tooling.]

Leadership

  • [Add mentoring/review/architecture influence.]

Tip: keep this section brutally specific over time—swap placeholders for real outcomes as you collect them.

Selected Work

Case studies (placeholders until you add real projects here).

[Case Study Placeholder]

Problem → Approach → Result

[Add a real project when ready. Keep it short and outcome-based.]

[Tech] [Domain]

[Case Study Placeholder]

What you built • Why it mattered

[Add another case study. Avoid buzzwords. Be concrete.]

[Tech] [Impact]

[Case Study Placeholder]

Leadership • systems • product

[Add a third if you want. Two is enough if they’re strong.]

[Stack] [Team]

Skills

Grouped tags. No cheesy meters.

Leadership

[Coaching] [Hiring] [Org design] [Delivery]

Engineering

[Architecture] [Reviews] [Reliability] [Performance]

Tech

[Languages] [Infra] [Data] [Cloud]

Writing / Talks / OSS

Optional—add what you’re proud of.

[Writing Placeholder]

[Publication • Year]

[Add a link when you have one.]

[Talk Placeholder]

[Conference • Year]

[Add a recording or slides.]

[Open Source Placeholder]

[Repo]

[Add what you maintain or meaningful contributions.]

Contact

Fast actions. No friction.

Email andrew.watkinz@gmail.com
LinkedIn GitHub Calendar (placeholder)

If you’re building something ambitious and want a leader who cares about the humans and the work, I’m easy to reach.