Using to Power our Frontend Technical Interviews
summary
Company doubles hiring while standardizing interviews by using GitLab to seed interview projects via GitLab CI/CD, creating merge-request tasks candidates must review and fix, and automating access with a bot user with expiring permissions. Project Cedar handles template export/import and pipeline triggers so interviewers avoid API key work. A rubric plus a Periscope dashboard measures outcomes; dashboard finds Vue experience is ~30% of staff but not predictive of success, and overall process improves consistency and throughput.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:40Can you raise your hand
- 1:21Problems
- 1:42GitLab
- 1:52Previous Interview Techniques
- 3:44Drawbacks
- 4:21TakeHome Project
- 5:14Project Cedar
- 6:01Email Template
- 6:15Merge Request
- 6:31Rubric
- 6:48Previous Techniques
- 7:11Dashboard
- 8:10Demo
- 10:41Why is this model better
- 11:03Why we use GitLab
- 12:06Why you should use GitLab
- 12:34Resources
related talks
15mUsing GitLab to Power our Frontend Technical Interviews
42mElevate Your Expertise: the power tools and smart processes of a modern...
45mAn Open Source Approach to Driving Developer Efficiency
26mTechnical Interviews Don't Have to Suck
31mWhen GitOps Meets UX
05mScale tooling before people onboarding
57mWorkshop. GitLab + CI/CD + JavaScript = ❤️ (part 2)
21mUsing CI Templates for Speed and Consistency