
Starry Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 50 interview experiences · FREE TO READ
Which role are you interviewing for?
26 roles · 50 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Starry.
Technical Support
It was a really easy process, they mainly wanted to see how much you know about electronic devices and internet services. Also asked a few questions about deescalating customer issues. Pretty much they just wanted to know how good you are at guiding customers through fixing their devices.
- Can you describe how you would guide a customer through troubleshooting their Roku TV?
- How would you walk a customer through troubleshooting a Roku TV?
Software Engineer
I had a 30-minute phone chat where they asked why I was interested in Starry and some other basic stuff. Then came about 15 quick questions on C++, networks, data structures, threading, etc. The next thing was a 'short' programming homework problem. It had a lot of things I hadn't used before, so it was pretty hard for me. I spent a ton of time and energy on it, losing sleep to work on it along with school stuff. I was basically always thinking about it and how to make it perfect. After a couple of all-nighters, I sent it in. They told me no a few days later. Pretty annoying since I spent two weeks of my life on this assignment.
- Implement a deck of cards.
- C++ questions were asked.
- Networking questions were asked.
Financial Analyst
I applied online and heard back from the recruiter about one to two weeks later to set up a phone interview. The first phone interview lasted about 30 minutes and the recruiter was really professional and prepared. I mainly just talked through my resume and experience. The second phone interview was with the Head of Finance, and it was pretty relaxed, more like a conversation about me with a few quick finance questions thrown in. Sadly, they let me know the role had shifted to a business ops/analyst position and they went with someone else who was a better fit for those requirements. I get it though, with the company being a startup and growing.
- What about this role and company interested you?
iOS Developer
It started with a recruiter phone screen, then a call with the hiring manager, followed by an in-person interview. This was a pretty standard iOS developer interview. The engineers I met were really nice and seemed like great people to work with. The interview had four parts: a behavioral session, a coding problem, a deep dive into my experience, and a whiteboard problem. It felt like a startup environment, with an open office that seemed a bit packed. I ended up declining the offer because the salary wasn't as high as I expected for a Senior iOS role. The recruiter could have done a better job selling the position too; he came across as a bit unfriendly when he extended the offer, but maybe that was just me.
- Can you elaborate on the design patterns you employ and the reasoning behind their selection?
Starry Interview Questions
Quoted word for word from Starry interview reports.
“Create a Big <-> Little Endian converter.”
Read reports →“Can you write a function, ideally in Python, that checks if a word is a palindrome?”
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 report →“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 →Formats, difficulty and experience
Across all 50 Starry interview reports.