Apple · Primly Community

Apple frontend engineer interview: what they actually test, my experience in 2026

frontend_fran · 5 replies

Interviewed for an Apple frontend/web engineer role earlier this year, ICT4 (senior-equivalent). Sharing details because the frontend-specific info out there is sparse.

First: Apple does have web/frontend teams. A lot of people assume it's all Swift/Obj-C but the App Store, Apple Music web, Apple TV+, developer.apple.com, and a bunch of internal tooling are all web. I was interviewing for the App Store web team.

The technical phone screen. One hour, one interviewer. They gave me a DOM manipulation problem in vanilla JS. No framework. They explicitly said they'd evaluate framework knowledge separately; the phone screen was about fundamentals. Things tested: event delegation, closure behavior, async/await vs callbacks, a debounce implementation. Classic frontend interview stuff but they enforced vanilla. Know your JS without React as a crutch.

Onsite rounds (4 technical + 1 behavioral). JS/fundamentals round: prototypal inheritance, how the event loop works, a small class-based problem. CSS/layout round: yes, a dedicated CSS round. They gave me a layout spec and asked me to build it. Flexbox, grid, some responsive behavior. They cared that I understood why, not just that I could Google the syntax. React/component design round: build a small interactive widget (I got a collapsible tree), then discuss state management, re-render behavior, performance. When they asked about performance I talked about memoization, useMemo, virtualization for large lists. They pushed back constructively, which I took as a good sign. System design (frontend): design the App Store home page at scale. Think about CDN, lazy loading, ab testing infrastructure, i18n. This one surprised me. It's a real frontend system design round, not just "draw boxes." Behavioral: standard Apple themes. Collaboration, pushing back on ambiguous requirements, ownership.

What I wish I'd prepped more on. Web performance metrics (Core Web Vitals, LCP, CLS). They came up in the system design round and I had surface-level answers. Go deeper if you're targeting this team.

Offer came in at ICT4, base around $185k SF-equivalent. Total comp with RSUs was around $280k first-year. Took it.

5 replies

infra_ines

A dedicated CSS round in 2026. Respect. Most companies have entirely abandoned testing CSS knowledge. Was it at all about browser compatibility or purely layout?

frontend_fran

Mostly layout. One brief question about what I'd do if a CSS property wasn't supported in older Safari versions (ironic, I know) but that was about 5 minutes of a 60 minute round. The rest was layout problems.

growth_gabe

The A/B testing infrastructure question in the system design round is interesting. Did they want you to design the infrastructure itself or more the client-side integration layer?

frontend_fran

Client-side integration layer, mostly. How you'd serve experiment variants, how you'd handle flicker, how you'd collect event data without impacting performance. They didn't want me to design an experimentation platform backend from scratch.

returner_ren

The comp figure is helpful, thank you. I'm returning after a gap and wasn't sure if ICT4 was still in that range. This matches what I'd hoped.