UPE

UPE

• Upsilon Pi Epsilon
• Computer Science honors society

What do we do?

• Tutoring hours
• Other academic talks/events
• Inductions in Fall/Spring

How to join

• Requires a 3.4 gpa
• You will receive an email once you've taken the required amount of computer science classes

ACM

What does ACM do?

• Weekly workshops
  • Algorithms
  • Cool technologies
  • New programming languages
• Competitions
  • 2-3 per semester
  • Sometimes with companies
• Mock interviews
• Other events with companies

Coming up

• Programming competition tentatively on November 18th
• Workshops
  • Solving types of brute force problems
  • Making code fast with profiles, threads, and gpus

Links

• Mock interviews
  • bit.ly/2PR89bQ
• Discord
  • discord.gg/invite/FXFu5K5
• Signup for our mailing list
  • binghamtonacm.com

Interviews

What is a technical interview

• Generally 1-3 programming problems
• Problems are often algorithm focused
• Supposed to show how the candidate thinks

Format

• Sometimes the interviewer might ask a few general/resume questions first
• Interviewer gives 1-3 programming problems
• Interviewer asks if the candidate has any questions
  • Try to ask a couple of questions here, about company culture, average day, etc.

What companies look for

• Communication
• Solving the problem correctly
• Thought process

(Disclaimer, we aren't recruiters and don't know how companies make decisons)

Communication

• Discuss how you plan to solve the problem
• Talk about your thought process while coding
• Let the interviewer know if you need to take some time to think about the problem

Try do mock interviews with friends (or ACM) to help practice this

Solving the problem

• Practice interview problems
• Try practice without a computer sometimes
• Resources
  • Leetcode.com
  • Hackerrank.com
  • Cracking the Coding Interview
  • ACM workshops
  • CLRS, Skiena Textbooks (Advanced)
• Practice problems later

Thought process

• Companies say this is the most important part
• How do you approach the problem?
  • Do you consider which data structures to use
  • Do you consider edge cases
  • Do you consider time complexity
• Do you create test cases and test your solution?
• Do you try check if there could be a better approach?

Some tips

• Practice (On paper, ideally)
• Take the interviewers hints
• Plan out your solution before coding
• Don't chase a solution you've seen but can't remember
• Test your code