Live data from Hacker News

Ask HN: First hire offered to work part-time – what should I do?

news.ycombinator.com

31–40 of 106 posts

Re: Ask HN: First hire offered to work part-time – what should I do?

#32
Controversial opinion but learned through experience the hard way here, repeatedly proven, anyone that you feel "like lack of commitment from him could possibly influence our culture in a negative way", just pass (at least until you have product market fit or a repeatable business running). As soon as shit hits the fan, they will either leave or drop performance, and you will have to let them go.

In your case, I think the issue is not about part time, but the commitment itself. If it's your first hire, you need them to be on-board, and contrary to what most people say, have more expectations than people would for a "normal" employee. The truth is, that person is not a normal employee, it's the first hire in a very early stage business. If you treat that hire as a regular employee, you will build expectations and won't be able to live up to it, and it will backfire for both of you 6-8 months down the road. That will hurt your ability to build a core team, and you will have to start from scratch.

Do not give up on that, no matter what the popular opinion tells you. Most people are not founders, and you should trust the guts that you have about building your core team.

Re: Ask HN: First hire offered to work part-time – what should I do?

#33
I can emphasize with you, as a first hire is always a tough decision. Having bad first hires can set a company back, make it harder to hire others in the future and be bad for moral (which makes it that much more important).

What an employee does outside of work should not matter in your decision (tons of people have side gigs, for example).

What should matter is the expectations and the output of the employee. If you feel that its important to have someone working full-time, in the office 5 days a week, then I think that's perfectly OK (in the same way that its OK if an organization cannot handle remote teams). This is a decision you would be making. If you wanted 5 days a week, that would disqualify this candidate (at least for now).

IMO (and experience), the lack of commitment is the `three days a week` instead of full-time.

Re: Ask HN: First hire offered to work part-time – what should I do?

#34
Hire for professionalism. You've been working on this for a long time. It means it's intrinsically interesting for you, and you've gained quite a lot of internalized intuitive understanding of the field.

It's very unlikely that you find someone who is intrinsically interested of the same things as you. Or has as deep intuitive understanding of all the business variables. But it does not mean he can't provide great value.

Id's say it's a red flag if you hire for "passion" instead of "professionalism". True professionals want to do a good job and ship on time. You don't need "passion" for that.

Re: Ask HN: First hire offered to work part-time – what should I do?

#35
post #26
post #10

Earlier quoted context omitted.

What do you all call the feeling around enjoying the work you do because of the mission and/or technical challenge and/or team? Or, the feeling of wanting to do high quality work wherever you are? Generally, I've never worried about that being called passion.

> Or, the feeling of wanting to do high quality work wherever you are? We have a word that literally translates as "professional pride." Now I'm not sure it has the right vibe in English, but it captures the idea that you do high quality work and you wouldn't do a sloppy job, even if the job sucks. For example, I would like such a plumber, because I know they will be careful not to make a mess, and they will clean up…

[deleted]

Re: Ask HN: First hire offered to work part-time – what should I do?

#36

He's hedging his bets because you are a very risky proposition. No employee is going to drink the Kool-Aid like the founders until the project proves itself. If it's going well, he'll come on full-time. If not, he doesn't have a hole in his resume and his bank account. If this person has the chops you need, do the deal and prove your worth by landing customers and investors.

This seems to be a lot of assumptions on what the "candidate" might feel like. TBH, We dont have enough information.

Why would the candidate hedge their bets on risky propositions by working part-time on TWO startups? Wouldn't it be more likely they need a side-gig (backup plan)?

Re: Ask HN: First hire offered to work part-time – what should I do?

#38
I would definitely hire them. I don't see it as a lack of commitment, rather he/she just understands the value of their time. 24 hours of labour is NOT 60% of a full work week, especially for a knowledge worker.

It's a big green flag from my perspective.

Re: Ask HN: First hire offered to work part-time – what should I do?

#39

Meh... In most cases, talking about "passion" in this context is just a roundabout way of saying "we want people to work harder for less compensation." Expecting founders to have "passion" is fine, since they (presumably) own equity stakes that will make them wealthy if the company is successful. But unless you're giving your early hires a large stake in the company, I'd suggest dropping the "passion" verbiage and tr…

> "If you're worried about them leaving too soon if their side project takes off, you can always try some "golden handcuffs" in the form of some perk that disappears if they leave before X months."

Seems to me the obvious choice here would be to give him equity that vests over time. Have it scale with how much he works. That rewards his "passion", if he has it or develops it over the course of the project, and it might tempt him to commit more. Vesting over time discourages him from leaving early.

Re: Ask HN: First hire offered to work part-time – what should I do?

#40
It sounds to me like you're uncertain about whether to hire this guy or not. It's my own personal rule to only hire people when I am 100% certain.

Now I could give you all sorts of reasons why this guy will be an excellent hire. My personal gut feeling is that some people deliver more value in 3 days than others deliver in 3 years, so "bum in seat time" can be misleading in terms of the contribution someone will make. Engineers with side projects are often more goal-focused, because they purge their need to over-engineer and try new things outside your core production project. You hire employees for their talent, not their passion. But these are _my_ gut feelings, not _yours_, and you need to pay attention to _your_ gut feelings when you make such a critical hire because it's _your_ startup. Presumably, your gut feelings are pretty good which is how you're in a position to be running a startup in the first place.

Over the next few months, you will inevitably have problems. Things will be harder and take longer than you think. Then you'll be saying "it's because they're not committed enough, I should have listened to my gut feeling when we hired them".

I would express my thoughts fully and transparently to this guy. Perhaps you can explore a middle-ground - here's some ideas:

1. More hours with more pay in the short-term to help you scaffold things, scaling back once you're up and running.

2. Work part-time as an engineer, still be available for operational stuff outside those hours (with pay).

3. Help you hire somebody else ASAP, so you don't need the original guy full time.

Post reply on HN