Flix logo

Flix Software Engineer Interview Questions
& Process

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

Based on 24 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
37.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Flix.

Showing 3 of 24
Flix logo
Flix

Software Engineer

Engineering · nearly a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel
Interview formats
Technical Coding Behavioral

So the interview process was pretty structured and seemed legit at first. It kicked off with an HR chat, then I got this coding challenge to do over seven days. Once I sent it back, I had a general chat with a senior engineer and a product owner. After that, two developers and I did a technical deep dive on that same challenge. I was supposed to talk to the Engineering Manager next, but before that, I got this quick 'feedback call.' They told me that even though the team's feedback was 'super positive,' they suddenly had 'technical doubts.' They never brought up these doubts during the actual interviews, which made the end result feel fake and not upfront. The sudden switch in how they communicated makes me wonder about how honest the company is and if their hiring process is really that coordinated.

Confirmed questions3 questions
  • Can you discuss application monitoring?
  • How do you handle deployment and delivery processes?
  • What are your general development practices?
Flix logo
Flix

Software Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Technical Coding System Design Behavioral

It was a four-part interview: first HR, then the Project Manager, followed by a technical part where we did discussion, live coding, and system design, and finally a behavioral interview. The whole thing went smoothly and they really focused on stuff that matters for the job, like frontend security, RBAC, feature tagging, accessibility, component architecture, performance, and keeping code in good shape.

Confirmed questions7 questions
  • What are your thoughts on frontend security?
  • Can you explain RBAC?
  • How do you handle feature tagging?
Flix logo
Flix

Software Engineer

Engineering

Entry Average Negative experience Decline offer 7 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel Background check Offer
Interview formats
Technical Coding System Design Behavioral

The interview process was extremely lengthy. It began with an email for a 45-minute initial call with a recruiter. A week later, I received a take-home task that took about 3-4 hours to complete. After submitting it, I got feedback two weeks later suggesting minor changes. I made those changes, and about a week after that, I was invited to discuss the task. This was followed by a technical interview with two engineers, though only one showed up. The interview focused on the tools used for the job and included one or two problems. A week after that, I received invitations for two successive interviews: one with the hiring manager and then another with the team and the hiring manager. Subsequently, I had a call to discuss my salary expectations and onboarding. Other than the technical interview and the take-home task, the interviews were quite repetitive, essentially covering the same ground. During the team interview, both sides (team, manager, and myself) seemed to run out of things to discuss. Regarding compensation, the salary offered was below average for a company of this standing, with no significant bonuses or benefits.

Confirmed questions5 questions
  • Could you complete a system design take-home task, including answering questions about scalability, system design, and optimization relevant to the specific use case?
  • Be prepared for technical questions covering SQL syntax, joins, and aggregations.
  • There will be questions related to concurrency.

Flix Software Engineer Interview Questions

Quoted word for word from Flix interview reports.

Can you find mentions of the company using the Twitter API?

Read reports

How would you improve the Twitter API mention finder solution?

Read reports

What are the advantages and disadvantages of different task runners for ETL tasks?

Read reports

Describe how you would architect an event-driven system.

Read report

What are your thoughts on different task runners for ETL tasks?

Read report

Formats, difficulty and experience

Across all 24 Flix interview reports.

Interview formats

Behavioral 32.3%
Technical 30.8%
Coding 24.6%
Presentation 4.6%
System Design 4.6%

Interview difficulty

Easy 12.5%
Average 87.5%
Difficult 0%

Candidate experience

Negative 58.3%
Positive 37.5%
Neutral 4.2%