Ryan Lindsey
Senior Engineering Manager, Agentic Engineering
Agentic engineering is making engineers dramatically faster. I build the instruments that let the organization around them keep pace. Nineteen years in software, a decade of it leading engineering teams: I own incident management for an entire engineering organization, I build the agentic tooling that other managers choose to adopt, and I still ship the code. The habit underneath all of it is to measure a process before improving it, because the constraint is not always where it is assumed to be.
Prefer JSON? Markdown?
Based in
Experience
Weedmaps
Irvine, CA
Mar 2016 — Present
Senior Engineering Manager
Feb 2021 — Present
Own incident management for the entire engineering organization since 2024 and coach fellow engineering managers, while leading 8 engineers across 2 teams whose work spans the whole platform, the web applications and the native iOS and Android applications alike. Platform: AWS, Ruby on Rails, Node.js, GraphQL, React, Next.js, Swift, Kotlin, React Native, Terraform, Kubernetes, Docker, Fastly, Snowflake.
- Lead cross-functional teams of polyglot engineers shipping features across Android, iOS, and web, partnering with Product and Design from definition through release. The native applications run Swift and Kotlin, with React Native covering roughly half the production surface since 2025.
- Designed and built a delivery-forecasting toolchain for engineering managers, beginning as a set of Claude Skills and migrating to an internal MCP server as adoption outgrew that packaging. Adopted by >80% of engineering managers and absorbed into the org-wide roadmapping and reporting process.
- The incident process I own now runs on agentic investigation: incident commanders use agents and connected MCP servers over live telemetry, which has raised root-cause-analysis quality and sharply reduced the time to produce one.
- That ownership covers the process itself, the communication strategy, service integrations with third-party systems of record including Salesforce, data reporting, and training, and it has covered the native mobile applications from the start alongside the web and back-end services. Data Engineering and InfoSec run their own incident processes on the same tooling. Accountable for the area's OKRs and report on them to the executive team monthly. Risky changes go through a change advisory board with documented rollback plans, and post-incident review is blameless with linked action items.
- Measured the inherited process before changing it, and found response and resolution times were already at or better than industry standard, a reading corroborated independently by a vendor in the space. The real weakness was time to detect, so that became the focus: a service-level observability initiative run with DevOps and SRE now surfaces issues before customers report them, across both web and native applications.
- Publish agentic tooling as Claude Skills in a shared repository open to every engineering manager, running on scheduled cloud routines, including a daily digest covering incident-response concerns.
- Day-to-day software and product development runs through Snowflake's MCP servers, so querying the system of record is part of the agentic toolchain rather than a separate reporting step.
- Took on an advertising technology platform to raise its engineering rigor: documented its critical paths, built a test coverage strategy integrated with CI and improved it over time, moved it to blue/green deployments for zero downtime with DevOps, and added bot mitigation and payload verification with InfoSec to protect metric integrity against junk traffic.
- Built an off-marketplace e-commerce platform from nothing with a team, to meet marketplace regulatory requirements across the United States and Canada. Still in production and contributing to platform GMV.
Case study: Replacing guessed delivery dates with calibrated forecasts
Engineering Manager
Sep 2017 — Feb 2021
- Managed up to 19 engineers, from junior through staff level, across several cross-functional product delivery teams on a consumer platform used by millions of people every month.
- From 2019 the teams reporting to me shipped across Android, iOS, and web rather than one surface at a time, with backend, front-end, iOS, and Android engineers on the same delivery teams. Coordinating one feature across three release surfaces, two of them gated by app review, is a different planning problem than shipping to the web alone.
- Decoupled deployment from feature release, so the product and go-to-market teams could control launch timing independently of engineering deploys. This removed a standing coupling between shipping software and announcing it.
- Introduced global edge caching across the primary web applications on both client and server, through a Fastly CDN integration and an API caching strategy keyed on surrogate keys, so caches invalidate by content association rather than by URL.
- Tripled overall test coverage and reduced escape defects by making code quality standards something the teams practiced rather than something they were handed.
- Led image processing pipeline work spanning millions of unique assets, improving engineering efficiency, vendor costs, and application performance. Improved inter-service communication for business-critical APIs with a publish-subscribe message queue pattern.
- Sat several hundred interviews and grew the engineering team by dozens across multiple growth cycles. Promoted a dozen or more, a few onto the management track and the majority further along the technical one.
- As one of the company's first engineering managers, helped shape its performance management program, iterated on it with HR for nearly a decade, and coached other managers on running it, one-to-ones, and situational management.
- Founded and ran a public monthly engineering meetup that passed 250 members inside a year, and built a repeatable onboarding process for new engineers.
Manager, Front End Engineering
May 2016 — Sep 2017
- The company's first engineering manager below the executive level. Before this team existed, every engineer reported to the same VP or CTO.
- Chartered to develop front-end developers into front-end engineers, which is where the department's technical rigor and its cultural shift started.
- Began the front-end re-architecture. Shipping a single roadmap feature meant changing three separate code bases to reach every user and device, a legacy of the pre-responsive mobile subdomain era. The work cut time to market and became the foundation for the company's later front-end architecture on React and Next.js, including a shared UI library built with the Design team.
- Defined and delivered the front-end staffing roadmap, and rebuilt the front-end technical exercise with the talent team.
Sr. Front End Engineer
Mar 2016 — May 2016
- Built and maintained features across the company's web applications, mentored other engineers, reviewed code, and provided technical input to Product. Moved into engineering management within three months.
RED Digital Cinema
Irvine, CA
Oct 2011 — Feb 2016
Sr. Front End Developer
- Architected UI features for the company's e-commerce, marketing, and customer support websites, and drove adoption of a new UI component library and design language with the design and marketing departments.
Innocean Worldwide
Huntington Beach, CA
Feb 2011 — Oct 2011
Sr. Front End Developer
- Led interactive development for Hyundai USA, including hyundaiusa.com, microsites, Facebook games, and a custom YouTube channel, working with the creative team from concept onward.
Y&R Brands / Wunderman
Irvine, CA
Jun 2007 — Feb 2011
Front End Developer
- Delivered interactive work for Land Rover, Southwest Airlines, Toshiba, and Hilton, recognized with Lester Wunderman awards (2008, 2009) and a 38th Annual Creativity Award (2008).
Freelance
Orange County, CA
Jan 2001 — Jun 2007
Web design & development
- Ran every part of the business: client relationships, project management, design, and development. Built marketing sites, online communities, and custom content management systems for local businesses, independent films, and bands.
Projects
A sim racing coaching platform that turns telemetry into driver development goals, with a personal AI race engineer for every driver, plus a products line for sim racers.
- Built and run solo on Cloudflare Workers, D1, R2, Durable Objects, Queues and Workflows, with Claude routed through AI Gateway.
- Per-driver isolation by object addressing, property-based eval harnesses that report their own unmet gates, and cost tracked per unit of work against per-driver budgets.
Case study: A green run is not proof: building an agent platform around silent failure
A pour-over coffee companion for iPhone, iPad, and Apple Watch, written in Swift and SwiftUI and shipped on the App Store. On-device Apple Foundation models write tasting notes and brew guides, with no account and no third-party data sharing. Guided brews run as a Live Activity in the Dynamic Island, state syncs over iCloud, and the collection is reachable through Siri, Shortcuts, and Spotlight.
A Claude Code plugin that gives an agent a GitHub Projects board: it claims the next item, works it on a branch, and opens a pull request it cannot merge.
- Open source under MIT since September 2026 and used every day to deliver production features for Pixelsonly Racing. The public iteration of private Claude Skills in use since June.
- Claims work on the board before writing code and never merges, with no flag or option to allow it. Runs daily against production work and builds itself.
ryanlindsey.me
Aug 2026 — Present
An agent-native personal site and MCP server on Cloudflare, built largely by agents working a plan, with grounded chat and a published AI policy and risk register.
- Retrieval through Vectorize, rate limits in a Durable Object, a tool-call audit trail, fenced untrusted content against prompt injection, and evals scored by a model judge.
Home lab
Author
2020 — Present
A self-designed home network and service platform: a segmented LAN reached over WireGuard, Traefik routing with Cloudflare certificate resolution, several Docker hosts, and a NUT server running the UPS power sequencing I wrote, which brings services down and back up in order, with Uptime Kuma as the dashboard.
Education
The Art Institute of California
2003 — 2007
B.S., Interactive Media (HCI)
Golden West College
2001 — 2003
A.A., Business Administration
Skills
Agentic engineering
MCP servers (Model Context Protocol), Claude Code and Claude Skills, Agent design and tool use, Spec-driven agentic development, LLM evals (property-based, LLM-as-judge), Retrieval-augmented generation (RAG), Human-in-the-loop controls, AI governance (acceptable use, risk register, audit trail), Prompt-injection defenses, LLM cost controls and gateways, Agent access to systems of record (MCP over Snowflake)
Engineering leadership
Incident management, Change management (CAB, rollback plans), Observability, OKRs and executive reporting, Hiring and team growth, Coaching engineering managers, Engineering enablement, Cross-functional partnership, Performance management, Native mobile teams (iOS, Android), Multi-platform release coordination
Native mobile
Swift and SwiftUI, iOS, iPadOS, and watchOS, React Native, App Store delivery and review, App Intents, Siri, and Shortcuts, Live Activities and Dynamic Island, On-device Foundation models (Apple Intelligence), iCloud sync
Platform and delivery
Edge compute and caching (Fastly, Cloudflare Workers), Serverless (Durable Objects, Workflows, Queues), Kubernetes and Docker, AWS and Terraform, CI/CD and automated testing, Blue/green, zero-downtime deployment, Release management, Bot mitigation, API design, High availability, Data warehouse (Snowflake), VPN and network segmentation (WireGuard), Reverse proxy and TLS automation (Traefik), Self-hosted monitoring (Uptime Kuma)
Languages and frameworks
TypeScript, JavaScript, Node.js, React and Next.js, React Native, Ruby on Rails, Swift and SwiftUI, Kotlin, SQL (SQLite, D1), GraphQL, *nix shell