01 · The person behind the programs
Who I Am
About me
The longer version, in my own words.
Hello! 👋
I’m Lindsay Vora (she/her), a hands-on Technical & Design Program Manager with twenty years of experience working behind the scenes of AI, voice, audio, data collection, software, hardware, and product development.
Program management is the spine of what I do, but I’ve never been the PgM who only holds the schedule and assigns tasks. I like getting into the details: turning ambiguous ideas into requirements, defining what “good” means and making it measurable, building tools and workflows when something is missing, and creating the structure that helps teams do their best work.
Voice has been a through-line for much of my career. If you’ve talked to an assistant in the last decade, there’s a fair chance I worked on its voice. I’ve helped design and develop Siri’s international voices, the flagship en-US Google Assistant voice, Meta AI and Assistant voices, and Gemini voices and models. Along the way, I’ve worked across the entire development lifecycle: voice design, recording and production, training data collection, vendor and customer management, model development, evaluation, DSP and tuning, tooling, localization, and the global operations needed to ship and scale it all.
But voice is only part of the story. I’ve built and led programs spanning business operations, smart glasses, VR/MR/XR, home devices, UX sound and spatial audio, haptics, AI data collection, evaluation systems, technical prototyping, internal tools, and large-scale operations. I’ve managed multimillion-dollar budgets and global vendor networks, built teams and programs from 0 → 1, and developed portfolio systems supporting organizations of 100+ people. My work has shipped across Meta, Google DeepMind, Uber, and products ranging from Ray-Ban Meta Smart Glasses and Quest to Google Home, Gemini, and two Emmy Award-winning immersive experiences.
I came up as a sound engineer, and that hands-on instinct never really left. I still write specs, prototype tools, dig into data, and yes, open the session file. I like understanding how things actually work, being close enough to the details to spot what’s wrong, and broad enough to connect the people, technology, and operations needed to fix it.
When I’m not doing any of that, I’m usually spending time with my family, at a Valkyries or Giants game, seeing one of my favorite bands play live, or buried in a fantasy or sci-fi novel. I also run, hike, snowboard, and play drums, with varying levels of skill and dignity depending on the day.
How I work
Twenty years in, a few things have stuck.
01
I’m comfortable not knowing.
At least at first. I like problems I haven’t seen before, and I try not to assume I already know the answer. I ask questions, poke around, experiment, and pull ideas from places that don’t always look like traditional program management. Sometimes that means building a tool, prototyping something myself, or finding a completely different way through. Not knowing the answer yet leaves a lot more room to find a better one.
02
I stay close to the work.
I’m hands-on by nature. I like understanding how things actually work, not just managing the process around them. I’ll sit in the recording session, test the build myself, dig into the data, or prototype something when there’s a gap. It makes me a better collaborator and helps me catch problems early. I’ll zoom in when there’s a problem to solve, then zoom back out to make sure we’re still solving the right problem.
03
If something’s missing, I’ll probably build it.
A lot of my favorite projects started with “I wish we had a tool for this.” I’m not an engineer, but I’m good at figuring out what something needs to do and getting a working version into people’s hands. I’ve helped build evaluation and audio tooling, capacity systems, dashboards, and scrappy prototypes that made their way into PRDs. I’m a big believer in show, don’t tell. Sometimes the fastest way to get everyone on the same page is to make the idea real.
04
I like making messy things make sense.
I like taking something complicated and figuring out how the pieces fit together: requirements, priorities, ownership, and a path forward, without adding process just for the sake of process. The goal is enough structure to help people move faster, make better decisions, and know what good looks like.
05
I put being a good human first.
The work matters, but so do the people doing it. I try to lead by example, give credit loudly, say thank you often, and admit when I’m wrong or just don’t know. I want people to feel like they can ask questions, disagree, make mistakes, and be themselves. You can hold a high bar while still being kind. I strive to be a person people actually want to work with.
Tools & Technology
Program Management
Jira
Confluence
Proprietary task management systems
Asana
Airtable
Trello
Proprietary DAM/CMS platforms
Apps Script
Quickbase
Linear
Tableau
SQL
Development
Figma
ADB
CLI
GitHub
Git
Mercurial
Unity
Unreal
FMOD
Wwise
VS Code
Python
AI
Gemini
Claude
Claude Code
ChatGPT
Lovable
Codex
Figma Make
Cursor
Audio
Pro Tools
iZotope RX
Adobe Audition
Proprietary DSP tools
Audacity
Reaper
SoX
FFmpeg
Logic Pro
WaveSurfer
MATLAB
Collaboration
Google Workspace
Slack
Zoom
Microsoft 365
FigJam
Mural
Daily driverin my hands constantly
Fluentcomfortable and current
Familiarused it, would ramp fast