Update technical interview information

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Helps clarify expectations around technical interviews for interviewers and provide instruction

CHANGEME

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file technical.md

---

The document you provided contains changes to the technical interview process at GitLab. The key updates include:

• Candidates will receive a merge request link 48 hours before their interview instead of 24 hours.
• Candidates are encouraged to complete their review of the merge request at least 24 hours before the interview to give the interviewer time to evaluate their progress.
• Candidates are advised to review the code review guidelines and contact their recruiter or CES team member with any questions before the interview.
• GitLab no longer requests candidates to work on live or "real" issues as part of the technical interview. Instead, they will receive a self-contained merge request from a curated bank of technical exercises.