Skip to main content

Career 101: Dunk, layup or dribble out of bounds?

Saw this on Whisper:


The way I see it, this dude has 3 options:
  • Reject the $55K increase and stick with his old job that he loves (dribble out of bounds)
  • Take the $170K to his current boss and negotiate for a raise (layup)
  • Take the $170K job, stick with it for a year and then bounce (dunk)
The first option is what I call a poor person's advice. It sounds very noble...very "get a job you love and you'll never work". Well I am here to say that's bullshit (mostly). This is business; you should always get the most you can. Besides, this is a chance for this dude to change his baseline salary for future jobs. At his current job, getting that $55K will take several years because corporate America isn't going to offer you more than a token raise each year.

My advice would be to take the $170K offer to his current manager and get him/her to match it or raise his current salary. That's the layup option. It's not too money-hungry and doesn't summarily leave $55K (almost 50% his current pay) on the table. Worst case, he'll be fired and fall back on the $170K offer. Best and unlikely case, they'll match the $170K. Most likely, he'll be offered a raise to stay because the cost of replacement is not $0.

The last option isn't too bad either. He takes the $170K boring job, spends a year there and uses the downtime to burnish his resume (certifications, conferences etc). At the end of a year, he leaves for a better job...that could even be his old job (boomerangs are not unheard of). With this approach, he banks that $55K and doesn't have to burn any bridge doing so. If a manager looks you in the face and tells you to ignore a 48% offer from another company, he's not giving you good career advice. 

What would you do? Dunk, layup or dribble out of bounds?

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…