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!

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…