Redesigning the core hiring workflow for small teams who only hire a few people a year. Screening, scheduling, and messaging in one place, with nothing they don't need.
Context
Most hiring tools are built for companies that hire constantly. Applicant tracking systems, multi-stage pipelines, integrations with a dozen other platforms. That's great if you're a 200-person company with a dedicated recruiting team. But the majority of businesses on Wellfound aren't that. They're 5 to 30 people, hiring one to five roles a year.
For these teams, existing tools felt like overkill. They'd sign up for an ATS, spend a week configuring it, use it for one hire, and then forget the login. Or worse, they'd just manage everything in spreadsheets and email threads, losing candidates in the process. The tools that existed were either too complex or too bare. Nothing lived in the middle.
Discovery & Research
We started with a simple question: what does hiring look like when it's not your full-time job? We needed to understand the mental model of someone who opens a role once or twice a year and has to context-switch back into "hiring mode" every time.
Opened a role. Couldn’t remember how we did it last time. Found January’s spreadsheet.
12 applicants, all in Gmail. Starred the good ones. Lost two in a thread.
Scheduling 3 candidates with 2 teammates. 14 emails. One double-booking.
Logged into the ATS trial again. Couldn’t find anything. Closed it. Back to the spreadsheet.
Scheduling Screening in email Follow-ups dropped Forgot own process Abandoned an ATS
Synthesized findings from diary studies and interviews, mapped against the hiring journey
Strategy & Framing
The research made one thing clear: the product needed to do fewer things, not more. We identified four core jobs that every small team needs to get right. Everything else was out of scope on purpose.
Surface the most relevant applicants without requiring teams to read every resume. Structured screening criteria that anyone on the team can apply consistently, even if they've never hired before.
Eliminate the "what time works for you" email chains. Integrated calendar availability that lets candidates self-schedule, with automatic reminders for both sides.
Templated messaging that feels personal, not robotic. Status updates, rejection notes, and next-step emails that teams can send in two clicks instead of drafting from scratch every time.
A simple, visual pipeline that answers the question "where is everyone?" without requiring any setup. Default stages that work out of the box, with the option to customize if needed.
Design Process
The design challenge wasn't building features. It was removing friction. Every screen had to earn its place, and every interaction had to feel obvious to someone who only hires a few times a year.
The biggest structural decision was adopting progressive disclosure throughout the product. New users see a clean, minimal interface with sensible defaults. As they use the tool and their needs grow, advanced options reveal themselves naturally. This meant occasional hirers could get started in minutes, while teams that hire more frequently could unlock deeper functionality without switching tools.
Traditional ATS products require 30 to 60 minutes of setup before you can do anything useful. We flipped that completely. Essentials ships with pre-built templates, default pipeline stages, and smart suggestions based on your role type. Teams post a job and start reviewing candidates in under five minutes, with zero configuration.
We tested this with 8 teams who had never used a hiring tool before. Every single one was able to post a role and review their first applicant within the first session, without reading documentation or watching a tutorial.
1:12 role posted✓3:40 first applicant in✓4:51 reviewed, screen booked✓
One of the clearest insights from research was that candidate communication was scattered across email, Slack, and text messages. We designed a unified inbox that brings all candidate conversations into one place, threaded by candidate and role. Team members can collaborate on responses, leave internal notes, and see the full history without leaving the product.
Key Design Decisions
Every feature ships with an opinion. Pipeline stages, email templates, screening criteria, evaluation rubrics. All of it comes pre-configured based on role type and team size. The philosophy was simple: if 80% of teams would set it up the same way, just do it for them. Configuration exists for the 20% who need it, but it's never the first thing you see.
In most hiring tools, scheduling is an afterthought or a paid add-on. For small teams, it's the single biggest time sink. We made it a core part of the product: calendar sync, candidate self-scheduling, automatic timezone detection, and one-click confirmation. No integrations required, no extra cost. This single decision eliminated the most common reason teams told us they abandoned hiring tools.
Most ATS products are designed for a dedicated recruiter. But on small teams, hiring is a shared responsibility. The founder screens resumes, the engineering lead does technical interviews, the office manager coordinates schedules. We designed every surface for collaboration: shared evaluations, @mentions in candidate notes, role-based permissions that don't require an admin to set up. The goal was to make hiring feel like a team sport, not a solo task.
Outcomes
Essentials launched as Wellfound's lightweight hiring toolkit, purpose-built for teams that hire occasionally. It replaced a fragmented workflow of spreadsheets, email, and calendar apps with a single product that handles the entire process.
Reflection
The hardest part of this project wasn't adding features. It was resisting the urge to add them. Every stakeholder conversation surfaced another "what if we also..." and the discipline required to keep saying "not yet" was constant. The product's strength came directly from its constraints.
I learned that designing for occasional users is fundamentally different from designing for power users. You can't rely on learned behaviors or muscle memory. Every interaction needs to be self-explanatory because your user might not come back for three months. That constraint pushed me to design interfaces that are genuinely simple, not just visually clean but cognitively lightweight.
This project also reinforced something I believe deeply: the best product design often looks like subtraction. The features we removed or never built were just as important as the ones we shipped. When you're designing for people who don't want to think about your tool, the highest compliment is that they barely noticed it was there.