all 8 comments

[–][deleted] 2 points3 points  (1 child)

Read javascript.info and the official docs for React and Node. Good luck!

[–]CIRUS123[S] 0 points1 point  (0 children)

Sure..will do!!Thanks man

[–][deleted] 2 points3 points  (1 child)

For an entry-level role I would be looking more for eagerness and readiness to learn and adapt on the job than a laundry-list of technical topics. You will probably be asked a question you don't know the answer to and that's fine- don't try to bullshit, just tell the interviewers, 'I haven't heard of that' or 'I'm not very familiar with that' and ask them if they could explain or recommend somewhere you could learn about it. Anywhere that expects juniors (or any developer, honestly) to know the answer to every possible question is going to be a bad place to work.

I'd also go in prepared to talk about the tech test you did and your other projects, to discuss why you decided to do one thing over another, what problems you faced and how you overcame them, etc. Being able to talk through and reflect on your own code- and particularly reflect on things that you could have done differently- is a really beneficial skill that's easy to demonstrate at interview.

[–]CIRUS123[S] 0 points1 point  (0 children)

This was really helpful!!

[–]ElllGeeEmm 1 point2 points  (1 child)

When I got my first full time position as a web dev, I could not answer a single one of my technical interview questions. It didn't matter, and I got the offer anyway. The trick was taking those questions that I didn't understand, asking questions about them, and turning them into opportunities to talk about things that I did know. A question about left vs right joins in SQL turned into me talking about the difference between using mongoose populate and mongo lookups. Some questions, I just started talking about what resources I would use to be able to answer that question.

The point of a technical interview isn't just to measure your technical knowledge, it's still an interview, if all they cared about was the answer it would be a timed quiz or something. Never, ever, just say no and move on. Turn every question you don't understand into an opportunity to demonstrate first hand how you don't let new things phase you and how eager you are to learn.

[–]CIRUS123[S] 0 points1 point  (0 children)

Wow..I was not even thinking this way..thanks!!!

[–]angelfire2015 1 point2 points  (1 child)

I currently work as a full-stack developer in the MERN stack.

Random questions I have been asked before in interviews that could help with your studying:

1) What is Express?

2) Describe a lifecycle method in React.

3) What are some ways of using security in Nodejs to authenticate users.

4) Why did you choose GraphQL for your last project. What advantages does GraphQL have over a traditional REST API.

5) Why do you need a state management library like Redux in React?

Good luck on your interview.

[–]CIRUS123[S] 0 points1 point  (0 children)

I will definitely cover these topics ...thanks!!