Fast (CA) logo

Fast (CA) Interview Questions
& Process

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

Based on 24 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
45.8% Positive experience

Which role are you interviewing for?

13 roles · 24 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Fast (CA).

Showing 4 of 24
Fast (CA) logo
Fast (CA)

Software Engineer

Engineering

Mid Easy Negative experience Decline offer 4 rounds
Interview process
Take home Technical screen Technical screen Recruiter call
Interview formats
Coding System Design Technical Behavioral

The whole thing took like 2 weeks. Had to do a homework assignment for frontend/backend, then a system design interview for frontend/backend, and a coding interview for frontend/backend. Also had a behavioral and values interview with an EM. It was a really weird process overall, felt like the interviewers and recruiter weren't sure what they wanted. The offer was super shady too, the numbers kept changing. They were totally unclear about the ISOs, wouldn't share details to understand the compensation. They told me to value shares at X price with Y strike price instead of (X-Y) * # of ISOs. Recruiters were awful, never called when they said they would, and communication was terrible. Too shady for me, not a good experience. Be super careful.

Confirmed questions4 questions
  • Homework: Build a React App Using an API
  • Systems Design: Design a generic application
  • Coding: Design and build a generic board game
Fast (CA) logo
Fast (CA)

Lead

Operations

Lead Average Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Presentation Panel Background check Offer
Interview formats
Behavioral Technical Presentation

A recruiter reached out to me on LinkedIn in late September 2021. I was interested but told them I needed leadership opportunities with pay matching my experience. They said they could meet my salary needs. Communication was slow and sometimes a leader had to reschedule and showed up unprepared. There were long gaps (1-3 weeks) between interview steps, so much so that the hiring manager forgot our first meeting by the second one. The whole process felt long and like they didn't respect my time. It started with an HR screening (30 mins) in late September. Then an interview with the hiring manager (30 mins) in early October. After passing that, I got a big case study with a few exercises and process flows (3 hours). Once the hiring manager reviewed my slides, I had two more interviews in mid-late October with a potential direct report (30 mins) and a potential collaborator (30 mins). Then in early November, I interviewed with the hiring manager again (30 mins) and a senior leader (30 mins). Because the senior leader was unprepared the first time, we had a second meeting (30 mins). In total, I spent about 6.5 hours interviewing. At the end of November, two months after starting, I got an email saying they weren't moving forward but were impressed and wanted to stay in touch. I asked for feedback but never heard back. They then reposted the job soon after. I was uneasy about the case study because I worried they'd use my work without paying for consulting. I've interviewed for director roles before and never had to do so much work upfront. I'm hesitant to do that again.

Confirmed questions4 questions
  • Can you tell me about your experience with leadership, specifically how you build and manage teams?
  • Describe how you operate and lead in a fast-paced and changing environment.
  • Can you discuss your case study presentation?
Fast (CA) logo
Fast (CA)

Customer Support Engineer

Engineering

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Behavioral Technical

The technical recruiter was really great to work with, super professional and responsive. I got to meet the rest of the team too, they were really personable and seemed genuinely interested. I really liked how engaged everyone was and how well they represented the role and the company. They were also really flexible with interview timing and managed to set up back-to-back interviews since they're trying to fill this role quickly. Even though I didn't get an offer, I did ask for feedback from the recruiter and the hiring team to understand why I wasn't a fit, but unfortunately, I didn't hear back. I would have really appreciated that feedback as it would be super helpful for my future interviews. Overall, it was a positive interview experience.

Confirmed questions1 question
  • Tell me about a challenging situation you encountered and how you resolved it.
Fast (CA) logo
Fast (CA)

Frontend Software Engineer

Engineering

Mid Average Negative experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding

The overall interview process was okay. I started with a technical screen with a senior engineer which went well, and they were quite friendly. After that, I moved on to the virtual onsite interviews. I had good conversations with most interviewers, but my last coding interview was a bit rough. The task involved some HTML/vanilla JS, and the interviewer offered very little guidance. They didn't seem very engaged and when I asked for help, they just said I needed to figure out what was wrong. It felt less like a pairing session and more like being watched struggling with a challenge that isn't really relevant to the actual job. Despite this, most other interactions were positive, but I ultimately didn't get an offer. I've also heard some negative things about the company, so that's something to consider.

Confirmed questions2 questions
  • How would you convert an RGB color value to its Hexadecimal representation and then display it on the screen?
  • Given a pre-implemented search query function, how would you build a React application to display and sort the search results?

Fast (CA) Interview Questions

Quoted word for word from Fast (CA) interview reports.

How would you convert an RGB color value to its Hexadecimal representation and then display it on the screen?

Read reports

Given a pre-implemented search query function, how would you build a React application to display and sort the search results?

Read reports

Build a pod in eks that runs a curl on a schedule. (Note: They preferred screensharing despite offering other methods.)

Read report

What steps would you take to troubleshoot a latency problem?

Read report

Implement solutions involving arrays, hash tables, and trees.

Read report

Formats, difficulty and experience

Across all 24 Fast (CA) interview reports.

Interview formats

Behavioral 41.5%
Technical 26.4%
Coding 15.1%
Presentation 5.7%
System Design 5.7%

Interview difficulty

Easy 29.2%
Average 62.5%
Difficult 8.3%

Candidate experience

Neutral 8.3%
Negative 45.8%
Positive 45.8%

Reports by job function

Engineering 10
HR 5
Sales 5
Operations 3
Finance 1