Granular logo

Granular Interview Questions
& Process

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

Based on 38 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
39.5% Positive experience

Which role are you interviewing for?

12 roles · 38 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Granular.

Showing 4 of 38
Granular logo
Granular

Product Designer

Design

Senior Average Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Presentation Background check Offer
Interview formats
Behavioral Technical Presentation Coding

Started with a phone call with the hiring manager about the company and design team. Then a video call with the hiring manager, director of design systems, and another product designer for a portfolio review and a 30-min design exercise. Moved to the final on-site interview, spread over 2 days. This included a portfolio presentation and interviews with the design team, a lead PM, a lead engineer, and the head of design. The interview process was okay, but I didn't get a good sense of the design team. Some interviewers seemed unprepared. My recruiter was wonderful, very forthcoming and honest, helpful every step of the way, preparing me thoroughly for the on-site. He followed up with feedback explaining why they chose other candidates. Even though I didn't get an offer, I appreciated his honesty and his willingness to be a resource for me.

Confirmed questions3 questions
  • Tell me about how you collaborate with other functions.
  • What are your expectations when joining a design team?
  • We'd like you to complete a design exercise based on the Granular product.
Granular logo
Granular

Data Scientist

Analytics

Mid Average Negative experience No offer 4 rounds
Interview process
Take home Onsite
Interview formats
Technical Coding Other

Applied online and got a take-home assessment, then was invited for an onsite. The onsite has 3 interviews, each lasting an hour, where you're given a dataset and need to do classification. The first two are focused on timeseries modeling, so be quick. The last one is a basic SQL/Pandas interview. The Data Scientists there are typical SF 'coder bros', acting superior and quick to point out errors. It's tough to model a dataset without knowing the features and with the time pressure. The VP of DS does give feedback, but they should really re-evaluate their interview process. Honestly, I'd avoid this company.

Confirmed questions3 questions
  • Model the data with location as a factor.
  • Model the data with time as a factor.
  • Basic SQL/Pandas questions.
Granular logo
Granular

Office Operations Specialist

Operations

Entry Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

I applied online and a Recruiter reached out to me setting up a phone interview. It was a nice conversation about the role and my background. The same day I got an email for a second round interview via video chat. It was with the hiring manager - a pleasant talk, more about the role and "what would you do if" questions. Since they are super responsive, the same day I got an invitation for an onsite interview. In the meantime I got another job offer that is much more convenient for me because of short commute, so I accepted it and didn't attend the onsite interview. I have a very very good impression about the company, interview process was very smooth, and the interviewers were professional and outgoing.

Confirmed questions2 questions
  • Could you introduce yourself and walk me through your background?
  • Describe how you would handle various scenarios.
Granular logo
Granular

Senior Software Engineer

Engineering

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Coding Behavioral

The interview process involved an initial call with the recruiter, then a conversation with the hiring manager, and finally a lengthy 4 hour 45 minute on-site interview which included two 15 minute breaks. Some parts of the interviews felt a bit awkward due to slow speech and long pauses. I had asked about the coding environment and if there was any specific preparation needed. I was told to be ready to clone a repo, which I assumed meant we'd work from a project. Turns out, that was incorrect. The interviewers expected me to have a project already set up using a tool I'd never used before, and it wouldn't even work on my machine. I really wish I had asked what tools I'd need to prepare in advance. I felt blindsided and like the interview was over before it started, especially when I was expected to use a framework I wasn't familiar with in a way I'd never encountered.

Confirmed questions2 questions
  • Can you write a function to convert between various units of measurement?
  • Could you build an application that fetches data from an API and displays it in a table, using provided helper libraries, and includes retry logic for API failures?

Granular Interview Questions

Quoted word for word from Granular interview reports.

Can you write a function to convert between various units of measurement?

Read reports

Can you build models using two datasets for two problems within 1 hour?

Read report

Can you whiteboard a function to convert different units of measurement?

Read report

Formats, difficulty and experience

Across all 38 Granular interview reports.

Interview formats

Behavioral 34.2%
Technical 26.6%
Coding 15.2%
Presentation 11.4%
Other 6.3%

Interview difficulty

Easy 31.6%
Average 36.8%
Difficult 31.6%

Candidate experience

Positive 39.5%
Negative 39.5%
Neutral 21.1%

Reports by job function

Engineering 10
Analytics 9
Sales 8
Design 4
Product 3
Operations 2