Solve fundamentally new UX problems

Developing self-driving cars is one of today’s most technically complex challenges. We make this process faster, safer, and easier by designing the world’s best software for testing self-driving cars.

Who uses Applied’s products?

Here are some examples of how autonomous vehicle engineers use Applied's software.

Customer
Kodiak (Silicon Valley)

Use case
“If the safety driver hadn’t taken control, would our truck have been able to avoid an accident?”
Customer
General Motors (Detroit)

Use case
“Are the road lanes and stop signs in our maps located correctly and up to date with the real world?”
Customer
Toyota (Japan)

Use case
“How does rain interfere with our car’s ability to accurately identify other vehicles around it?”

What's unique about design at Applied?

Design at Applied
vs.
Consumer apps
Enterprise tools
Autonomy
Large companies
Startups
Design for a safer future
vs.
Design for engagement
Solve fundamentally new problems that existing UX paradigms don’t fit
vs.
Reference existing UX paradigms for just about every feature (tags, comments, feeds, etc.)
Get to know and solve specific problems for a niche (and highly appreciative) audience
vs.
Rely on “user personas” or faceless usage data to guide design directions
Solve interesting problems that impact your life as a driver, passenger, and pedestrian
vs.
Build deep domain knowledge that has minimal overlap with your day-to-day life
Create solutions across 2D and 3D spaces
vs.
Design different kinds of tables over and over and over and over and...
Design for users working on the cutting edge of technology 
vs.
Fight legacy systems and processes that hinder good user experience
Accelerate autonomy as a whole by working with major players across the industry
vs.
Your overall impact is limited to the success of a single AV stack
Ship features that are immediately used to improve AV testing and development
vs.
Users won’t experience the benefit of your design work until large scale deployments happen
Get direct, actionable feedback from real users on a daily/weekly basis
vs.
Design is mostly constrained to research and hypotheses
You’ll own entire products from concept through implementation
vs.
Your ownership is often limited to individual features
We’re lean with clear goals: design work gets shipped quickly
vs.
Design cycles are wasted exploring different concepts every time leadership waffles
Help close large deals by actively addressing customer pain points during trial periods
vs.
The correlation between your design contributions and business impact is fuzzy 
Each of our products tackle a completely different use case within autonomy development 
vs.
Focused on solving one problem
We work on mature, revenue-generating products while also exploring new products
vs.
Searching for product-market fit
Design plays a key role – our customers regularly mention the UX of our products as a key differentiator
vs.
Design is often treated as an afterthought to engineering or sales

Who’s on the design team at Applied?

Justin

Design Lead
Google, Savannah College of Art and Design

Elizabeth

Product Designer
UC Berkeley

Ayman

Product Designer
Aptiv, Motional

Michelle

Brand Designer
Facebook, California College of the Arts

Justin

Design Lead
Google, Savannah College of Art and Design

Elizabeth

Product Designer
UC Berkeley

Ayman

Product Designer
Aptiv, Motional

Michelle

Brand Designer
Facebook, California College of the Arts