What is a Service Worker's role and key PWA capability?

WHAT THIS TESTS: The interviewer wants to know if you understand the architectural role of a Service Worker as a programmable network proxy and its relationship to Progressive Web Apps. This is foundational for modern web performance and reliability. They are checking whether you can distinguish it from other worker types and whether you grasp why HTTPS is required.

A GOOD ANSWER COVERS: A good answer hits four things in order. First, define the Service Worker as a JavaScript file that acts as a proxy between your web application, the browser, and the network. Second, explain that its primary power is intercepting network requests and deciding how to respond, which enables offline experiences through granular caching strategies. Third, mention that it unlocks specific PWA capabilities such as push notifications and background sync. Fourth, note the constraints: it runs in a worker context with no DOM access, is fully asynchronous and non-blocking, and only works in secure contexts like HTTPS or localhost.

COMMON WRONG ANSWERS: Red flags to avoid include confusing a Service Worker with a standard Web Worker or claiming it can manipulate the DOM directly. Another mistake is describing it only as a cache layer without mentioning the proxy interception model. Saying it enables offline mode magically without explaining request interception is also weak. Finally, forgetting that it requires a secure context shows a lack of production awareness.

LIKELY FOLLOW-UPS: Expect the interviewer to ask how you would implement a cache-first versus network-first strategy, how to handle Service Worker updates and activation, or how the lifecycle events like install and activate work. They might also ask about the Cache Storage API versus browser HTTP cache, or how to test Service Workers during local development given the HTTPS requirement.

ONE CONCRETE EXAMPLE: Imagine a news PWA where a user opens an article. The Service Worker intercepts the fetch request for the article HTML and assets. If the network is available, it fetches fresh content and updates the cache. If the user is on a subway with no connection, the Service Worker serves the cached article from the previous visit, allowing the user to keep reading. This same worker could also register for push notifications to alert the user when a breaking story publishes, and use background sync to retry a failed comment submission once connectivity returns.

Source: developer.mozilla.org