Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
If you apply for a programming job, you may be asked to complete a take home code challenge, "pair program" with another developer, and/or sketch out some code on a whiteboard. A lot has been said of the validity and fairness of these tactics, but, company ethics aside, what if you just need a job? In this talk, I'll show you a series of mistakes I have seen in these interview challenges and give you strategies for avoiding them. I'll give recommendations for how you can impress the programmers grading your work and I'll tell you which rules you should bend in your solutions.
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
In the talk titled "Implementing the LHC on a Whiteboard," speaker James Edward Gray II discusses strategies to excel in coding interviews, addressing commonly used interview formats and offering practical advice based on his own experiences. Key Points:\n- **Interview Formats**: Gray identifies different types of coding interviews including take-home tasks, technical interviews with live pairing, whiteboard interviews, and audition-style tasks where candidates work on a company’s application. He emphasizes that the methods used can feel disconnected from real-world programming. - **Preparation Strategies**: Gray stresses the importance of familiarizing oneself with commonly asked coding problems and algorithm concepts, particularly Big O notation, which helps in analyzing the efficiency of algorithms. He suggests developing a strong understanding of algorithms and problem-solving techniques. - **Common Mistakes to Avoid**: He highlights the importance of understanding the problem statement before diving into coding. He recounts a personal anecdote where miscommunication led to a misunderstanding during an interview. - **Demonstrating Thought Process**: Gray encourages candidates to articulate their thought process during interviews, using phrases like "My first thought is..." to maintain communication. He regards humbly admitting gaps in knowledge as a strength. - **Focus on Core Challenges**: Candidates should prioritize solving the main problem rather than getting sidetracked with bonus challenges or excessive setup work. Writing tests alongside coding is also encouraged to enhance clarity and presentation of solutions. - **Professionalism and Presentation**: Appropriate behavior in interviews is essential; candidates are reminded to maintain professionalism and avoid distractions that could signal unfit behavior. - **Use of Tools and Techniques**: Gray recommends practicing coding with resources like Exorcism.io and contributing to open-source projects to build a professional portfolio. In conclusion, Gray emphasizes that while there is no guaranteed way to ace coding interviews, focusing on preparation, clear communication, and a sound understanding of algorithms can significantly increase chances of success. His advice serves as a roadmap for aspiring developers to navigate the often stressful interview process effectively.
Suggest modifications
Cancel
