ITT: Interview Tips

feeling friendly today, here's some basic tips:

>interviewers always ask a set of really common questions, prepare for those
>research the company you're applying to, prepare to ask questions
>have multiple copies of your resume handy
>if doing software dev, be prepared to show them your projects on github
>actually have some projects you can show off
>some places also care about hackerrank
>read cracking the coding interview, but also be prepared for places that don't use it.
>understand your body language and try not to sperg out

>>57704298
I have a hard time determining what to put on github.

Should I put class projects? I forget about those as soon as i do them, if they ask me what I did 10 weeks ago on a project I honestly probably wouldn't remember.

Should I put my toy problems I write up on there? I implement mathematical code to solve certain problems.

Should I put my side projects on there? Usually those get the jobs done but the code could be optimized

Not sure what to add to my githb

Cram everything 1 week before exams

Yes, BAE Systems, pretty chill, just 2 interviews with a presentation on a complex problem in the last one, then I managed to turn the rest of it into a general chat about technical stuff which I really enjoyed and so did the people interviewing me so I got the job

>>57704838
What company/position is it? What is your job role like? Hours? What languages you program? I'm jelly

>>57704864
just said BAE Systems, some kind of software development role, but it's on some really cool projects

40 hours a week

best language that fits the task really, C++, python, C#, etc.
any good company will look for your computer science skills, not your ability in a single language
a good computer scientist will be able to pick up any language that is needed quickly