Get an internship: Tips for interviews and applications
•
23 likes•9,013 views
This document provides advice for getting a software development internship. It discusses why the author is qualified to give advice, how to get an interview, preparing for interviews, the interview process, resume building, networking, applying to many companies, and approaching interview questions. Key points include gaining experience with multiple programming languages through online courses and projects, attending hackathons, networking, applying widely, and practicing behavioral and coding interview questions by thinking through examples out loud rather than on a computer.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (12)
Similar to Get an internship: Tips for interviews and applications
Similar to Get an internship: Tips for interviews and applications (20)
Recently uploaded
Recently uploaded (20)
Get an internship: Tips for interviews and applications
- 1. Let’s get a software development internship Julian Ozen
- 2. Why you should listen to me How to get an interview How to approach interview practicing
- 3. Why am I talking? Generic career advice isn’t always relevant WashU is not a top computer science recruiting school You may not be a top candidate
- 4. Software Developer Positions are not given out solely by intelligence, school, GPA, or referral
- 5. 2014 High Paid Interns
- 6. by Gayle Laakmann Mcdowell Sources Recruiters Company Hiring Blogs careercup.com Quora / Reddit / Twitter HackerNewsCracking the Coding Interview
- 7. Are you ready? If you’re 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
- 8. Why you should listen to me How to get an interview How to approach interview practicing
- 9. Interview Process Build a resume Submitting Application Screening Interviews Follow Up Interviews
- 10. Resume Building CareerCenter is still a valuable resource
- 11. Quantifiable Bullet Point Accomplished ____X____, by using ____Y____, which led to ____Z____.
- 12. 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?
- 13. 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.
- 14. Projects and Languages WashU doesn’t teach anything except JAVA for the first few semesters
- 15. You don’t want a recruiter to think you’re just a __________ developerJAVA
- 16. You don’t want a recruiter to think you’re just a __________ developeriPhone
- 17. You don’t want a recruiter to think you’re just a __________ developerWeb
- 18. 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
- 19. 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
- 20. Networking Getting an interview can be the hardest part of the application process Critical if your school doesn’t attract top companies Referrals are both everything and nothing
- 21. Apply, Apply, Apply Make an A / B List of Companies, but interview everywhere Multiple offers give you leverage, even for internships
- 22. Why you should listen to me How to get an interview How to approach interview practicing
- 24. Behavior Question Memorize Resume Talking Points Most Interesting ProjectConflict with Teammates Hardest Bug Most Interesting What languages did you use?
- 25. Coding Questions Done on paper or a whiteboard or collaborative doc so don’t practice on a computer
- 26. Coding Questions Ask Questions What attributes does the data have? What resources / libraries can I use? What constraint’s do I have? What is the context?
- 27. Figure out the catch Coding Questions
- 28. Coding Questions Pseudocode, then "real"code
- 29. 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?
- 30. 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.
- 31. 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.