Mechanic and early builder
Learned how real systems fail, how people use tools, and how work actually gets done.
Timeline
The career map behind the work.
The roles changed. The pattern stayed steady: learn how systems fail, understand how work moves, and build the structure that lets people execute better.
Chemistry degree, tutoring, leadership, resident life, outdoor club
Built a foundation in science, teaching, leadership, and group coordination.
Chemistry PhD, research, teaching, head tutor
The first workflow automation project was not AI. It was a tutoring-center sign-in system built in Excel because a clipboard made no sense.
Tesla, battery materials and GigaLab
Structured supplier evaluation, requirements gathering, test planning, and laboratory buildout during hypergrowth.
Faraday Future, requirements and workflow architecture
Built requirements systems, workflow automations, data-flow maps, and configuration-management processes across disconnected enterprise systems.
Rivian, production scale and governance
Helped create product governance, traceability, and operating mechanisms during the transition from prototype to volume production.
Ampaire, hybrid-electric aircraft programs
Owned complex subsystem programs involving budgets, suppliers, FAA certification, requirements, timelines, and executive alignment.
Kyma, CEO and startup operating model
Built the business operating system: team, headquarters, roadmap, partners, supply, revenue, IP, and execution model.
Lucid, engineering knowledge and workflow tools
Built a structured engineering knowledge system combining a curated knowledge base, internal web app, and retrieval support.
Ask Anyway / VOREN / private technology systems work
Applies the same systems thinking toward human connection, human-centered technology, standards, storytelling, and workflow tools.