open questions for Applied Intuition
on the strategic position
- How does Applied think about the tension between the toolchain/Vehicle OS business and SDS? In verticals where Applied's tooling customers are also building their own autonomy stacks (passenger cars especially), is SDS positioned as complementary, competitive, or intentionally constrained in those verticals? This is the cleanest way to find out whether Applied is actually trying to be a winner-take-all autonomy company or whether the company has made a strategic decision to stay in the supplier lane to protect tooling relationships. A company that intends to win autonomy fully will staff and structure itself very differently from one running SDS as a protected, limited bet. The answer tells me which version is real, and therefore what kind of company I just joined.
- Where does Applied see the next five years of revenue growth concentrated: continued expansion of toolchain/Vehicle OS, SDS deployments, or defense and specialized verticals? Which is the company betting on as the primary growth engine? Resources and attention follow revenue strategy. If the primary growth engine is toolchain, then Onboard Architecture supports a business unit that is secondary to the company's revenue. If it is SDS, my team's work is central to the company's next chapter. If it is defense, the cultural center of gravity shifts. I would rather work at the center than the periphery, so understanding where the growth is tells me whether I need to advocate for repositioning or I am already well-placed.
- In passenger cars specifically, how does Applied approach customers that have their own internal autonomy teams? Is the toolchain the primary offering there, or does SDS get positioned for segments the OEM's own team won't cover (e.g., specific ODDs, safety fallback, validation)? Passenger cars are the largest market and the most contested. The way Applied positions SDS there tells me whether the company believes it can win passenger-car autonomy on merit, or whether it has accepted that passenger cars go to whoever the OEM picks and SDS competes for specific narrow use cases. Those are different strategic realities. If Applied has accepted the narrow position, passenger-car work is constrained, and the interesting autonomy-stack growth is elsewhere (trucking, mining, defense).
on the architectural bets
- How does the research org under Wei Zhan coordinate with the Fallback Stack org? Are they genuinely running parallel bets, or is the Fallback Stack a temporary safety net that's meant to shrink as the learned stack matures? The "running parallel bets" framing is central to why Applied's architecture looks intellectually honest from the outside. But if the Fallback Stack is actually just a transitional scaffolding meant to disappear once learned systems mature, Applied is effectively making the same bet as Wayve and Tesla, just more slowly. That would change my read of the company's architectural philosophy significantly. The answer tells me whether the duality is a real long-term commitment or a temporary hedge.
- Where does Applied see the balance settling between end-to-end learned and modular-differentiable architectures? Is the differentiable stack a permanent architectural stance or a transitional one on the way to more end-to-end? This determines what the integration work actually becomes. A company committed to modular-differentiable has integration layers that stay as real engineering artifacts for a decade. A company transitioning to end-to-end progressively dissolves those integration layers. The first world makes a career as an integration engineer durable. The second world means I need to move into something else within three years or become obsolete. I need to know which world I'm in.
- Given the research-heavy competitors (Wayve, Tesla, Physical Intelligence) running foundation-model-first bets, how does Applied plan to stay competitive on the research frontier without becoming a pure research company? Applied has real research under Wei Zhan, but research is not the primary business. Companies that under-invest in research get left behind when the paradigm shifts. Companies that over-invest become expensive research labs without a product. I want to know where Applied draws the line, because it tells me whether the research I get to work adjacent to is serious or symbolic, and whether Applied is positioned to survive a foundation-model moment from a competitor.
on engineering and my role
- What does "Onboard Architecture" mean in the mature state: is the team's long-term role to adapt each customer's stack to their specific platform, or to define a canonical onboard architecture that gets deployed across customers with customizations? These two versions of the role produce different engineers. Customer adaptation makes the role a high-leverage integration specialist with deep cross-platform experience but no ownership of a canonical product. Canonical architecture makes it a platform architect whose decisions ripple across every deployment. I want the second eventually. Knowing which version the team is evolving toward tells me whether my trajectory here matches my goal.