Sky Software Engineer Interview Questions
& Process

The interview process at Sky was really well set up and professional. I went through four stages: first, a recruiter call, then a technical screen, after that a systems design chat, and finally a panel interview with the team. I really liked how open and clear they were the whole time. The recruiter gave me all the info I needed before each step, telling me what to expect and how to get ready. They even sent over some helpful stuff for the technical part. The technical screen was tough but fair, focusing on solving actual problems instead of weird algorithm tricks. The interviewer was cool and it felt more like we were coding together than them grilling me. The systems design part was super fun because I got to be creative and see how they tackle big challenges. The interviewers seemed genuinely interested in how I thought and what I'd done before. The last panel interview gave me a good feel for the company vibe and how the team works. Everyone was nice and totally answered my questions about work-life balance, growing my career, and what the job is like day-to-day. The whole thing took about three weeks, and they were always mindful of my time. They got back to me quickly after each round and were cool about scheduling around my job. I especially liked when the hiring manager called me personally to talk about the offer, explaining the pay and how I could grow in detail.

First, there were some online technical tests, I think 3 LeetCode algorithm problems. Then, I had a technical interview with 2 people where I had to solve a LeetCode algorithm problem in front of them. After that, there was a 30-minute system design session. One interviewer was very rude and unprepared. He took the problem from Alex Xu's book and was confused about the questions he wanted to ask. I thought the interview was too long for the salary offered.

The interview process seemed to have 3 or 4 stages. I completed 2 assessments: an initial one with psychometric and IQ tests, and a coding assessment. The first assessment, especially the reasoning/IQ part, was interesting and original. It involved finding a password by analyzing previous attempts that partially matched and considering other words not yet tried. After the initial assessment, I waited a couple of days for the coding stage invitation. The communication about the next stage and its time commitment wasn't very clear. The coding questions were difficult for an apprentice with only GCSEs and no prior coding background. Despite having some prior coding experience and partially completing all 3 questions, I didn't pass. The system tracked out-of-window clicks, making me cautious about using Google.