Fearless logo

Fearless Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
42.9% Positive experience

Which role are you interviewing for?

13 roles · 21 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Fearless.

Showing 4 of 21
Fearless logo
Fearless

Software Engineer

Engineering · a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

I applied online and had an interview scheduled, but they retracted the meeting just 2 hours later. Honestly, the company name should be changed to fearUS.tech. They reject candidates and cancel meetings for so many silly reasons: qualifications, even though my resume was a direct match to the job description, and salary expectations, even though they claim to be upfront about salary ranges and my expectations were within their brackets. It really showed me their red flags. Definitely not a place I'd want to work. Luckily, I landed an amazing job right after. Keep your heads up, everyone.

Confirmed questions1 question
  • I didn't really get a chance to be asked many questions.
Fearless logo
Fearless

Content Strategist

Marketing · a year ago

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

I applied for a Content Strategist II role at Fearless and had a pretty bad interview experience. I went through two interviews and a background check, but then they changed their business needs and I had to reapply for a different job. After several more interviews for that new role, I was ghosted for weeks.

Confirmed questions5 questions
  • Can you describe your writing skills and experience?
  • What's your background in design?
  • Have you done any editing work?
Fearless logo
Fearless

Site Reliability Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Group
Interview formats
Coding Technical Behavioral

The interview process involved a recruiter call, a clearance conversation, a third-party coding assessment via Karat, a technical interview, and a business fit interview. The entire process was completed in just over two weeks with prompt responses. I found the discussions engaging and the people I interacted with to be pleasant, even though I dislike doing third-party coding assessments.

Confirmed questions4 questions
  • Do you have experience with Python?
  • Can you tell me about your experience with Kubernetes?
  • What are your thoughts on Agile methodologies?
Fearless logo
Fearless

Designer

Design · more than a year ago

Entry Easy Neutral experience Decline offer 2 rounds
Interview process
Recruiter call Background check Offer
Interview formats
Behavioral Technical Presentation

The interview started with a diversity recruitment call, followed by a meeting with a peer and a portfolio manager. During this, background checks for security and drugs were done since the company has federal contracts. Typically, designers have 1-2 more interviews, but I was surprised to get a conditional offer right after the second round. The offer was contingent on the company securing the project contract, which would determine hiring. Other conditions included passing background and drug tests. There were many uncertainties about the team, project details, work location (requiring full-time presence in the project office), and start dates (2-4 weeks after signing). These unknowns made it hard to decide, especially with Fearless pushing to sign without them. For me, the uncertainties were too significant, and I felt the vetting process for a designer wasn't thorough, which contrasts with their stated commitment to nurturing talent.

Confirmed questions1 question
  • Can you describe your design process?

Fearless Interview Questions

Quoted word for word from Fearless interview reports.

Regarding the movie recommendation, what are the computational and memory requirements in Big O notation?

Read reports

Can you design a REST API service to handle CRUD operations?

Read reports

How would you approach writing technical requirements?

Read report

Formats, difficulty and experience

Across all 21 Fearless interview reports.

Interview formats

Behavioral 46.7%
Technical 24.4%
Presentation 11.1%
Coding 11.1%
Other 2.2%

Interview difficulty

Easy 28.6%
Average 61.9%
Difficult 9.5%

Candidate experience

Neutral 28.6%
Positive 42.9%
Negative 28.6%

Reports by job function

Design 6
Engineering 6
Marketing 3
Sales 2
Operations 2
Finance 1