I think it means they haven't started resume screening yet. More on reddit.com

143k members in the csMajors community. All about studying and students of computer science. More on reddit.com

did they have data structures or algo in the HackerRank? I am worried cause i have only taken an intro:Python class

More on reddit.com

Hi there, I'm a former interview-trained Facebooker. In this loop, you'll most likely get either two different easy-ish questions or an easy question with a milder followup. As an intern candidate, don't expect any system design or leadership questions. These questions will mostly gauge your ability to code/how well you understand your tools, how well you do with algorithms and data structures, and generally, how well you thrive within mild ambiguity. The expectation is for this to be somewhat interactive, and it's always better to work out the solution with your interviewer (including guiding them through your solution process as well as asking clarifying questions). Some tips that I've always found helpful (for my own personal interviews as well as from what I've observed interviewing others): It's always better to work through the problem solving process out loud with your interviewer. Don't worry, we all get stuck on problems during interviews, and being able to either contain the scope of the problem or to work out hairy details of the design with your interviewer/potential future peer is always a good sign. The hiring rubrik does heavily lean towards having a good mastery of algorithms/data structures, but most interviewers will also value being able to work through a problem with a little bit of nudging from their part. In fact, this is one of the expectations from the interviewer's part: you're expected to struggle a bit with the question, otherwise it's difficult to tell how your mind works. Get a good night of rest before the interview. While it's not as crazy for skype interviews, interviews are generally more social and informal than most people treat it. The hiring process is not a full meritocracy precisely because our "signals" for strong/lean hire/no-hires are pretty bullshit and unrealistic. At the end of the day, if you can vibe with the interviewer, that'll help your case through the hiring committee much more than if you can memorize the solutions to every problem. Don't memorize solutions to problems. It's a horrible way to spend your time "studying" for interviews, and it doesn't always help. If you're interested, I can also go through what the process after your interview may look like. There's quite a few factors that affect the outcome. Most interviewers procrastinate on sending up feedback, so typically by the time they do finally submit their decision, they only have their notes and a camera shot of a whiteboard to go on. I'll add more once I get back home. More on reddit.com