Flooid logo

Flooid Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
30.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Flooid.

Showing 3 of 13
Flooid logo
Flooid

Software Engineer Intern

Engineering · more than a year ago

Intern Average Neutral experience Accept offer 3 rounds
Interview process
Presentation Technical screen Onsite
Interview formats
Presentation Technical Coding Behavioral

We had an assessment day. First, we did a presentation on a tech topic applied to retail. Then, there was a written assessment with questions about Java, like very specific behavior of operations in the language. After that, half the candidates went home, and the rest did an algorithms test, followed by an interview with higher management at the end.

Confirmed questions3 questions
  • Basic algorithm questions, possibly involving counting pairs of values in an array.
  • Discussing time/space complexity for algorithm questions.
  • Expressing passion for Computer Science.
Flooid logo
Flooid

Software Developer

Engineering

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Group Presentation Background check Offer
Interview formats
Technical Group Coding Behavioral Presentation

So I applied online, then had a 20-min technical phone interview. After that was the assessment centre, which went from 8:30am to about 3pm. At the assessment centre, we did a group exercise, a multiple-choice technical test, a reasoning test, and a data analysis report. We had lunch with current students, and then they let us know if we got to the next stage. The interviews themselves were a bit of a mess, in my opinion. There were 3-4 interviewers and about 6 of us, and they only interviewed one person at a time, so some people left early while others stayed late. It felt unprofessional with one interviewer making jokes and having a condescending attitude. The interview felt rushed, and I don't think the interviewers knew how to get the best out of us, so make sure to explain everything thoroughly, even if they don't ask follow-up questions, as they ask very open-ended questions like 'how much do you know about databases and SQL?'

Confirmed questions2 questions
  • Tell us about your experience and what you can contribute to PCMS.
  • What experience makes you fit in PCMS and what can you bring to it?
Flooid logo
Flooid

Software Developer

Engineering

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I applied online and then got a call for a 20-minute telephone interview. It was mostly technical questions, with just a few competency-based ones.

Confirmed questions4 questions
  • Could you tell me what you know about PCMs?
  • What are the primary components of OOP?
  • Can you describe your experience with different programming languages?

Flooid Software Engineer Interview Questions

Quoted word for word from Flooid interview reports.

What differentiates an ArrayList from an array and a list?

Read reports

Write an object-oriented program to determine if a string is a palindrome, using provided objects and tests.

Read reports

What are hash tables, how do they operate, and what is their syntax?

Read reports

What can you tell me about arrays, including how they function and their syntax?

Read report

Can you describe linked lists, their operation, and syntax?

Read report

Formats, difficulty and experience

Across all 13 Flooid interview reports.

Interview formats

Technical 35.1%
Behavioral 27%
Coding 16.2%
Presentation 10.8%
Group 8.1%

Interview difficulty

Easy 7.7%
Average 92.3%
Difficult 0%

Candidate experience

Positive 30.8%
Neutral 53.8%
Negative 15.4%