Web & Mobile interviews. 13 titles, each with its own model.
Each page shows the competency model, the questions that test it, what changes with seniority, and where candidates lose the interview.
Last reviewed
Every Web & Mobile title
13 titlesWhat the report looks like for Web & Mobile
- The situation in one sentence: where, what was short, and by how much.
- The decision that was yours rather than the team’s, and what you chose not to do.
- One number or one consequence that shows it worked.
Every competency is scored out of five with a line you actually said as evidence, and the weakest answers are rewritten as structure and specifics, never a script.
What Web & Mobile interviewers keep scoring
Problem decomposition & design
Breaks an ambiguous requirement into components, chooses appropriate data structures and boundaries, and can explain the trade-offs of the design they picked.
Code quality & testing discipline
Writes code that others can read and change safely, and uses tests deliberately to protect behaviour rather than to hit a coverage number.
Debugging & production incidents
Finds the root cause of unexpected behaviour methodically using logs, metrics and reproduction, and closes the loop so the same failure does not recur.
Systems & data fundamentals
Understands how their code behaves on a real machine and network: concurrency, memory, I/O, databases, caching and the failure modes of distributed calls.
Delivery & scope management
Ships working software on a predictable cadence by slicing work, surfacing risks early, and negotiating scope rather than silently missing dates.
Code review & technical collaboration
Gives and receives code review that improves the codebase, and works through technical disagreements with evidence rather than seniority or volume.
Ownership beyond the ticket
Takes responsibility for the system and its users rather than only assigned tasks: notices problems, fixes what is broken, and follows work through to production and beyond.
UI architecture & state management
Structures components, data flow and state so that features can be added without regressions, and can justify where state lives and why.
Web performance & loading
Makes pages fast on real devices and networks by measuring Core Web Vitals, controlling bundle size and rendering work, and knowing which fix matters most.
Accessibility & semantic HTML
Builds interfaces that work with keyboards, screen readers and assistive settings by using correct semantics and ARIA only where needed, and tests them.
Browser, network & JavaScript fundamentals
Understands the event loop, rendering pipeline, HTTP caching, CORS, cookies and security headers well enough to diagnose behaviour that the framework hides.
Frontend testing & release safety
Prevents regressions with the right mix of unit, component, visual and end-to-end tests, and ships behind flags or staged rollouts so problems are caught before all users see them.