FLASH logo

FLASH Interview Questions
& Process

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

Based on 16 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
87.5% Positive experience

Which role are you interviewing for?

9 roles · 16 reports

Candidate interview experiences

First-hand accounts from people who interviewed at FLASH.

Showing 4 of 16
FLASH logo
FLASH

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design

Applied online and got contacted by a recruiter in a few days. Had a phone screen, then a 60-minute chat with the hiring manager. The last part was a 3-hour block with two technical panels and then an hour going over my resume with the hiring manager and his boss. Everyone was super nice, and the tech panels were actually fun. Even though I didn't think I nailed the tech panels, the interviewers were helpful and kind. What was great is how fast it all was - heard back within days after each stage.

Confirmed questions4 questions
  • Can you walk me through your past roles and experience?
  • Let's do a system design problem using pseudo-code.
  • Here's a logic and coding problem for you.
FLASH logo
FLASH

BDR

Sales · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Group
Interview formats
Behavioral Technical

Extremely humanized interview. They asked a lot about me professionally and personally. Simple questions and a light energy throughout all 3 interviews I had. I had an interview with HR, then one with the pre-sales team (with roleplay), and finally an interview with the head of the department. All in the same vein, wanting to know more about me and my experiences.

Confirmed questions4 questions
  • What do you do in your free time?
  • Tell me about your experiences
  • Tell me about your studies
FLASH logo
FLASH

Product Manager

Product · more than a year ago

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

So I had two interviews, one with HR and then another one with the Product team. Both interviews were pretty moderate in terms of difficulty. The thing is, after the second interview, they sent me an email that EXPLICITLY said I was selected for the final interview round. But then, while we were trying to schedule that last interview, they changed their mind and said there was an 'adjustment' to the role's hiring process and they'd get back to me. It's been 4 weeks since then and I haven't heard anything at all. They basically ghosted me, which is really unprofessional and dishonest. Your company needs to be brave enough to actually tell candidates who've put in a lot of time interviewing where they really stand. I hope the person you ghosted me for ghosts you back.

Confirmed questions1 question
  • Why even bother with this company?
FLASH logo
FLASH

Front End Engineer

Engineering

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding Behavioral

The interview process started with a recruiter call, then moved into several technical rounds. It seemed to be 2 or 3 rounds in total, depending on the interviewer. The first technical round focused heavily on LeetCode problems, specifically easy and medium difficulty ones, so prior practice is key. They surprisingly don't offer take-home tests, saying candidates dislike them, though I think take-homes are a good way to showcase practical skills using tools like create-react-app or next.js. The technical questions also felt a bit dated, asking about older React patterns like higher-order components and class-based components instead of focusing on newer features like Hooks. They also inquired about Redux, a technology less commonly used in newer projects over the last few years, as simpler state management is often handled with the Context API and hooks now. One interviewer seemed unfamiliar with React's memoization features (memo, useMemo, useCallback). There were also some communication disconnects between HR and Engineering, as the process described by the recruiter differed from the actual experience. Initially, I was told multiple roles were open, but later it seemed like only one position was being filled. During the first technical round, I received positive feedback and an assurance of a strong recommendation for the next stage. However, I was also advised to follow up proactively if I didn't hear back, as a previous candidate missed an offer due to an unacknowledged email. The scheduling process was also cumbersome, lacking the use of standard tools like Calendly. Despite some disorganization and what felt like unprofessional moments, like an off-the-record comment during the interview, FLASH appears to be a company with potential, possibly navigating typical growth challenges.

Confirmed questions1 question
  • Could you define what a higher order component is in the context of React?

FLASH Interview Questions

Quoted word for word from FLASH interview reports.

Could you define what a higher order component is in the context of React?

Read reports

What are your thoughts on the technology used in parking spaces?

Read reports

Are your certifications currently active or have they expired?

Read report

Formats, difficulty and experience

Across all 16 FLASH interview reports.

Interview formats

Behavioral 45.9%
Technical 29.7%
Presentation 13.5%
Coding 5.4%
System Design 2.7%

Interview difficulty

Easy 18.8%
Average 62.5%
Difficult 18.8%

Candidate experience

Positive 87.5%
Negative 12.5%

Reports by job function

Sales 4
Engineering 4
Operations 2
Design 2
Finance 1
Other 1