Skip to main content

So you got a couple of job offers, how do you negotiate from here?


I just interviewed a solid QA candidate.  She seemed qualified for a job and had the right experience.  It was no secret that she was interviewing in multiple places and got several offers because she deserved it.

We started putting together an offer on the upper end of where we felt that she would land.  The other company being a less exciting startup came in with an offer that was greater than ours because, frankly, they had to.

That is the awkward situation where the candidate has to call someone back and say: “I am getting a better package from another company, what can you do on your end?” The moment is awkward because we, engineers, generally are not used to going back and forth.  We have an answer and some data to back it up, the negotiation game makes everyone uncomfortable.

What happened next?  Next, we matched the offer.
Later on we got another call: the other company is beating this offer by $8,500.  The candidate said that she thought that we were a more exciting company to work for, but the eight grand made it a difficult choice.

At that point I made a decision that we are not going to enter a bidding war and said that the more interesting job was there for her, but the numbers are going to stay the same.  Internally we actually became a little indifferent to her accepting the offer and already started scheduling interviews with the other eight candidates we had in our pipeline.

Why did that happen? How can you handle it better in your own job search?  Number one thing to do is to understand what happens on the other end of the table.

After interviewing multiple people the hiring manager generally has one or two best candidates to move forward with.  While interviewing can happen in parallel with multiple folks, once you start the job offer you are operating serially.  You can’t have two outstanding job offers and have both of them accepted.

The hiring manager goes to HR and they get an approval to put together a package.  If the package exceeds the budget for a particular position you generally need to get an executive approval for expanded budget.  Exec approval takes time and follow-up.  If you need to do it several times over several things happen: first - you are going back for more money constantly, second – you start wondering if you are being taken advantage of.  Lastly you start wondering if you are getting a technology enthusiast or a professional negotiator.

I understand and fully support people getting what they deserve.  So what’s the best way to handle multiple offers?  My advice is to say this: “Hi, I want to let you know that I am getting multiple job offers.  I don’t want to go through several rounds of negotiations – you probably don’t either.  In the interest of making this easy on everyone could you please put together your highest and final offer? I am asking other companies to do the same.  By the way, the general range for a person with my experience and knowledge is: X to Y.”

This makes the exercise a blind auction, which is a better overall experience for people involved.

If you have a better strategy, let me know – feedback is welcome on twitter @mikebz and elsewhere.

2 comments

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…