Star logo

Star Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 18 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
77.8% Positive experience

Which role are you interviewing for?

10 roles · 18 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Star.

Showing 4 of 18
Star logo
Star

Senior Mobile Developer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Behavioral

It was a really quick process. It started with a screening call to get to know the company and projects, then a technical interview with open questions about frameworks and languages, and then I got the offer. The whole thing took just 2 days.

Confirmed questions3 questions
  • Can you tell me about Flutter's widgets and lifecycle?
  • How do you handle state management in Flutter?
  • What are the differences between Flutter and React Native?
Star logo
Star

Java Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation
Interview formats
Technical Coding System Design Behavioral

Referred by a friend, so the communication was straightforward. The recruiter reached out soon after. The first screening call was quite easy. It's good they ensure they hire the right people. Following the recruiter call, there were two more interviews. The first was a 1-hour session with two engineers, involving many technical questions and some quiz-like tasks. The second interview was with senior staff or managers, where we talked about my past experience, system design, and hypothetical scenarios. The interviews tend to start simple and get progressively harder. Later, I had a Skype interview with a client, which was relatively simple compared to the previous two.

Confirmed questions2 questions
  • I wasn't expecting the quiz-style tasks during the interviews.
  • Some of the architectural and design questions were quite challenging.
Star logo
Star

Software Engineer

Engineering · more than a year ago

Senior Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding

I communicated with the recruiter via email and sent my resume. The whole interview process lasted one week. The first interview was with the recruiter, where I was asked about my previous job and my most challenging project. Then I had technical questions with two engineers about Ruby and related topics. After two days, I got invited for a second interview. This second interview was a broader technical one where I was asked about databases, transactions, triggers, REST, and XML. Finally, I had to solve two quiz puzzles, one general and one about programming skills. By the end of the week, I received a job offer. The office itself is nice, with cozy open-space rooms, a small kitchen, a fridge, a coffee machine, and various teas.

Confirmed questions1 question
  • Can you elaborate on Ruby's metaprogramming capabilities?
Star logo
Star

Product Manager

Product

Mid Average Neutral experience Decline offer 3 rounds
Interview process
Recruiter call Take home Presentation
Interview formats
Technical Presentation

The interview was pretty standard but had some really specific questions. They interviewed me for both Product and Project Manager roles to save time. It was fine until we got to the opinionated questions, then it got a bit tense. The product management part was easier, and I got a substantial test task. I finished it in a week and got invited to the next stage. That stage was an English check combined with presenting the test task. It was supposed to be a pitch, which is super tough and needs prep, and probably a good way to test English. I wasn't even told I'd have to present, so I didn't do great. That ended up being the official reason they rejected me. Honestly, I still think the process is okay and the company is worth checking out, but the interview part felt a bit unprofessional to me.

Confirmed questions1 question
  • In a scrum process with a great team, perfect environment, and happy customers, why might we consistently fail to deliver on time? What potential problems do you foresee?

Star Interview Questions

Quoted word for word from Star interview reports.

What are the differences between Flutter and React Native?

Read reports

Can you elaborate on Ruby's metaprogramming capabilities?

Read report

In a scrum process with a great team, perfect environment, and happy customers, why might we consistently fail to deliver on time? What potential problems do you foresee?

Read report

Formats, difficulty and experience

Across all 18 Star interview reports.

Interview formats

Behavioral 35.9%
Technical 30.8%
Presentation 17.9%
Coding 10.3%
Other 2.6%

Interview difficulty

Easy 11.1%
Average 61.1%
Difficult 27.8%

Candidate experience

Positive 77.8%
Neutral 22.2%

Reports by job function

Design 9
Engineering 5
HR 2
Product 2