Blankfactor logo

Blankfactor Interview Questions
& Process

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

Based on 18 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
27.8% Positive experience

Which role are you interviewing for?

9 roles · 18 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Blankfactor.

Showing 4 of 18
Blankfactor logo
Blankfactor

Software Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Technical Coding

So first you gotta do this online assessment, it's mostly basic SQL and some Java stuff. If you do well on that, then you've got a technical interview where they go deeper into Java, like core Java, OOP, DS, and some basic Spring Boot. Then there's a live-coding part, like Leetcode.

Confirmed questions3 questions
  • What are the differences between various data structures?
  • Can you explain exceptions?
  • Tell me about the differences between each data structure and exceptions.
Blankfactor logo
Blankfactor

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Negative experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen Offer
Interview formats
Coding Technical

So I went through this interview process for a role that was initially called 'full stack' engineer. Overall it was okay, but there are some things that could be better. The job title said 'full stack', but it turned out they really wanted someone for React. I always save job descriptions, which was good because the in-office days changed. It first said 2 days, then an interviewer told me 3 days. The recruiter did fix it later, but didn't tell me. Communication was a bit messy between the recruiter and the tech interviewers. This was obvious in my second coding interview. The main interviewer didn't know about the React focus and had to get someone else to join. They handled it fine, but it was unexpected. First coding interview was good, all about javascript/typescript and code snippets. The interviewer was nice and knew their stuff. Second coding interview is where the React thing came up, and they had to bring in another person. Before the offer, I told the recruiter I'd need a week to decide on any offer. When they gave me the offer, the decision time was way shorter. The recruiter did give me extensions when I asked, but the deadline changes and the suggested start date felt rushed. The offer might have been good for 2 days in-office, but with 3 days, the unclear role focus, and the process issues, it wasn't as appealing. The interviewers themselves were great, seemed like a good team. But the red flags made me rethink it.

Confirmed questions2 questions
  • Can you answer basic javascript questions in a way that shows you aren't using ChatGPT during the interview?
  • Evaluate code snippets.
Blankfactor logo
Blankfactor

Technical Product Owner

Product

Mid Average Negative experience Decline offer 3 rounds
Interview process
Recruiter call Offer Background check
Interview formats
Behavioral Other

The interview process was pretty fast, and maybe too fast. I only talked to 3 people including the recruiter for the first call. The recruiter was helpful in getting me ready, but the whole thing ended really unprofessionally. They offered me a job for way less than what the recruiter and I talked about before I even started. So, I sent a reasonable counter-offer within an hour. I didn't hear back for over 24 hours, so I reached out and they said they'd have an answer by Monday. I didn't hear from them on Monday, so I followed up again and the recruiter said 'as with any interview process we are still considering other candidates.' This was after they already gave me an offer! The recruiter said he'd get back to me by the end of the week, but he didn't. I followed up again the next week and then got a 'form' email saying they decided to go with other applicants. I never got a direct response to my counter-offer, and in the end, they treated me like I never got an offer. I felt like they treated me like I was inexperienced and didn't know how recruiting works. I'm glad I didn't take the first offer because I wouldn't want to work for a company that operates like this, lacks transparency, is misleading, and doesn't seem to know that they are interviewing human beings who deserve basic professional courtesies and communication. The whole thing felt shady. I'd be careful about taking a job with this company.

Confirmed questions1 question
  • Can you briefly summarize your background?
Blankfactor logo
Blankfactor

Senior Frontend Developer

Engineering

Senior Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

This was a pretty bad interview experience. The interviewer clearly hadn't looked at my resume and asked me the same HR screening questions about my English and personal life, like 'Tell me about yourself' and 'What do you do in your free time?' The technical part was just one question about why a value might not render in a React component. He mostly talked about React concepts instead of architecture or events. He even bragged about a senior candidate failing to answer his question, which I thought was odd and maybe the question was bad. My answers were right, but he didn't seem to like them. It was super awkward. Then he tried to explain React hooks to me like I didn't know them, which felt like mansplaining.

Confirmed questions1 question
  • Can you explain the reasons why a value might render or not render within a React component across different scopes such as within a useEffect hook, a method, or at the component's root level?

Blankfactor Interview Questions

Quoted word for word from Blankfactor interview reports.

Can you explain the reasons why a value might render or not render within a React component across different scopes such as within a useEffect hook, a method, or at the component's root level?

Read report

What are the requirements, recommendations, and what should be avoided in this process?

Read report

Could you explain the git process and the internal process?

Read report

Tell me about the differences between each data structure and exceptions.

Read report

Formats, difficulty and experience

Across all 18 Blankfactor interview reports.

Interview formats

Technical 39.4%
Behavioral 39.4%
Coding 15.2%
Presentation 3%
Other 3%

Interview difficulty

Easy 22.2%
Average 66.7%
Difficult 11.1%

Candidate experience

Positive 27.8%
Neutral 5.6%
Negative 66.7%

Reports by job function

Engineering 14
Product 2
Operations 1
HR 1