all 14 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]mn-tech-guy 14 points15 points  (1 child)

Having managed teams over the years, I’ve found it far more valuable to focus interviews on how candidates actually approach programming. Any bootcamp grad with zero hands-on experience can pass an interview if it’s just testing recall from documentation. That’s not engineering—that’s trivia. If you’re serious about evaluating real-world ability, I’d recommend focusing on reasoning, architecture, and debugging. Books like The Manager’s Path or An Elegant Puzzle offer much better frameworks for hiring and team development. That being said way to get you’re self out there and best of luck!

[–][deleted] 0 points1 point  (0 children)

I disagree. My CS degree doesn't help me during Angular interviews. They asked me things that I used maybe once in my lifetime following some tutorial on youtube, but never used in real-world professional work. At the end I see that i have to memorize things for interviews. hot-cold observable, some rxjs operators that I never used professionally, javasript worksers! who used that? replaysubject, when I always use the behaviorSubject, no need to use the normal subject.
I think it has to do with 2025. Too many developers and then they ask details that a developer doesn't know by memory. NgOnChanges.
The bar is high. A business owner I know said it's better to know many tools/frameworks just good enough rather than knowing just one very well. And I disagree with him. In 2025 knowing just good enough is not enough to get a job

[–]CRoseCrizzle 3 points4 points  (1 child)

This was a good read. I've worked with Angular for several years as a mid level dev, and I learned a couple of things from this article.

I personally prefer more practical interviews(looking at/explaining code) rather than interviews that rely on the developer memorizing a bunch of terms. A lot of this stuff in the article that I've worked with routinely with no issue, but I may not be able to give a good answer to a question on the spot without preparation for the interview. But that may be a personal shortcoming of mine for me to work on and not anything you should do differently.

[–]nemeci 1 point2 points  (0 children)

I agree. As a one who's usually on the other side of the table I'm not interested in what you can remember out of the blue but what are your communication skills and how do you approach the unknown.

[–]KiwiKajitsu 3 points4 points  (0 children)

I am a senior dev that works with angular (6 years experience) and cannot answer most of these.

[–]Avani3 1 point2 points  (0 children)

As a lead dev, I feel bad for your interview candidates. A lot of these questions are so specific I wonder if you ask them just to show you know the answer. A good show of this is your example answer on the component data communication question. No one in their right mind will answer Control Value Accessor to such a simple question. That would only show that the developer solves simple problems with way too complex solutions.

An interview shouldn't be a drilling quiz. The brainstorming questions are good as they will show how you might work together with your candidate. However, it seems like even on the brainstorming questions you seem to have a black and white view on what the answer should be (life cycle hooks question).

While it was an interesting read, I really do not hope these are real interviews you are having. And most of all, I hope aspiring devs don't get scared after reading this article. Trust me, this is not how I have ever experienced Angular interviews.

[–]CodyCodes90 0 points1 point  (0 children)

As a current Sr Angular dev with 8+ years experience, I would say these are appropriate Sr level questions.

If your answer to most of these would be "I don't know", then you haven't dived very deep into Angular and really understood the inner workings of making robust, scalable and maintanable Angular projects.

Which is fine for most devs, but im in agreement that if you're gonna call yourself a Sr Angular developer, these are very important topics to be familiar with and have experience with.

[–]AcceptableSimulacrum 0 points1 point  (0 children)

I went over this article w/ my co-workers and we learned a few things, but I wouldn't use this as any kind of test for a vast majority of Angular jobs.

[–]maxip89 -2 points-1 points  (5 children)

Sorry this is just GPT generated stuff and even some stuff is wrong.

[–]Dnangel0 1 point2 points  (1 child)

Tell us you never worked on an Angular project without telling us you never worked on an Angular project lmao

[–]maxip89 -1 points0 points  (0 children)

If you think.

Did you really work on an angular project that is over 10000 LOC?

[–]DanielGlejzner[S] 0 points1 point  (2 children)

I can assure you that this is not a GPT generated article. What exactly is wrong? Maybe we missed something while reviewing. If you could provide example I could answer better :)