Comment by leeny

Comment by leeny

Ok, there are some things to keep in mind when negotiating with founders rather than recruiters. (I just grabbed this from the book and edited it down a bit.)

At young startups (seed and possibly Series A), there often isn't a recruiting team. Until a startup hires a recruiting team, usually one of the founders handles important hiring-related tasks, such as negotiation. Even if they do have one or two recruiters on staff, sometimes the founder hasn’t handed over the negotiation reins to them yet.

In case you do find yourself negotiating with a founder, here's how to handle it because if you treat them just like recruiters, the results could be disastrous.

Here’s the most important difference between recruiters and founders. Recruiters are doing a job, and at larger companies, they’re often following a script. Though we always advise you to be enthusiastic, gracious, and courteous (and we take great pains in our copy to do so), at the end of the day, there’s an undercurrent in our negotiations: if you read between the lines, we’re practically shouting, “Look! Here’s my leverage! I’m cold and calculating and indifferent! Money talks!”

For founders, everything is personal. The company is their baby, and talking to them like they’re a recruiter may upset them and make them think you’re wasting their time. Moreover, many founders are not experienced at hiring, especially if it’s their first company, and may not have had many candidate conversations. The playing field between you and a founder is, in this way, much more level than it would be with a recruiter.

Here’s a real story to drive these points home.

One of our users had just wrapped up the onsite at a seed-stage startup. The final step was to meet (once more) with the founders. During the call, they asked him where else he was interviewing. Using our playbook, he was deliberately vague and said that he’s interviewing with a number of companies, at various stages, and is unable to share more information at this time.

The founders dug in and asked several more times if he was interviewing with big tech companies. He held the line, even though the founders were visibly surprised in the meeting that he wasn’t more forthcoming.

After the meeting, the candidate got an email from their recruiter saying that they wouldn’t be moving forward because “we aren’t sure what you’re looking for.”

What happened here? Here’s my best guess.

After spending several weeks of interviews telling them how interested he was in their startup, the founders were shocked to find that he wasn’t fully bought in and was still considering other companies. Moreover, going into the conversation, the founders were probably worried that this candidate was interviewing at FAANGs and other big companies and that there’s no way they’d be able to match big company compensation. It’s a real thing.

As such, they made the calculated decision to stop investing in this candidate because they’d be unlikely to close him.

As a former founder, I can relate to the visceral irritation that comes with feeling like someone is wasting your time. But as a former founder, this decision strikes me as naive – if a candidate is spending time with you, it’s on you to sell him, and you sell til the last minute! However, founders don’t always feel this way. Their time is limited and the opportunity cost of any time spent is very high. Moreover, as we discussed earlier, they’re not recruiters – they have less experience navigating these conversations, and for them it’s personal.

So how do you deal with founders? Here’s what we recommend. Incidentally, the advice below assumes that you’re OK with the cash hit you’d invariably take when working at a startup and that you’re going into it with your eyes open. If you’re not actually OK with it, please don’t waste founders’ time! And if you’re using small startups for interview practice, shame on you. Not only is it unethical, but the types of questions and feedback you’ll get will likely be non-indicative of what you’ll see at big companies.

When founders ask where else you’re interviewing, you can say that you’re excited about this company and that you’re talking to a mix of startups and big companies.

If they ask you about your comp expectations and/or if they push on the big company thing, and especially if you’ve previously worked at one, say up front that you understand startups can’t pay the same thing as FAANG, and that you’re sure that they’ll make you a fair offer.

If they give you a compensation range at the beginning of the process, take it seriously. Large company ranges are often fungible (we’ve seen FAANGs go $100k+ above their ranges with proper negotiation). Startup ranges are much less so, when it comes to cash. You may be able to negotiate a lot more equity, but if you don’t want equity, think seriously about whether you even want to continue with the process.

Replies leeny · 2025-02-23
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.