1. SOFTWARE ENGINEERING JOBS Tyler White & Mim Cobaj

2. About Us  Double CS & Math Major  Cannot stop eating Buffalo Wild Wings  Solved an NP-complete problem in polynomial time  Hope to open up the first machine learning obedience school for AI pets  CS Major, Math Minor  Renaissance Man of the Year Award Winner[1995]  Using a decision tree to lead me  Currently reading "Physically Based Rendering" by Rharr Humphrys so I can make a world that's better than mine MimTyler

3. What We’ll Talk About  What different interview processes are like from our experiences  What a professional work environment is like  How to make the perfect lemon meringue pie

4. Interviews: How to Get Recognized  Keep your resume up-to-date  Don’t sell yourself short!  Stay active in the CS Department  GitHub and LinkedIn  Apply to many places (even places you don’t see yourself working in, in 5 years)  SIDE PROJECTS  SIDE PROJECTS MORE SIDE PROJECTS

5. Interviews: BAE  Phone screen about resume  Don’t put anything on there you’re not willing to talk about  On-site interview  Suit & Tie  Know how to talk through a program and how you would design it

6. Interviews: UPS  Only half technical  Dress up business casual  Know your stuff on the languages they require  It’s a conversation not a competition  They might ask questions to see if you know what the company is

7. Interviews: Google  Dress down, but try to keep it nice (only for the interview)  Want to see how you think  Again, it’s a conversation (really important for this interview)  Interviewer might seem distant, don’t worry!  Know your algorithms, data structures, and run times

8. Interviews: How to Prepare  Research the company  Great books on difficult coding interviews  Cracking the Coding Interview  Coding Puzzles: Thinking in Code  Review all basic data structures/algorithms and learn more in depth ones with extra time  Preparation is nothing without practice

9. Interviews: Response  Yes  They will tell you all you need to know for the next steps  No  Don’t worry! Rejection is a natural part in life  We didn’t get Google but we’re not scared of living in our parents basements

10. Jobs  Don’t expect to write 100 lines of code a day  They don’t just throw you in  Built to last  Code reviews  Development, Testing, and Production

11. Jobs: BAE  Integrate with an existing team  Read project documentation  Learn a codebase  SCRUM  Develop C++ OOP  Unit tests  Company wide presentation  On-site presentation to management

12. Jobs: UPS  A couple of days of setup  A week or so of learning the design of the project I was going to be working on  Coding and Learning  Once comfortable, given the green light on a solo project  Agile programming for internal application  End of the summer presentation

13. Jobs: Local startup  Much more relaxed environment  Quick flexible design  Client doesn’t always know what they want  Extreme agile programming  Refactoring a lot is common  Meetings happen often to stay on track

14. Questions?