Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2019 - Beyond the whiteboard interview by Joel Quenneville & Rachel Mathew _______________________________________________________________________________________________ Cloud 66 - Pain Free Rails Deployments Cloud 66 for Rails acts like your in-house DevOps team to build, deploy and maintain your Rails applications on any cloud or server. Get $100 Cloud 66 Free Credits with the code: RailsConf-19 ($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2019) Link to the website: https://cloud66.com/rails?utm_source=-&utm_medium=-&utm_campaign=RailsConf19 Link to sign up: https://app.cloud66.com/users/sign_in?utm_source=-&utm_medium=-&utm_campaign=RailsConf19 _______________________________________________________________________________________________ You've spent a lot of time preparing for this moment. Your palms are sweaty. You take a deep breath, walk into the room, and shake hands with the candidate. Welcome to the interview! Interviewing can be intimidating and our industry is notorious for interviews that are arbitrary, academic, and adversarial. How can we do better? Come be a fly on the wall for a real interview! At thoughtbot, we've put a lot of thought into crafting an interview that is both humane and allows us to accurately capture a candidate's strengths and weaknesses relative to the real-life work they will be doing.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Beyond the whiteboard interview" features Joel Quenneville and Rachel Mathew discussing the interview process at thoughtbot during RailsConf 2019. The session aims to demonstrate a more humane and collaborative approach to technical interviews, moving away from traditional whiteboarding methodologies. Key points discussed include: - **Preparation for the Interview**: The nervousness of candidates is acknowledged, with an emphasis on creating a comfortable environment for discussing interview questions. A collaborative discussion model is suggested, as opposed to a confrontational one. - **Interview Structure**: Quenneville explains that the interview will involve scenario-based questions that mix technical queries with consulting-related aspects such as team interactions and project scope. - **Technical Scenarios**: The hypothetical project involves building a self-service appointment scheduling system for a gym. Candidates are prompted to explain their methods for understanding existing codebases and defining the Minimum Viable Product (MVP) based on client requirements. - **Onboarding Process**: The candidate shares strategies for onboarding to a new codebase, including checking models and running test suites. - **Defining MVP**: The discussion leads to defining the MVP, establishing the importance of self-service for gym clients while debating the complexities of scheduling appointments and handling holidays. - **Modeling Objects**: The conversation evolves towards data modeling. Through iterative brainstorming, they explore various structures for schedules, appointments, and eventually arrive at a more sophisticated solution for handling holidays versus standard hours. - **Flexibility in Design**: By the end of the discussion, they devise effective strategies that allow for scalability and the inclusion of features such as multiple gym locations and special events. - **Conclusions and Next Steps**: The interview wraps up with a discussion about the next steps in the interview process, emphasizing the importance of collaboration, feedback, and continuous improvement in both interview and work settings. **Key Takeaways**: - The importance of a collaborative interview style that reflects real-world work scenarios. - Understanding the nuances of MVP scoping and technical decisions within software development. - The need for robust testing and modeling strategies that can adapt to the dynamic needs of projects.
Suggest modifications
Cancel
