Senior Angular Developer Interview (theory)

[WeCoded]

For those wondering whether I got the job after taking that interview.
I did get the offer but the compensation level was much lower than what I was aiming for. So, I declined it.
p.s.
For some reason, that company decided to host 7 interviews in total, 4 of which were technical (similar to the one in the video). With a lot of repeated questions.
And it wasn't disclosing the pay range until the last step.

[shwetakumari-msxg]

thanks for this, I have an interview tomorrow. This was helpful.

[sergiustanciu]

Your interviews are pure gold! Thank you for sharing!

[Mecagothits]

thanks for the interview really good for my future

[phoolherreracondezo]

I liked this kinda type video thank a lot bro

[riva]

i need more interviews like this and if you can add technical interview, better

[elsasolen]

Great interview, learnt a lot, thanks!

[sfspmusic]

I didn't get the interviewers points, we can definitely use constructor for logic, but since we have a special method that makes sure that all the input properties will be initialized, there is no reason for doing it in the constructor quite often, still nobody forbids us us to do it in constructor

[igorring]

It's interesting. But sometimes I hear strange questions. For example 08:00. Object lifecycle! What does he mean? I mean, that is called foul play.

[alexgeolog]

Why interviewer asking about ng-deep? /deep/ combinator already deprecated and removed from the browsers and not using anymore.

[theanswer]

I hate these kind of interviews where you can see that the person asking questions found the hardest questions possible just to mess with you and assert dominance. Also to downgrade your skill and then offer you lower salary.

[andreiromulus]

I've been a full stack dev for 3 years. For the past year I've been only doing angular, adding up to a total of about 2 years of hands on experience with building UIs in Angular. I think the questions in this interview are good and relevant questions. With my level of experience I could also answer a few of them and I find your conversation with the interviewer very insightful.

Just a few days ago I had an interview for the role of a middle level angular developer (that required a minimum of 3 years experience). The only few questions I was asked were about angular compilation techniques, onPush change detection, multi-casting observable, and to compare promises vs observables.
Apart from the promise vs observable comparation, I wasn't able to answer any of them. The interview was supposed to last for one hour, but after 20 minutes the interviewer called it a day, saying they didn't have any more questions for me.

Is it expected from a mid angular dev to know this stuff? Were these kind of questions indeed a little too advanced or do I simply lack the experience?

[misterV]

Hey. A nice interview, thanks. Do you have a tech one after that?

[WelWel-py]

Anyone can't hear his questions ? 😅

[SumitKhanduri]

can someone explain the question he asked about constructor vs ngOnInit,

[jayTzanTG]

Has anybody the feeling that the interviewer is kinda aggressively shooting q`s and interrupts the interviewee like constantly ? :D

[bdabroad]

Dudes accent is way too thick. I would’ve been asking “what?” The whole time. Also asking useless questions just for the heck of it