
Starry Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Starry.
Software Engineer
Had a good phone screening with the recruiter where they asked some basic stuff about programming and networking, but told me not to stress about networking. Then, I had a video call with the hiring manager who threw some networking problem-solving questions at me. I found it tough since networking isn't really my thing. The hiring manager seemed really frustrated and negative, which wasn't very professional.
- How would you troubleshoot internet connectivity issues when you can't access a website?
- What could explain slower download speeds when you're further away from the router compared to being right next to it?
Software Engineer
First, I had a recruiter call where I talked about my Python skills. Then, a manager interviewed me to check my networking knowledge and problem-solving skills. After that, I completed a Python technical test. Next, there was a 3-hour team interview that included a coding session with a new Python library, a whiteboard discussion on networking, and a casual chat about my past experiences. This was followed by an onsite coding interview where I had to explain my thought process. They also checked my references. Finally, I got a call with the offer.
- Can you describe a difficult project you worked on and what you gained from it?
- What's the difference between UDP and TCP?
Software Engineer
After applying online, I got an email for a phone interview with the HR director 'Kory' that week. It was about 45-60 minutes and they asked some conceptual C/C++ and network protocol questions. Then, I was asked to do a week-long project to show my planning and coding style, with different objectives. It was a pretty long project needing full attention, but I finished it and all milestones worked. I submitted it a day early and asked if they had questions. They said they'd review it over the next week. Less than a day later, I got a very general email saying I wasn't being considered anymore. I'm not sure if they just wanted my project, but I asked for feedback, pointing out the contradiction. I heard nothing back. I'm really disappointed and frustrated, it felt unprofessional. I think I deserved more than being ignored after a week of work. I never found out why I was out of the running. Seriously consider asking yourself if you're okay with putting in a week of work and then being ghosted the same day you submit.
- Regarding memory allocation in C, what's the proper function to call for freeing memory?
Starry Software Engineer Interview Questions
Quoted word for word from Starry interview reports.
“Create a Big <-> Little Endian converter.”
Read reports →“What is the difference between a semaphore and a mutex?”
Read reports →“What's the difference between UDP and TCP?”
Read reports →“Implement a deck of cards.”
Read reports →“What distinguishes a semaphore from a mutex?”
Read report →“What are smart pointers?”
Read report →“What could explain slower download speeds when you're further away from the router compared to being right next to it?”
Read report →“Regarding memory allocation in C, what's the proper function to call for freeing memory?”
Read report →“Can you explain the difference in dictionary implementation between C++ and Python?”
Read report →Formats, difficulty and experience
Across all 14 Starry interview reports.