Using GitLab to Power our Frontend Technical Interviews
summary
Company doubles frontend headcount, so a template called Project Cedar uses GitLab CI/CD and a bot account to auto-create per-candidate repos and a test merge request with a failing pipeline candidates must fix. Interviewers use a standardized Google Sheets rubric and a dashboard to track scores, measuring real skills: Git usage, CI familiarity, testing and problem solving. The repo and dashboard are public and the system runs live in interviews.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:53Challenges in remote hiring
- 3:01Drawbacks of previous methods
- 6:14New standardized approach
- 8:42Dashboard and metrics
- 9:03Live demo of Project Cedar
- 12:14Why this model works better
- 13:17Benefits of using GitLab
- 14:19Resources and Q&A
related talks
13mUsing to Power our Frontend Technical Interviews
21mGitLab: The Asynchronous Enterprise
21mUsing CI Templates for Speed and Consistency
42mElevate Your Expertise: the power tools and smart processes of a modern...
28mDeveloper Flow with Google Cloud and GitLab
57mWorkshop. GitLab + CI/CD + JavaScript = ❤️ (part 2)
21mFighting Git Workflows
05mScale tooling before people onboarding
