FLYR logo

FLYR Interview Questions
& Process

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

Based on 38 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
44.7% Positive experience

Which role are you interviewing for?

23 roles · 38 reports

Candidate interview experiences

First-hand accounts from people who interviewed at FLYR.

Showing 4 of 38
FLYR logo
FLYR

Technical Product Owner

Product · nearly a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Behavioral Presentation

The interview process with Flyr lasted for almost two months and included 4-5 rounds with multiple interviewers. It started out seeming organized, but the communication became inconsistent. I was told after each round that the process was continuing, but later found out that someone else was already offered the position while I was still interviewing. Even after the final round, I was told to wait another two weeks because they were 'trying to open a similar position,' but that never happened. I eventually got a vague email saying there was still no clarity and wishing me luck. It felt like there was a lack of internal alignment and transparency. I get that processes can change, but candidates should get timely communication and honesty about their status. The interviewers were professional, and the product discussion was interesting, but the communication was poor, there was a lack of transparency, and the hiring process was slow and disorganized.

Confirmed questions1 question
  • How do you handle prioritizing roadmap planning for the product backlog?
FLYR logo
FLYR

Product Owner

Product · nearly a year ago

Mid Difficult Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Presentation Group
Interview formats
Behavioral Technical Case Presentation Group

First, there was a screening chat with the Recruiter. Then, a Technical interview with the Manager. After that, a Business case task to do over 3 days. This was followed by a Business case presentation with the Manager and Tech Lead. Lastly, a Cultural fit discussion with the team.

Confirmed questions2 questions
  • Could you tell me about your experience within the airline industry?
  • And what's your background with Agile methodologies?
FLYR logo
FLYR

Senior Backend Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical System Design

The interview process was a bit bumpy. The links they sent didn't work at first, which caused some delays and confusion. In the first round, the recruiter seemed disengaged, which wasn't ideal. The technical part was challenging because the interviewers kept interrupting, and the whole thing felt disorganized. They didn't really introduce the session or give an agenda. It was just a barrage of questions without much context, making it hard to show what I can do. It felt like they were more interested in showing off their own knowledge than understanding my experience. I think a more structured approach would be better, with clear goals upfront so everyone can have a more productive and respectful conversation.

Confirmed questions1 question
  • Can you design a system that implements their current project?
FLYR logo
FLYR

Technical Lead

Engineering

Lead Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Phone screen
Interview formats
Technical Coding Case

I applied online and was quickly contacted for an interview with the hiring manager. Then, I received a take-home technical challenge that simulated real-life scenarios I'd encounter daily. The scenarios felt realistic given my domain experience. Next, I had a technical interview with two team members. This involved tasks building on the take-home assessment and some domain knowledge questions. After about two weeks, I received negative feedback, which I felt was unfairly focused on specific SQL knowledge, though their reasoning was fair within their criteria. While the interview process itself was okay, I was really put off by being promised future opportunities that never materialized. It left a bad taste in my mouth.

Confirmed questions4 questions
  • Using air ticket price history data, can you find and explain the cheap, expensive, and volatile markets?
  • With flight information tables, could you construct an arrival board for a specific airport?
  • Can you create a list showing connections between different city pairs?

FLYR Interview Questions

Quoted word for word from FLYR interview reports.

How do you check if a TCP port is listening on a remote server using the Linux shell?

Read reports

Can you identify that a city-airport dictionary key is missing?

Read reports

With flight information tables, could you construct an arrival board for a specific airport?

Read reports

Can you explain the difference between throughput and latency?

Read report

Using air ticket price history data, can you find and explain the cheap, expensive, and volatile markets?

Read report

Can you create a list showing connections between different city pairs?

Read report

Formats, difficulty and experience

Across all 38 FLYR interview reports.

Interview formats

Behavioral 39.3%
Technical 34.5%
Coding 8.3%
System Design 6%
Other 3.6%

Interview difficulty

Easy 21.1%
Average 71.1%
Difficult 7.9%

Candidate experience

Positive 44.7%
Neutral 18.4%
Negative 36.8%

Reports by job function

Engineering 14
Product 5
Operations 4
Analytics 4
HR 3
Design 2