Sequoia logo

Sequoia Interview Questions
& Process

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

Based on 99 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
48.5% Positive experience

Which role are you interviewing for?

30 roles · 99 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Sequoia.

Showing 4 of 99
Sequoia logo
Sequoia

Intern Software Engineer

Engineering · half a year ago

Intern Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Technical screen Recruiter call
Interview formats
Coding System Design Technical Behavioral

So at Sequoia Group, first they looked at my resume, then I had to do an online coding test. After that, there was a technical interview where they asked me about data structures and system design stuff. Finally, I had an HR round to check how well I communicate, work with others, and if I'd fit into the company culture.

Confirmed questions1 question
  • Design a scalable REST API for a student management system, including how to handle authentication.
Sequoia logo
Sequoia

Data Scientist

Analytics · a year ago

Lead Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral Presentation

Recruiter reached out over LinkedIn. The interview process was a bit messy, with initial rounds getting rescheduled multiple times. I got good feedback from each round and was eventually called in for the final HR round. We talked about company culture, and then she asked about my expected compensation. I shared my expectation and reminded her that I'd already told her this before the first round, and only proceeded after confirming it was within their budget. After the HR round, there was no communication. When I tried to contact the recruiter, they just said they were moving with another candidate, with no specific reason or feedback despite me asking. This was really off-putting, especially after investing time (while working) and passing all rounds, including the final HR one where we discussed expectations. Good companies communicate transparently and give feedback to those who reach the final stage. They should at least say why I wasn't considered at the final stage, or if compensation was the issue (which they didn't mention initially). It was a total waste of time.

Confirmed questions4 questions
  • Can you tell me about your projects?
  • What are your thoughts on LLM evaluation?
  • How do you approach hallucination mitigation in LLMs?
Sequoia logo
Sequoia

Onboarding Director

Operations · a year ago

Director Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

I found the process lacking and unprofessional for a company of this size. I was contacted by an in house recruiter for the role. The process seemed straightforward: phone screen with the recruiter, then a 30 minute call with the hiring manager. The interview with the hiring manager was very one sided- the HM used the entire time we had to ask questions of me but did not save any time for me to ask her any questions. The HM mentioned she had a hard stop when I asked if she had time for my questions, so I was not able to further assess the role/team. Fast forward 3 weeks and not a single word from the recruiter - completely ghosted. I never ended up following up with them either since I accepted another role at a different company. The whole experience was off putting and as a result, I would not seek out future roles here.

Confirmed questions1 question
  • How do you manage when you have too many things to do at once?
Sequoia logo
Sequoia

Frontend Engineering Manager

Engineering · a year ago

Manager Easy Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical Coding

I went through two technical rounds. The first one was fine, but the second round was weird. The interviewer, a senior engineer (staff level), seemed to not know about Progressive JPEGs, thinking they only worked with React. He also only knew about module federation for multi-frontend architecture and didn't understand other options. It felt like the staff engineers interviewing didn't have enough technical knowledge. I don't think it's worth your time. You probably won't get past round two, and even if you do, their poor decisions in the debrief will likely cause problems. I got one coding question in each round and finished it quickly (12-15 mins), but I still got rejected. It seems like feedback from 2022 for frontend devs is similar. Pro tip for candidates: Only talk about module federation for microfrontends, or they might just reject you. For leadership: Maybe try AI summaries of interviews. The insights could show you where interviewers need to improve. I also wondered if unconscious bias, maybe gender-related, affected my rejection, which could explain the company's low diversity. Just something to think about. Hope this helps candidates and leadership.

Confirmed questions4 questions
  • Could you explain the event loop?
  • Can you write a function to flatten an array?
  • How would you implement Progressive JPEGs?

Sequoia Interview Questions

Quoted word for word from Sequoia interview reports.

What are the distinctions between high-level design (HLD) and low-level design (LLD)?

Read reports

If you were given a million dollars, where would you put your money?

Read reports

Can you explain the difference between monolithic and mono repo architectures?

Read reports

What role does configuration management play in DevOps tool specialization?

Read reports

Design a scalable REST API for a student management system, including how to handle authentication.

Read report

Can you explain the distinction between an inner join and an outer join?

Read report

What are three words your closest friends would use to describe you?

Read report

What are your thoughts on different multi-frontend architecture strategies besides module federation?

Read report

Formats, difficulty and experience

Across all 99 Sequoia interview reports.

Interview formats

Behavioral 50.7%
Technical 24.4%
Presentation 8.5%
Other 5%
Case 3.5%

Interview difficulty

Easy 27.3%
Average 51.5%
Difficult 21.2%

Candidate experience

Neutral 12.1%
Positive 48.5%
Negative 39.4%

Reports by job function

Operations 21
Sales 14
Engineering 14
HR 13
Other 10
Analytics 8