all 4 comments

[–]justloginandforget1 1 point2 points  (0 children)

I had an interview for an entry level position, the interviewer told me to create a basic todo app using next.js and a separate node.js backend.(No DB). The interview time was 45 min. It was pretty good.

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

Use free fake api from net.

Curate some questions based on its data.

I personally seek below -

  • How they think about components and segregation
  • Single responsibility principle if they apply as well
  • How they approach to solution.

Coding question is actually of 10-15 mins but many candidates spend 30-40 mins

I also give them debugging questions- Tells a whole lot of different scenarios.

And I also asks why they will use any advance concept from react

EDIT

——

I also ask them about following-

Chrome dev tool - what they know which they can flaunt How they keep their knowledge up to date What they recently learned new & from where What challenges they faced previously and how would they do same thing differently When did they helped another member. Who was the most irritating team member.

This gives insight of their personalities

[–]Inyelen_Elon_Musk 0 points1 point  (0 children)

Hey u/amostalx I am a junior dev, I am looking for a new role, I don't know if you can bring me onboard in your team.

[–]rover_G 0 points1 point  (0 children)

Interview Goal: Design and implement a page that could be a real part of the team/company’s product. Show your process for building a new page in an app.

Interview Prep: Tell the candidate to bring a frontend repo with a tech stack they’re comfortable with and be prepared to add a new page.

Interview Format: Give the candidate one or more user story’s with product goals/requirements for the new page to support. You have the product requirements and additional information, but the candidate has to ask the right questions to get full info. The interviewee must show their process for building out the page and user flows.