Fearless logo

Fearless Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Fearless.

Showing 3 of 5
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

Software Developer

Engineering · more than a year ago

Mid Average Negative experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Coding Behavioral

I had a recruiter screening for culture fit. Then, I did a live coding session with an interviewer via a third party. After that, I had a technical interview with a principal engineer and a project manager. I was told I passed, but the specific project grant wasn't awarded to Fearless. They asked me to sign a contingent offer for a different project, which seemed interesting, so I agreed. I completed new hire paperwork like W2s. I checked with the agency handling the federal project, and they weren't aware of any grants related to it, though I considered they might not be allowed to discuss it. Later, a job ad for the position I was supposedly waiting on reappeared on LinkedIn, then vanished. I was informed Fearless didn't get that award either. Months passed, and they asked if I was interested in a different project. This made me question where past funding went and if this was a way to manage cash flow or the uncertainty of grant work. I wondered about staff downtime between projects and what happens when contracts end.

Confirmed questions3 questions
  • Recommend movies based on users with similar tastes, explain the O(n) complexity.
  • Regarding the movie recommendation, what are the computational and memory requirements in Big O notation?
  • Which company value resonates with you the most?
Fearless logo
Fearless

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Take home Technical screen Offer
Interview formats
Coding Technical Behavioral

The overall interview process was great, better than others I've experienced. I really enjoyed working with the recruiter. The company seemed like a nice place to work, and I even considered it, but I accepted another offer that felt like a better fit. The process included: 1. A call with the recruiter to discuss my background and the company's culture. 2. A take-home project involving the design of a RESTful API service with multiple endpoints and a Dockerfile for execution, allowing any programming language. 3. A technical discussion with a senior engineer about my experience and the take-home project. 4. An offer extended by the recruiter.

Confirmed questions2 questions
  • Can you design a REST API service to handle CRUD operations?
  • What are your 5-year career aspirations?

Fearless Software Engineer 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

What are some normal technical questions you might ask?

Read report

Formats, difficulty and experience

Across all 5 Fearless interview reports.

Interview formats

Behavioral 33.3%
Technical 33.3%
Coding 33.3%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Negative 40%
Positive 40%
Neutral 20%