How to answer: “How do you stay up to date with new technologies?”

What they’re actually asking

The field turns over every few years and they're checking whether your skills expire. But the trap runs the other way too: chasing every new framework signals you'll rewrite their stack for fun. They want curiosity with a filter.

How to structure your answer

Name your actual sources — specific newsletters, specific engineers you read, release notes for tools you use daily — then describe your filter: you try things in side projects, not production. One recent example of something you learned and used beats a subscription list.

Example answer

“I read a couple of engineering newsletters and the changelogs of everything in our stack, but the real learning is building: I keep one side project as a sandbox. That's where I tried server components before we adopted them at work — by the time we migrated, I'd already hit the footguns on my own time. My rule is new tech earns its way into production by surviving a side project first.”

What sinks people

• A list of subscriptions with no evidence any of it changed how you work
• "I try to use the latest tech everywhere" — that's a threat, not an answer
• Pretending to know a technology the interviewer might then ask about