Template is the real consumer
Use the async pipe
Best fitSubscribe manually in the component
ReasonableTRADEOFF BATTLE
user$, plan$, and notificationsCount$ as Observables. The page mostly needs to render those values in the template and update automatically when the service emits new data. A teammate wants to subscribe manually in ngOnInit, copy the values into component fields, and unsubscribe later. Another teammate wants to keep the streams in the template and render them with the async pipe. In the interview, the panel asks which direction you would defend.
You are not looking for the universal winner. You are picking the strongest answer for this prompt.
Pick the option you would defend, then reveal the stronger interview framing for this prompt.
STRONG ANSWER
user$, plan$, and notificationsCount$.Watch how the answer changes as the scenario changes. This is where tradeoff thinking starts to feel real.
Use the async pipe
Best fitSubscribe manually in the component
ReasonableUse the async pipe
Best fitSubscribe manually in the component
StretchUse the async pipe
ReasonableSubscribe manually in the component
Best fitOnce the answer is revealed, compare all options. The selected card stays highlighted so you can pressure-test your own instinct.
Alternative
Alternative
A strong answer survives follow-up pressure. These are the questions most likely to expose shallow reasoning.
Pushback
Pushback
Pushback
This is often the fastest way to internalize the difference between opinions and interview-grade reasoning.
Weak answer
I would use the async pipe because that is the Angular way.
What it is missing
Decent answer
I would probably use the async pipe because it keeps the template reactive and avoids some subscription code.
What it is missing
Strong answer
For this prompt I would use the async pipe because the page mainly needs to render Observable values from the service and update when they change. The template is the real consumer, so I do not want to subscribe manually just to copy those values into component fields. I would only move to manual subscribe if each emission needed imperative work in the component, such as patching a form, triggering navigation, or coordinating with APIs the template cannot own.
Why it works
These are the dimensions that make your answer feel senior instead of generic.
Use this structure if you want your answer to sound calm and easy to follow.
Avoid these shortcuts if you want the answer to feel grounded in engineering tradeoffs.