I'm a Computer Science student, and I'm currently looking for software engineering internships. I graduate in ~1 year or so, so I'm interested in how interviews work for full-time entry-level positions as well.
Companies are so different and ask various questions - How can you predict with decent accuracy what's going to be on their interviews? Also are behavioral questions in a tech interview generally the same for most companies?
This depends what roles you are applying for. Are you looking at Software Engineer, Product Managers, or other roles? What kinds of companies are you applying to? You can generally find mock questions on Glassdoor for larger companies. For software roles, Leetcode (data structures & algorithms) tends to be the gold standard. When looking for the answer to this question for you, you'll want to look online or ask here based on what you are applying for.
As far as the behavioral questions, there are some themes, but it will vary by interviewer. Some companies have specific requirements, like Amazon focusing on their Leadership Principles, which you want your stories to relate to. Preparing detailed, clear stories for different themes is important. You can look up formats like the STAR method.
Once you have interviews lined up for specific roles at specific companies, you can make your preparation more specific. Until then, think about the roles you want to apply to and cater your interview preparation to generally getting ready for those roles.
This is a high-level question, but it's a good one as I've seen so many engineers mess this up. Of course, there are always going to be curve balls on interviews, but there is a surprisingly high amount of information you can extract to focus your studying and boost your chances.
I have a lot of thoughts here, so I'll split my interview scouting tactics up into 3 sections:
Big Tech interviews are tough due to the difficult questions and strict grading, but this is heavily counter-balanced out by their predictability. Here are the 2 things you absolutely have to do for every Big Tech interview:
If you are completely blindsided by your Big Tech interview, you probably did something wrong.
I talk about all this more in-depth here: [Masterclass] How To Ace Your Big Tech Interview - Data Structures And Algorithms
If you're interested in my Meta story: How Alex Got Into Meta With 0 Prior LeetCode Experience
Startups are much trickier, especially if they're on the smaller side (i.e. Series B or earlier). At a high-level, startups will generally rely more on practical coding, but this will vary as the startup ecosystem is inherently high-variance. I cover startup interview tactics in-depth here: "How to prep for interviews at a startup?"
Congratulations almost graduate!
Personally, I have not encountered a time thus far where the recruiter (startups and big tech) straight up refused to provide me any information on the interview process and pointers. (There has been one instance where the recruiter said they had no idea... probably not a great sign? Haha.) Typically, they have taken the time to brief me on the subsequent interview rounds and during that time, I have always received a helpful response to, "Would you be able to give me an idea of what the technical interview might entail? For example, is it sort of a real-life business-related coding exercise or a Leetcode type of problem?"
100% agree on what Alex and David have said~ scour Glassdoor interview reviews (a lot of info on startups too these days, as long as they aren't Seed stage) and be well-prepared for the behavioral round (using STAR method).