Wellframe logo

Wellframe Interview Questions
& Process

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

Based on 33 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
45.5% Positive experience

Which role are you interviewing for?

15 roles · 33 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Wellframe.

Showing 4 of 33
Wellframe logo
Wellframe

Software Engineer

Engineering

Entry Easy Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral

So first there was like a quick 15-minute phone screen, you know, the usual. Then I had this Coderpad interview where I was on Google Hangout with an engineer. The last part was the onsite, which was like three interviews back-to-back for about two and a half hours. The first one was more about like, my personality and work style with the person who would be my manager, and then the other two were straight up technical.

Confirmed questions2 questions
  • The technical questions were good in that they weren't ridiculous, more just easy-to-understand questions to allow interviewees to demonstrate a basic aptitude for programming, problem-solving, and creativity.
  • The behavioral questions were all the general things you'd expect in a behavioral interview, though I was happy that everyone seemed interested in parts of my resume that usually don't garner questions.
Wellframe logo
Wellframe

Account Executive

Sales

Mid Average Negative experience No offer 1 round
Interview process
Recruiter call Background check Offer
Interview formats
Behavioral Other

I had a phone screening with two women. They seemed uninterested from the start and only asked me three questions. The first was how I heard of Wellframe, which was pointless since I explained that when I applied online. They only asked about one of my previous jobs. The third question was for an example of how I solved a customer/client problem in a past role. If I hadn't asked them questions, the call would've been about 10 minutes. My questions extended it to nearly 20 minutes. I got a generic rejection email a little over two weeks later on a Saturday. When I asked them to clarify and reconsider because I was qualified, I got an out-of-office reply less than an hour later.

Confirmed questions1 question
  • How did you find out about Wellframe?
Wellframe logo
Wellframe

Client Operations Manager

Operations

Manager Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical

I went through two phone calls, then had back-to-back in-person interviews with four team members. Two weeks later, I had another in-person interview with the CEO. This role was a consideration after a previous opportunity didn't work out. The team was friendly and seemed smart. However, even though it looked positive, the company decided at the last minute to change the job requirements to need a clinical degree, which I don't have. I saw an old review on Glassdoor with a similar situation where they interviewed people, then changed the job description. I get it to some extent, but it's not really considerate of serious candidates who apply carefully.

Confirmed questions1 question
  • How do you get clinical leaders to agree with your plans?
Wellframe logo
Wellframe

Principal Software Engineer

Engineering

Staff Average Negative experience No offer 7 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation
Interview formats
Behavioral Technical Coding System Design Presentation

My interview process started with a good initial chat with the hiring manager. After that, I went through what was supposed to be the final round: six 45-minute interviews back-to-back, totaling 5 hours. It was a long day, but I was up for it because of the clear mutual interest. I felt those 6 interviews went well too. Then, a new exec joined and decided to step in. In a quick 25-minute chat, he thought he knew me better than the 7 people I'd already spoken with and insisted on ANOTHER round of technical interviews. The first of these was kind of weird; it was supposed to be an open-ended architecture discussion, but the interviewer kept saying there was a 'right' answer that wasn't always my own. Plus, they seemed to misunderstand some technical details, like saying the Kafka Streams API was a core part of Apache Kafka. Ultimately, this new exec used his 'findings' to overrule the hiring manager's positive recommendation, and I didn't get the offer.

Confirmed questions1 question
  • Could you write a function to transpose a matrix?

Wellframe Interview Questions

Quoted word for word from Wellframe interview reports.

What steps would you take to diagnose and fix a Java problem related to autoboxing and immutability?

Read reports

Can you walk me through how you would design a system for a medication reminder application that includes dosage information?

Read report

Formats, difficulty and experience

Across all 33 Wellframe interview reports.

Interview formats

Behavioral 47.9%
Technical 25.4%
Presentation 14.1%
Coding 7%
System Design 2.8%

Interview difficulty

Easy 12.1%
Average 84.8%
Difficult 3%

Candidate experience

Positive 45.5%
Neutral 15.2%
Negative 39.4%

Reports by job function

Engineering 10
Operations 7
Other 4
Product 3
Sales 3
Analytics 2