
Stream (CO) Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 23 interview experiences · FREE TO READ
Which role are you interviewing for?
10 roles · 23 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Stream (CO).
Engineer
They had 7 interviews for this role. It was pretty challenging but totally doable if you have the right experience and put in the work to prep. The recruiters were super helpful and always got back to me. There were also interviews about culture and management. They were really quick, the whole thing wrapped up in about two weeks.
- Can you discuss system design?
- How about some live coding?
- Do you have any behavioral questions for me?
Software Engineer
The recruiter was super helpful and made things easy up to the culture fit part. After that, it got a bit weird. The culture fit interview, which I thought would be quick, felt awkward and tense. Then, a surprise interview with the CTO was added late in the game. It got pushed back a few times. When we finally talked, it felt like he was judging me and dismissing my experience, making assumptions and unfairly criticizing my drive. Even though I did well on the technical parts and earlier interviews, I got rejected. It felt like internal politics and changing goals mattered more than my actual skills.
- Can you design an event-driven system?
- How would you optimize databases for better performance?
Marketing
This interview process involved five interviews across different departments, spanning six weeks and demanding significant time and energy while I was already employed full-time. It included a long take-home assignment requiring several hours of work. While most interviews went well, the final in-person meeting with the CRO was problematic. He hadn't reviewed my resume, asked disorganized questions, was dismissive when I asked my own questions, and it seemed inappropriate for a marketing candidate to be interviewed by the head of sales. I received conflicting signals throughout. After waiting a week for a rejection call, I was told my take-home was good, but they sought someone with more experience in technical product writing. The lengthy and slow interview process can cause qualified candidates to lose their drive.
- They asked me nearly 40 questions in total.
Sales
Started with a recruiter call, asking about leadership, culture, and expectations. Then, I talked with the SalesOps leader about cultural fit and the difference between selling to developers versus focusing on business outcomes, which was a pleasant chat. The CEO interview was interesting, with good questions, though the focus seemed to be more on the product itself than on scaling it into an enterprise software platform, and on the developer buyer rather than business results. He said he liked meeting me and wanted to move forward. After one more touchpoint from the recruiter, there was silence. It seems like there are some growing pains and issues with their recruiting, which is a shame because the culture and leaders appear good. Maybe that's why their reviews have dropped. Anyway, I wish them the best and hope they keep improving.
- Have you or your teams sold to application buyers before?
Stream (CO) Interview Questions
Quoted word for word from Stream (CO) interview reports.
“Can you explain what database indexes are, including their advantages and disadvantages?”
Read reports →“How would you optimize performance for sending an infinite amount of data to a client?”
Read reports →“When designing a public API, what factors would you take into account?”
Read reports →“How would you optimize databases for better performance?”
Read reports →“Can you design an event-driven system?”
Read report →“How about some live coding?”
Read report →“What's the company's stance on major events from 2020 like COVID19 and BLM?”
Read report →“What kind of projects have you been involved with that used Go?”
Read report →“What are your methods for optimizing database performance, including the trade-offs associated with choices like indexing?”
Read report →Formats, difficulty and experience
Across all 23 Stream (CO) interview reports.