Technical Staff Lead

AIC, El Segundo, CA

What you will do

Embed on-site with design partners and manufacturers for meaningful stretches of the year — their floor is your second office.
Build trust across the full vertical, from the GM to the technician running the station. Software and hardware deployed without this trust doesn't get adopted.
Develop genuine understanding of how each partner's shop works and why — the history, constraints, people, and physics of what moves through it.
Translate unstructured observation into concrete requirements, then build, ship, and maintain the software yourself and through the other technical staff you coordinate on-site and at HQ.
Write production code across the full stack — data model, ETL, backend, frontend, algorithms, hardware integrations, ML pipelines, analyses, and infrastructure. Everyone wears all the hats at various points in time.
Run the process-engineering side of deployment — sequencing software changes with operational changes so the two evolve in lockstep, including the cultural work: training, change management, work instructions, quiet one-on-ones with skeptics.

AIC, El Segundo, CA

Embed on-site with design partners and manufacturers for meaningful stretches of the year — their floor is your second office.
Build trust across the full vertical, from the GM to the technician running the station. Software and hardware deployed without this trust doesn't get adopted.
Develop genuine understanding of how each partner's shop works and why — the history, constraints, people, and physics of what moves through it.
Translate unstructured observation into concrete requirements, then build, ship, and maintain the software yourself and through the other technical staff you coordinate on-site and at HQ.
Write production code across the full stack — data model, ETL, backend, frontend, algorithms, hardware integrations, ML pipelines, analyses, and infrastructure. Everyone wears all the hats at various points in time.
Run the process-engineering side of deployment — sequencing software changes with operational changes so the two evolve in lockstep, including the cultural work: training, change management, work instructions, quiet one-on-ones with skeptics.