Pre-Mock Preparation & instructions

1. You must be in the same zoom room as your peer.
2. How to score the candidate (interviewee):
   1. For the non-technical conversation you’ll have the questions and guidelines on what should the candidate more or less talk about (it’s an open question so you expect from the candidate to be professional, focus on the question and not another unrelated topic).
   2. For the technical conversation part you’ll have for each question its correct answer and the candidate will either give the whole correct answer to get the whole point otherwise you give them 0.
   3. for the other coding exercises, the interviewee must have a working program with the correct output / answer to get the whole score on the task, otherwise 0.
3. Set a timer before starting each section.
4. If the candidate doesn’t answer all the questions for each section and the time is over, you should move to the next one ! ⇒ Set a timer on your phone or your computer before starting each section !
5. VERY IMPORTANT :
   1. Before starting the Mock Interview
      1. You as the interviewer must be logged in to use the google sheet to score the candidate.
      2. The candidate must give you their information that you’ll need to fill the google sheet such as :
         1. Intranet ID number
         2. Campus
         3. Name
         4. …
   2. How to score ?
      1. Give the full score (Scale / Max score column in the sheet) is the answer is complete.
      2. Give half the score if the answer is partially correct. (around 50% of the max score of the question).
      3. Give 0 if the answer is wrong.

Part 1: Non Technical Conversation (5 minutes)

1. What motivates you about web development?

   1. answer example :
      1. Passion for building user-centric experiences, continuous learning, tangible impact.

2. What are your long-term career goals ? Explain how do you think you’ll achieve your goals.

   1. Becoming a full-stack engineer, frontend, backend, blockchain, game developer…
   2. A startup founder
   3. An investor
   4. A team lead or an engineering manager
   5. A freelancer….
   6. They must explain (not into much details) how do they think they’ll get to their goal(s).

3. Tell me about a group project that you’ve worked on lately and what did you learn from it (technical and soft skills).

   1. They can mention one of the C projects that they’ve worked on, printf, simple shell, binary trees or any other personal project, etc.. the question is open so they just need to remain professional and focus on the topic of the question and not talk about something else.

4. How do you handle conflicts in team projects (e.g., coding style disagreements)?

   1. answer example :
      1. Communication, empathy, consensus via code review standards, focusing on objectives.

5. What’s your biggest weakness, and how do you mitigate it?

   1. answer example :
      1. Shows self-awareness + growth mindset (“I tend to over-research; I now set time limits”).

Part 2: Technical Conversation (25 minutes)

1. What is a unit test?

   • Answer: A unit test is a small, isolated test that verifies the behavior of a single function or component in your codebase.

2. Why are unit tests important?

   • Answer: They ensure that individual units of code work as expected, catching bugs early and making refactoring safer.

3. What is an integration test?

   • Answer: An integration test checks how different modules or components of a system work together.

4. Difference between unit and integration tests?

   • Answer: Unit tests test individual components in isolation, while integration tests verify interactions between components.

5. When should you use unit tests?

   • Answer: When testing logic-heavy functions that can run independently from other parts of the application.