How long does the folk interview process take?

Most candidates spend between 4 and 8 weeks from recruiter screen to offer. The onsite loop itself runs in a single day or is split across two half-days, with debrief and offer typically within 5 business days after.

How should I prepare specifically for folk?

Focus on three things: (1) the company DNA shown above - what they actually grade for, (2) the rounds in your loop, especially the round most candidates underestimate, and (3) drilling on the question types in this guide using a structured framework like CIRCLES or STAR.

Does this apply to engineering or design roles at folk?

The DNA stays the same - what changes is the round mix. SWE candidates face coding screens instead of Product Sense; designers face portfolio reviews and design exercises. The "what they value" and behavioral signals carry across all functions.

Other roles at folk:Product Manager Software Engineer Sales Customer Success Marketing

Growth · Software Engineer Interview Guide

Interview language: English

How to Pass the folk Software Engineer Interview in 2026

The folk DNA (TL;DR)

The practical application of folk's features, like the 'Recap Assistant', is a key evaluation point in their interview loop. They seek individuals who can articulate practical, user-centric solutions that directly improve the folk product experience and simplify complex workflows.

The folk Interview Loop

Your onsite loop will typically consist of 5 rounds.

1
Round 1
Recruiter Screen
Motivation, role fit, logistics.
2
Round 2
Coding Screen
LeetCode-medium algorithmic problems under time pressure.
3
Round 3
System Design
Distributed systems, trade-offs at scale, architecture under constraints.
4
Round 4
Onsite Coding
LeetCode-hard, debugging, code clarity, edge cases.
5
Round 5
Behavioral / Leadership
Past evidence of ownership, influence, resolving conflict.

The Danger Zone: Top Reasons Candidates Fail

Based on our database of folk interview outcomes, avoid these common traps:

Not demonstrating a clear process for resolving the conflict.
Designing an overly complex or inflexible query language.
Not being able to articulate their own technical reasoning.
Failing to demonstrate how the learning was applied in subsequent work.

Test Yourself: Real folk Questions

Three real prompts pulled from our database.

Type · motivation

What interests you about folk's mission to help teams build better relationships with their customers, and how does that align with your career goals as a software engineer?

Type · debugging

Here's a code snippet that's supposed to calculate the average interaction time per customer, but it's producing incorrect results. Find and fix the bug.

Type · learning-from-failure

Tell me about a time a product or feature you worked on did not meet expectations or failed. What did you learn from that experience, and how did it change your approach going forward?

+ many more questions, signals, and worked examples

Unlock the folk rubric, free

folk Interview Question Bank

A sample from our database, grouped by round. Sign up to see the full set.

9 of 18 questions shown

Recruiter Screen

1
Type · motivation
What interests you about folk's mission to help teams build better relationships with their customers, and how does that align with your career goals as a software engineer?

Coding Screen

2
Type · algorithmic
Given a list of customer interactions (timestamp, type, customer_id), write a function to find the number of customers who had more than 3 interactions within any 1-hour window.
3
Type · data-manipulation
Implement a function that takes a list of customer objects, where each object has a `tags` array, and returns a map where keys are tags and values are lists of customer IDs associated with that tag. Ensure each customer ID appears only once per tag.
+ 1 more questions in this round (sign up to unlock)

System Design

4
Type · api-design
Design an API endpoint for folk that allows users to search for customers based on a combination of metadata fields (e.g., company size, industry, last interaction date range, tags). Consider performance, scalability, and flexibility for future search criteria.
5
Type · scalability
folk's user base is growing rapidly. How would you design a system to process and store millions of customer interaction events daily, ensuring low latency for retrieval and high availability?
+ 1 more questions in this round (sign up to unlock)

Onsite Coding

6
Type · algorithmic
Implement a function to find the longest common subsequence between two lists of customer interaction types. For example, if interactions are ['email', 'call', 'meeting', 'email'] and ['call', 'meeting', 'email', 'chat'], the LCS is ['call', 'meeting', 'email'].
7
Type · code-quality
Refactor this piece of code that manages customer segmentation logic. Improve its readability, maintainability, and testability. Consider potential edge cases and ensure it handles them gracefully.
+ 1 more questions in this round (sign up to unlock)

Behavioral / Leadership

8
Type · conflict-resolution
Tell me about a time you had a significant disagreement with a cross-functional team member (e.g., engineering, marketing) about a product decision. How did you approach it, and what was the outcome?
9
Type · learning-from-failure
Tell me about a time a product or feature you worked on did not meet expectations or failed. What did you learn from that experience, and how did it change your approach going forward?
+ 6 more questions in this round (sign up to unlock)