FLYR logo

FLYR Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at FLYR.

Showing 3 of 5
FLYR logo
FLYR

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding

I applied on LinkedIn and a recruiter called me the next day. We had a quick chat about my willingness to relocate to San Francisco. After that, I was sent an easy coding challenge, which they seemed to really like. Then, I had a technical phone screen with the director of engineering. Because I don't live in San Francisco, they did a mock 'on site' interview for me. It was from 9:00 am to 1:45 pm via Skype, with different people. The first part involved live coding challenges with three separate people, and the second part was more about behavioral questions and discussing the company. Four days later, I got an email saying they weren't moving forward because they felt I didn't have enough experience and would need too much support. It was a pretty good experience though, and everything moved really fast – the whole thing took under two weeks.

Confirmed questions1 question
  • Would you be open to relocating to San Francisco?
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 logo
FLYR

Software Engineer

Engineering

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical System Design Behavioral

Started with a recruiter chat, then talked to the hiring manager, then a technical interview, and finished with an on-site behavioral interview. Communication was good during the process, and my questions were generally answered well. However, some logistics were a bit off; I was asked to use a different tool for the solution design than what was previously communicated, which was unexpected and not ideal.

Confirmed questions1 question
  • Could you walk me through a system design for a product owned by the hiring team?

FLYR Software Engineer Interview Questions

Quoted word for word from FLYR interview 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

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

Read reports

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

Read reports

Could you walk me through a system design for a product owned by the hiring team?

Read report

Formats, difficulty and experience

Across all 5 FLYR interview reports.

Interview formats

Technical 35.7%
Behavioral 28.6%
Coding 21.4%
Case 7.1%
System Design 7.1%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Negative 40%
Neutral 40%
Positive 20%