Live data from Hacker News

Ask HN: Best practices for hiring software contractors?

news.ycombinator.com

21–30 of 46 posts

Re: Ask HN: Best practices for hiring software contractors?

#21
post #17

It depends a lot of you size and your project scale. But here are a few advices. Do not pay by day/hour if you can avoid it. Define small deliverables then objective tests to validate them and attach fixed price to each piece. You don't have to come up with it out of thin air, the contractor is supposed to do that with you. You don't have to define all of them up front neither. In fact, they will probably change duri…

Following this advice you will work with 0 competent developers. No developer of any worth will give you turn-key offer for a non-trivial project.

> No developer of any worth will give you turn-key offer for a non-trivial project.

Yes, I'm actually saying exactly that in:

> [a good contractor will] not give you answers right away, especially deadline and price. I can take several (sometimes billable) hours up to several days with a customer to understand the project and assess this.

Re: Ask HN: Best practices for hiring software contractors?

#22
post #16

Yegor Bugayenko (yegor256) gives the most direct advice I've ever seen about hiring remote programmers, generally remote teams. The advice could be scaled down a bit for an individual developer. The general thrust is to keep things incremental: demand access to source at all times, one click build processes, regular independent code audits, change the team regularly so no one becomes essential to the process, demand…

That depends of the scale of your project though. If you have $10k dollar, you may have to choose between the one click build process and some features or documentation. Regular audits and updating list of risks have a cost and affect the deadline. Change the team regularly ? Do you know the cost of introducing anyone new even to the best made project ? What if you are an individual ? What if you are a start up ? Wha…

[deleted]

Re: Ask HN: Best practices for hiring software contractors?

#26
post #17

Earlier quoted context omitted.

Following this advice you will work with 0 competent developers. No developer of any worth will give you turn-key offer for a non-trivial project.

> No developer of any worth will give you turn-key offer for a non-trivial project. Yes, I'm actually saying exactly that in: > [a good contractor will] not give you answers right away, especially deadline and price. I can take several (sometimes billable) hours up to several days with a customer to understand the project and assess this.

How do you persuade a good contractor to take the several days to assess the project if you seem like you want to avoid paying an hourly or daily rate?

Re: Ask HN: Best practices for hiring software contractors?

#27

Earlier quoted context omitted.

> No developer of any worth will give you turn-key offer for a non-trivial project. Yes, I'm actually saying exactly that in: > [a good contractor will] not give you answers right away, especially deadline and price. I can take several (sometimes billable) hours up to several days with a customer to understand the project and assess this.

How do you persuade a good contractor to take the several days to assess the project if you seem like you want to avoid paying an hourly or daily rate?

I usually spend an hour or two for free with the client, unless I feel they are not serious about it. If I assess studing the project will take more time, I give them a flat rate for it. It's my job to assess how long it will take, then use my daily rate to give the total.

I always include an escape clause in the contract in case they forgot to mention something very important that change drastically the price.

I also never quote the entire project, only the first deliverables. Then roll incrementally from that.

Most contractors around me are well paid, it's not a big deal to not be accurate at the begining. We adjust on the way.

Re: Ask HN: Best practices for hiring software contractors?

#28
Software or otherwise, the best way to find a good contractor is to get referrals from people who had a positive experience for similar work. That can be somewhere between hard and impossible though.

Failing that, and if you need to go out and just evaluate contractors you find through other means, the most qualified person for evaluating a contractor is another experienced contractor who is not competing for the work.

Hire somebody experienced, for a nominal but fair fee, to help you review your project plan and advise you through the sourcing process for its fulfillment. This is a different role than a recruiter, and in fact, be wary of anyone who wants to simply hand you off to someone they know without assessing other options. You want a personal advocate, not some contractor's sales agent.

Then, consider retaining them after the contract begins to double check the work as it proceeds, and to bring issues to your attention if things smell fishy.

Basically, if you are asking this question on HN and don't have access to a good referral, you're about to throw a huge bunch of money at a stranger that you don't know how to evaluate. Written guidelines won't be enough help. Because of your own inexperience, you're almost certain to either trust them too much, or distrust them too much, and either one is going to strain your project and cost you money and time.

Having an experienced advocate on your side, who has a different incentive structure than your contractor, can make all the difference. And unlike the implementing contractor that you'll eventually hire, you can successfully evaluate the advisor yourself. Their role is about communicating things to you, and advocating for you, and these are actions that you are totally qualified to judge. Plus, it's a smaller and more ad hoc role that doesn't have the sunk cost issues that you'll face with your implementation contractor. If you find that they're not doing a good job being your advisor and advocate, you can drop them without sending the project into crisis.

Besides myself, I don't know a lot of people who advertise this role directly, but I think many independent contractors would take it on if you pitched it to them. I think many working developers and development managers would too, as a side gig, although they may not know the norms and pitfalls of contracting quite as well. They'll at least be able to vet your project plan, review candidates for technical merit, and perform code reviews. Even just those tasks can make all the difference for you.

So long story short: before you hire a contractor, go poke around for a paid advisor who you think could help you hire one better. It's really worth it.

Re: Ask HN: Best practices for hiring software contractors?

#29
I'll leave the legal stuff to others. In terms of how to find good contractors the key - before you start looking - is to be clear about:

- what you want

- what you actually need

- the priorities within those lists

- what level of service / availablity

- your budget (and how realistic it is in the context of the previous points).

Most ppl new to such efforts - and even many of the experienced - have unicorn ideals in mind, and a fast food budget.

p.s. Also be ready and willing to sharpen your communications. Assuming they'll know all their is to know about your effort isn't going to get you far. Unless you're able to hire a mind reader ;)

Re: Ask HN: Best practices for hiring software contractors?

#30
post #16

Yegor Bugayenko (yegor256) gives the most direct advice I've ever seen about hiring remote programmers, generally remote teams. The advice could be scaled down a bit for an individual developer. The general thrust is to keep things incremental: demand access to source at all times, one click build processes, regular independent code audits, change the team regularly so no one becomes essential to the process, demand…

That depends of the scale of your project though. If you have $10k dollar, you may have to choose between the one click build process and some features or documentation. Regular audits and updating list of risks have a cost and affect the deadline. Change the team regularly ? Do you know the cost of introducing anyone new even to the best made project ? What if you are an individual ? What if you are a start up ? Wha…

Yegor has direct and extensive responses to each of your points, and many more. Not that he is always correct, but he never avoids the questions you raise, and is happy to engage in discussions. Since he himself ran a development shop in Ukraine for many years, he is pulling back the curtain and sharing tips to stabilize a difficult process, especially for non-technical customers. He even has his money where his mouth is, with patents and a startup implementing many of the principles he lays out in a scalable system called Zerocracy[0].

And just as a counterpoint to your $10k customer needing to choose between things, there are hundreds and hundreds of customers who lose every penny of their $10k and start over from scratch. (That is what is in the podcast episode, if you have yet to listen.) By imposing the extra process and expense at the beginning, the customer can guarantee some forward progress toward their goal instead of trusting the dev shop to deliver everything by the end in a big bang delivery.

[0] https://www.zerocracy.com/

Post reply on HN