Future logo

Future Interview Questions
& Process

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

Based on 19 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
31.6% Positive experience

Which role are you interviewing for?

11 roles · 19 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Future.

Showing 4 of 19
Future logo
Future

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Presentation
Interview formats
Technical Coding System Design Presentation

It started with a recruiter call. Then, I got a take-home task where I had to build an API from scratch that was like a main part of their product. After that, I had a 2-hour pair programming session on Zoom. In that session, I had to think of some feature ideas, pick one, and then build it using their actual APIs on my own computer, not some online tool. Once I was done, I had to send them what I made. There was a short 10-minute break before the presentation part. For the presentation, I had to talk about my feature and answer some design questions.

Confirmed questions1 question
  • Can you design an API that meets these requirements?
Future logo
Future

Performance Coach

Other · a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Panel
Interview formats
Behavioral

The interview process was great. The recruiter was very informative. There were three interviews: two with the same person, and the third one was with a panel. They asked a good amount of customer service and coaching style questions.

Confirmed questions1 question
  • How would you handle various customer service situations?
Future logo
Future

iOS Engineer

Engineering · more than a year ago

Mid Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I applied to this company even though their job posting had been up for a month already, so I was surprised to hear back from their recruiter right away. The recruiter was pretty nice and made the interview process pleasant. I then had an interview with one of the members of their mobile team. At first, the interview was okay, but then the questions became more repetitive because it seemed like he wanted to hear some specific keywords. He then asked me about concurrency and multithreading and even mentioned that I had answered them correctly, but he was still not satisfied with my answer. While I was giving an answer about the time I used async/await, he questioned how I was able to use it for API calls at my previous company when it only came out in 2023. He also questioned why I had to use it while calling URLSession for an API call when URLSession has a built-in async/await. He said I didn’t have to use async/await again. What shocked me was that he made these statements with such unwavering confidence. I wanted to just end the interview right after that but tried to remain polite. This is the first time I have ever written an interview review, simply because the interviewer didn’t know what he was talking about at all.

Confirmed questions5 questions
  • Can you tell me about your overall experience?
  • Can you describe your experience with concurrency and multithreading?
  • Tell me about a time you used async/await for API calls.
Future logo
Future

Head of People Operations

HR · more than a year ago

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

It was a terrible waterfall interview process that wasted my time, taking over a month and 7 days to complete. Instead of 1-2 phone screens followed by a full interview with 4 people, I had to successfully complete each interview before moving to the next. To top it off, the recruiter didn't even remember to email me my rejection; I had to send two follow-up emails. The CEO mentioned during the final interview that I'd hear back quickly as he was speaking with the team right after. Instead, the recruiter waited a week, then sent a generic rejection email with a 'Cheers!' sign-off. My advice to interviewers: don't waste over a month interviewing with this company that clearly disrespects candidates. I sent thank you notes to all 5 interviewers, all of which were ignored.

Confirmed questions3 questions
  • What is your understanding of company culture, and how do you implement organizational change?
  • Could you describe your strengths and weaknesses?
  • Be aware of the CEO's interview, as he asks questions that are unclear and complicated.

Future Interview Questions

Quoted word for word from Future interview reports.

Why did you use async/await for API calls when URLSession already supports it?

Read reports

Could you build this appointment API? It should only take about 3 hours.

Read reports

Regarding a partnership with a credit card company that offers a subsidized trial period for customers, how would you determine if the program was successful and decide whether to extend it?

Read reports

How did you use async/await for API calls at your previous company if it was only released in 2023?

Read report

Can you describe how you'd measure the impact of a new feature and compare it to an earlier version?

Read report

Formats, difficulty and experience

Across all 19 Future interview reports.

Interview formats

Behavioral 38.5%
Technical 23.1%
Coding 15.4%
Presentation 15.4%
System Design 2.6%

Interview difficulty

Easy 36.8%
Average 57.9%
Difficult 5.3%

Candidate experience

Negative 52.6%
Neutral 15.8%
Positive 31.6%

Reports by job function

Engineering 8
Other 5
Analytics 3
Operations 2
HR 1