Let's get a computer science internship

  • Published on

  • View

  • Download

Embed Size (px)


Presentation I gave to help students entering their junior year secure computer science internships


<ul><li>Lets get a software development internship Julian Ozen </li><li>Why you should listen to me How to get an interview How to approach interview practicing </li><li>Why am I talking? Generic career advice isnt always relevant WashU is not a top computer science recruiting school You may not be a top candidate </li><li>Software Developer Positions are not given out solely by intelligence, school, GPA, or referral </li><li>2014 High Paid Interns </li><li>by Gayle Laakmann Mcdowell Sources Recruiters Company Hiring Blogs careercup.com Quora / Reddit / Twitter HackerNewsCracking the Coding Interview </li><li>Are you ready? If youre at WashU, have you taken CSE241? Linked Lists Binary Trees Tries Stacks Queues Vectors / Array Lists Hashtables Breadth First Search Depth First Search Binary Search Merge Sort Quick Sort Tree Insert / Find / etc Bit Manipulation Singleton Design Factory Design Memory Hierarchy Stack vs Heap Recursion </li><li>Why you should listen to me How to get an interview How to approach interview practicing </li><li>Interview Process Build a resume Submitting Application Screening Interviews Follow Up Interviews </li><li>Resume Building CareerCenter is still a valuable resource </li><li>Quantifiable Bullet Point Accomplished ____X____, by using ____Y____, which led to ____Z____. </li><li>Quantifiable Bullet Point Organized and directed a team with diverse technical backgrounds in the design of an urban disaster relief application. What technologies did you use? What was it for? Who did you help? How well did it perform its job? What recognition did it receive? </li><li>Quantifiable Bullet Point Wrote web application in Python, HTML, and JavaScript that checks if internal bridge lines are currently being used, and updates a database correspondingly. </li><li>Projects and Languages WashU doesnt teach anything except JAVA for the first few semesters </li><li>You dont want a recruiter to think youre just a __________ developerJAVA </li><li>You dont want a recruiter to think youre just a __________ developeriPhone </li><li>You dont want a recruiter to think youre just a __________ developerWeb </li><li>Projects and Languages Knowing several languages signals to a company that you are capable of being put on any project Online courses make this extremely easy to learn A projects proves you know that language </li><li>Go to Hackathons Utilize a new technology or language Create a projects to put on a resume Free t-shirts, swag, food, prizes Meet with recruiters and other smart people </li><li>Networking Getting an interview can be the hardest part of the application process Critical if your school doesnt attract top companies Referrals are both everything and nothing </li><li>Apply, Apply, Apply Make an A / B List of Companies, but interview everywhere Multiple offers give you leverage, even for internships </li><li>Why you should listen to me How to get an interview How to approach interview practicing </li><li>Interview Questions Behavioral Coding </li><li>Behavior Question Memorize Resume Talking Points Most Interesting ProjectConflict with Teammates Hardest Bug Most Interesting What languages did you use? </li><li>Coding Questions Done on paper or a whiteboard or collaborative doc so dont practice on a computer </li><li>Coding Questions Ask Questions What attributes does the data have? What resources / libraries can I use? What constraints do I have? What is the context? </li><li>Figure out the catch Coding Questions </li><li>Coding Questions Pseudocode, then "real"code </li><li>Coding Questions Test your code What happens at negative?What happens at 0? What happens at a million values? Does it do what you think it does? </li><li>Coding Questions Remember, these are hard. Go Slow. Stay Calm. Deep Breath. Start with any answer, work towards the best one. Often getting a question wrong does not mean you did poorly. </li><li>This is just the start. There are immediate significant payoffs to putting in hard work in a few specific areas. The best way to be successful is to become comfortable with this process. </li><li>Good Luck! Any questions? </li></ul>