Behavioural

Five stories in Situation → Task → Action → Result → what I'd do differently. Tooling roles reward stories about APIs other developers depended on, breaking changes, and debugging with measurements.

Questions to ask them

Pick five. Checked ones are your shortlist for the end of the interview.

Which Nuxt version are the apps on today, and what is the plan for Nuxt 5?Version skew between apps decides how a shared layer must be tested and versioned.
What modules and layers exist today, who owns them, and how are they versioned and released?Tells you whether you are building from scratch or inheriting a toolkit with consumers.
How do consumers report bugs today, and is there a reproduction or fixture culture?Reproduction-first intake is what makes shared tooling maintainable.
What does CI look like for shared packages — version matrix, E2E fixtures, type checks?Reveals how much safety net you will have to build before changing anything.
How many apps consume the shared code, and how is adoption of new versions tracked?You cannot deprecate anything you cannot see the usage of.
Monorepo or separate repositories? Is there an internal npm registry?Decides whether layers ship via workspace links, a registry or git tags.
What is the biggest pain the frontend team has with the current shared code?Points at the first thing worth fixing and shows you optimise for consumers.
How is success measured for this role in the first six months?Aligns your roadmap with what the team will actually reward.
How many apps would extend the layers, and how far apart are their Nuxt versions?Sets the peerDependency range and the CI matrix for every layer.
Would layers be consumed from a private registry, a monorepo workspace, or git?Each channel has a different dev loop, auth story and cache behaviour.
Who decides what goes into the base layer versus staying in an app?Without an owner and an RFC path, base layers rot into one app's wish list.
How are breaking changes in shared UI rolled out across apps today?Tells you whether deprecation windows and codemods exist or must be introduced.
Do apps override shared components today, and how — copies, props, wrappers?Copies mean the override story is missing; the layer needs recipes and a small surface.
Is there a consuming-app fixture in CI for shared packages, or only the package's own tests?The 'works in the playground' class of bugs is only caught by an external consumer build.