CS Questions in Frontend Interviews Are Too Hard

I've had a similar experience. I only prepared with React and got stuck on the browser rendering process. Now I'm building my foundation with books like 'CS for Frontend Developers.' Focusing only on topics that frequently come up in interviews has been more time-efficient.

I had the same concern, but these days when preparing for interviews, I approach it with the mindset that 'CS knowledge is problem-solving ability.' For example, understanding browser rendering helps you grasp why key props are important in React. Connecting it to actual development experience rather than just memorizing makes it stick much better.

I'm always most scared of CS questions during interviews. But since I don't use those concepts every day on the job, I think it's better to just memorize them for interviews. I used to refer to GitHub repos like 'Frontend Interview Questions' and memorized answer patterns, and it actually worked.

CS questions are really about testing your foundational knowledge, even for frontend roles. Browser rendering ties into performance optimization, and RESTful APIs are crucial in real collaboration. I studied by grasping concepts through MDN docs and YouTube lectures, then organized them on my blog. You don't need to dive too deep—just understanding the core ideas is enough to answer well in interviews.

Which company's interview was it? The difficulty of CS questions seems to vary depending on whether it's a large corporation or a startup. I remember being flustered when I got a question like 'Explain the event loop' during a mid-sized company interview. Now I'd recommend making sure to review at least one CS fundamentals book before going into an interview.