Stylight logo

Stylight Software Engineer Interview Questions
& Process

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

Based on 11 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
63.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Stylight.

Showing 3 of 11
Stylight logo
Stylight

Senior Software Engineer

Engineering · more than a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral Coding

I applied online and the first step was an HR call. Then, I was sent a technical challenge to complete within 2-3 days. After submitting it, I received an invitation for a technical interview 3-4 days later. This technical interview focused on discussing my approach to the technical challenge. Following up multiple times, I was invited 10 days later for a management interview with the CEO & VP, which seemed a bit unusual. Ultimately, I received a rejection email four days after that.

Confirmed questions8 questions
  • The HR person asked some basic questions.
  • Technical challenge: why did you use this approach?
  • How would you approach this in real-time?
Stylight logo
Stylight

Software Engineer

Engineering · more than a year ago

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Coding

My interview process with Stylight took about a month. The main issue was their slow responses and not being clear about the process status, like if they were waiting for feedback or if other candidates were still being interviewed. They also didn't give an estimated wait time for the next steps. I had two main rounds. The first was a 20-minute call with the technical recruiter. He introduced himself, I introduced myself, and he asked about my company knowledge, salary expectations, and availability. Right after that, he gave me a take-home assignment to complete over the weekend. After I submitted it, I had to follow up after two weeks. The following week, I had my technical/managerial interview where we discussed my past experience and some improvements to my take-home assignment solution. I had to follow up again after another week, and that's when I found out I didn't make it to the next round. No feedback was given on why. Because I had to chase them for status updates for weeks, I doubt I would have gotten any feedback even if I had followed up more.

Confirmed questions2 questions
  • Regarding your application, what led you to choose Spring Boot, and which of its specific advantages did you leverage?
  • What was the reasoning behind your decision to decouple your application?
Stylight logo
Stylight

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding

Started with a quick HR Skype call (about 15 mins) where they really sold the company. The next day, I got a take-home assignment due in two days. After that, there was a technical Skype interview with the team. We talked about my test assignment solution, I answered some theory questions, and did two coding problems on a whiteboard. It all felt pretty good. Then, I went to the office to hang out with the team and meet the CTO. We worked on a problem together, and we had lunch. I think I really messed up the problem-solving part with the team though. A few days later, I heard they went with someone else. A bit of a bummer, but my own fault. I'd give Stylight's hiring process a 5/5 – super fast, clear, and welcoming.

Confirmed questions1 question
  • How would you implement the functionality of Counter.most_common() using a Python dictionary?

Stylight Software Engineer Interview Questions

Quoted word for word from Stylight interview reports.

How would you implement the functionality of Counter.most_common() using a Python dictionary?

Read reports

How would you explain TCP vs. UDP to someone not technical?

Read reports

Could you build a budget notification system utilizing RDBMS and Python?

Read reports

Could you develop a REST application and a CLI script to hit the endpoint with arguments (JSON/XML payload)?

Read reports

What was the reasoning behind your decision to decouple your application?

Read report

What is your approach to designing a system for ingesting client signals?

Read report

Regarding your application, what led you to choose Spring Boot, and which of its specific advantages did you leverage?

Read report

Formats, difficulty and experience

Across all 11 Stylight interview reports.

Interview formats

Technical 32.3%
Coding 25.8%
Behavioral 19.4%
System Design 9.7%
Presentation 6.5%

Interview difficulty

Easy 9.1%
Average 90.9%
Difficult 0%

Candidate experience

Negative 18.2%
Neutral 18.2%
Positive 63.6%