Build in Public
How Building in Public Can Help You Attract Your First Startup Hires
Use building in public to show candidates your product, mission, working style, and open problems before you recruit your first startup hires.
By Uriel Bitton · 4 min read
The short answer
Building in public can help early startups attract better-fit hires by giving candidates evidence about the product, mission, pace, decisions, and working style before an interview. Share real work, explain why it matters, show how you operate, and make hiring needs explicit. It does not replace active sourcing or structured evaluation; it makes the company easier for the right people to understand and self-select into.
Building in public can help early SaaS founders attract strong first hires because candidates can see the company before a job description appears. Public product decisions, customer lessons, tradeoffs, and progress give potential teammates evidence about the mission, pace, and working style. It does not replace active recruiting or a structured interview process; it makes the company easier for the right people to understand and self-select into.
Your first hires are choosing more than a role
An early employee is joining a company that is still changing quickly. Product, responsibilities, and priorities may all move. Y Combinator has emphasized alignment with the kind of company you are trying to build, not simply filling a generic function. Public work can give candidates that context before the first recruiting call.
GitLab’s public handbook describes how the company operates and explicitly calls the handbook a talent-acquisition tool because candidates can inspect how GitLab works. GitLab also says transparency helps it recruit people who care about its values. A five-person SaaS does not need a 2,000-page handbook to use the same mechanism.
Build a public talent surface
Think of your build-in-public history as a talent surface: public evidence that lets a potential teammate answer four questions before you ask them to join.
1. What are we building?
Make the problem and product legible. A future engineer, marketer, or customer-success hire should understand who the product serves, why the problem matters, and what stage the company is in. Product screenshots help, but decisions and customer problems often reveal more than polished launch assets.
2. Why does the work matter?
Explain the mission through specific work instead of repeating a slogan. A post about why you rejected a feature, changed onboarding, or narrowed the customer profile shows what the company considers important. Early hires can use that evidence to judge whether the problem and responsibility appeal to them.
3. How do we work?
Public decisions can reveal operating style: how quickly you test ideas, respond to customer feedback, and make tradeoffs. Buffer says its external salary transparency helps prospective candidates understand its salary system before entering hiring. The broader principle is giving candidates truthful evidence they can evaluate.
4. Who do we need next?
Do not wait until the job listing to make the need visible. When a real constraint appears, explain it. Instead of posting “we are hiring an engineer,” describe the problem the person would own, the current state of the product, and why that work matters now. Buildside’s guide to attracting opportunities while building in public uses the same idea: make the useful person and next action recognizable.
Use the Work–Why–Way–Who format
For hiring-related public updates, use four parts:
Work: what the company is actually building or learning.
Why: why the problem or decision matters.
Way: how the team approached the work and what that says about how you operate.
Who: the kind of person who could help with the next constraint and one clear way to respond.
A hypothetical example: “We have spent the last month reducing onboarding drop-off. The hard part is turning noisy behavior into an explanation a founder can act on. We are looking for an engineer who likes ambiguous product problems, talks to users, and wants to shape the system rather than inherit a finished spec.”
Let candidates self-select before you interview
Transparency can improve the match even when it reduces applicant volume. A candidate who dislikes rapid iteration, public decision-making, or customer-facing engineering should be able to discover that early.
Y Combinator hiring guidance makes a similar point about broadcasting the culture you actually want so aligned people are drawn toward it and mismatched candidates can opt out. Public building gives founders raw material for that signal because culture is visible through repeated decisions rather than a careers-page adjective.
Keep recruiting active
Do not expect strong candidates to appear automatically because you post consistently. Early-stage hiring still requires founder effort: sourcing, introductions, relationship-building, and a deliberate evaluation process. A public record can make those conversations warmer because candidates can inspect the product, mission, and operating style before engaging.
Buildside’s founder-brand framework is useful here too: repeated public work should connect a problem, your point of view, proof, and the product. For hiring, add the team question: what kind of person would want to help build the next chapter?
Before your next hire, review your last ten public updates. Could a strong candidate understand what you are building, why it matters, how you make decisions, and where they might contribute? If not, you may not need more recruiting content. You may need to make the real work more legible.
Sources
Frequently asked questions
Can building in public actually help a startup hire people?
It can make the company easier for potential candidates to discover and evaluate by showing real product work, decisions, values, and working style. It does not guarantee applicants and should complement active sourcing, referrals, and a structured hiring process.
What should founders share publicly to attract early hires?
Share real product decisions, customer-safe problems, tradeoffs, progress, lessons, and the type of constraint the next hire would help solve. Candidates should be able to understand both the mission and how the team actually works.
Should I announce a role before I am ready to hire?
You do not need to post a formal opening early, but you can make the emerging need visible by explaining the problem or responsibility that is becoming important. When the role is real, provide a clear next step and accurate expectations.
Does public transparency replace a careers page or interview process?
No. Public work gives candidates context and can improve self-selection, but the role still needs clear requirements, compensation and process information, and a consistent evaluation method.
A note from Uriel Bitton
Building in public can do more than attract users. A useful public record also shows potential teammates what the company cares about, how decisions are made, and what kind of problems they would help solve. The goal is not recruiting content for its own sake; it is making the real work legible enough that the right person can imagine joining it.
Keep building with us
Get practical founder lessons and product updates in your inbox.