Yeah done my fair share of grad software interviews earlier this year.
As smath said, make sure you have the job spec open, but make sure you aren’t typing owt during the interview, they’ll hear it over the phone, so don’t google shit
Things I’d say you need to know about the company:
- Current products they’re working on
- How and when they started (if you can find it, usually on the about section of a webpage)
- Their future plan, are they taking on more AI projects? If so they’re probably looking to expand into AI.
- If they have ‘values’, learn them and relate yourself to each and every point. both IBM and BT did this for me, they’ve got skills, strengths, values or some buzzword like that, it’s almost always found on the website somewhere, and it’s their core principles surrounding the company, it’s almost always a bollocks way for HR to dictate if you’ll be a good fit for the company or not, but if they have a list of values, have a list of your own of a time you’ve demonstrated you are competent at one of those values.
I can’t advise enough that you take @smather up on his offering of a grilling, this is where you’re really going to see where you’re going to choke / if you’ve done enough prep.
That’s probably enough to get you by the interview if it’s not a technical one. If it’s a technical one, you need to learn:
- Development lifecycles and agile methodologies, and how much you love them no matter what your feelings towards them are
- If you’re doing C++ learn how memory is allocated on the stack, heap or in static memory, if you’re doing Java then be able to talk about the JVM and JIT compiler.
- Learn object orientation principles, encapsulation and all that bollocks
- Go through their job description, nit pick out every single technical requirement they want from a developer, and be able to talk about it.