Category Archives: interviewing

The Funny Things Candidates Send Us

JobMob has a post up with a list of funny things candidates send to recruiters (hint: if you’re formatting your resume like a Playboy centerfold “fact sheet” – and you list “intelligent people” as your biggest turn-on, spell intelligent right). It’s a pretty fun read, and eye-opening. Some of those tactics actually worked.

Granted – many of them don’t. I generally recommend you only go all-in if you’ve got a good, relevant reason to do so (for instance, I’m sure Playboy’s seen the centerfold-resume schtick before, and are probably okay with it, but Bank of America might not think it’s as… appropriate). Also, be careful what you send – boob cupcakes (sense a theme here?) can, and did, misfire.

In my time, I’ve gotten a few fun ones: giant novelty aspirin; Target flip-flops; a vinyl copy of Stand! by Sly and the Family Stone; a copy of The 21 Balloons; money (seriously – well, not “real” money, just a book of McDonald’s coupons – which showed lack of research, as I’m not a fan of the golden arches). Actually, the only one that got the candidate an interview was the giant aspirin, and that’s because it was a prop in a nifty marketing campaign from the candidate. Who I’m still in contact with, because he’s clever and interesting.

I’m curious – if you’re a recruiter, what sort of weird/ greatness have you gotten? If you’re a candidate, ever tried this approach? Succeed? Fail? Would you do it again?

Tagged , , , , , , ,

Salary Negotiations – Getting Untethered

Had an interesting experience a few weeks ago, around compensation and salary.

One of my clients, who I do a placement or two a year with (so, not my bread & butter, but consistent, and I like them), liked one of my candidates. One thing they look for is information on salary history. I’m ambivalent about this, personally. There are way too many variables (start-ups pay very little, hedge funds overpay, women and minorities are often discriminated against, the candidate may/ probably will lie, etc etc). Still, they’re the client, and I go along up to a point.

All that said, this candidate refused to play. When I pressed him for some comp info, he said flat-out “what they pay for the role they have, should be based on the work that _needs_ to be done, not the work I have _already_ done. As long as the quality of my prior work is sound, they should make me a fair offer based on that, and go from there.” Even when I went for a “Fine, I get that – at what point should they walk away from making an offer? When to I tell them they’d be insulting you? What’s your bottom, bottom line?”, he refused to budge. Wanted to see what they had to say.

So: bravo. I love it. He must be underpaid, and he’s trying to change that. This is a negotiation technique, that if you’re feeling confident that you can get an offer, is a decent approach. It takes some stones, and the ability to miss an opportunity if they don’t blink, but it can keep you from getting “tethered” if you’re underpaid at your current employer.

By tethered, I mean you get tied to a salary and can’t get much more than that. IE, you’re making $85k, and you know that’s low. You tell your prospective employer this. You don’t know it, but they can go as high as $110k for this role. But, by telling them $85k, they’re going to come in as close to this number as they can when they make the offer. They’ll factor in a bump, generally, and some might say “I want him/ her to come in excited, so we’ll make it a nice bump”, but don’t expect – at best – more than 10%, or $94k. They may even come in much lower, around $90k, with the expectation they’ll have to go up to $94k. You’re tethered to that $85k.

By not giving a number, if they want you, they have to assume the worst: that you were making close to their cap of $110k, and they have to come in around there to get you. They may still come in low, but you’re room to negotiate isn’t tied to your current salary. It’s tied to their imagination, and that’s what you want.

So. The faux pas. After all this, the client came back and said $105k”. They thought it was fair, based on the work they needed done, it was a par with the rest of the team who were doing similar work, and they’d bought some salary surveys and they were slightly above the regional average as it was.

His response? “But… that’s less than I’m making now”. I’ll admit, I almost screamed at him right then.

The take-away, for me, is know what your work is worth. If you’re making more than most, don’t hide that all the way through. You may want to soft-peddle it a bit, or wait til later in the process, because it can scare some people off, but don’t hide it completely – you’ll shoot yourself in the foot. On the reverse, if you’re woefully underpaid, know you can get more, and go for it, you might try asking to get paid what they think you’re worth, not what somebody else thought about you.

Tagged , , , , , , , , , ,

You Won’t Get the Job That Way

…here are some great tips by Renita Benjamin on the fundamentals of an interview. Still amazed that people don’t follow these basic rules…

What I’m Looking for in a Software Engineering Candidate

We’re doing some hiring in our engineering group.  Incredibly cool stuff happening here: complete rebuild of our our core platform, live apps, UI.  Re-architecting it all in Java (we’ve been a C#/.Net & C++ shop until now).  Taking our UI, and making it hugely interactive, yet elegantly simple.  Developing new metaphors for search.  And, more that we’re not public with yet.

We’re going to need software engineers with chops in Java for both our Core platform (semantic, AI, rocket-science type stuff), and Web Dev team (that beautiful UI I mentioned, plus major changes to our apps, and more to come). Lots of interesting problems, in other words.

It’s kind of like building the technology for a start-up, front to back, but at a place that’s already profitable, and has 5 million unique visitors per month (instant eyes-on your work – cool!)

We want you to come help us figure it out.

So, this is an opportunity.  A hell of an opportunity.  Let me repeat: an absolute (cover your kids eyes) mutha-fuckah of an opportunity.  Every software engineer in & around Boston should be clawing their way to get in here.  And, we’re getting some traction around that.

But here’s the thing: we want the best.  I figure it’s fair: best software engineering opportunity in Boston, possibly one of the best in the country, deserves the best software engineers.

No more or this “contributed to”, “supported”, “implemented” crap on your resumes.  I want you to brag.  Say “Architected & built from the ground up”.  “Led team to glory”.  “Researched and championed the use of [insert name of esoteric but cool technology here], which led to rapid scaling of…”

You get the idea.  Be amazing.  Don’t be some also ran, mostly worked as a consultant, never showed initiative.  Stun us.  We’ll give you work to do that you’ll thrive on.

I mean, think about it: this has been a Microsoft shop, and now we’re free.  But, the team’s light on Java – you’ll be the man/woman.  Major resource, cool cat, all of it.  Get yer ass over here, before somebody else does.

Blogged with the Flock Browser
Tagged , , , , , , , , ,
Follow

Get every new post delivered to your Inbox.

Join 2,539 other followers

%d bloggers like this: