Starting to Say 'No'

Today I made a breakthrough; I said no to an opportunity that seemed ok, but not excellent for me. The result was pretty liberating. I'm looking for a very specific type of job, and this one wasn't it, so I passed. I know sometimes people say if you don't answer when opportunity knocks, you are signaling that you do not want opportunity. I disagree wholeheartedly, and here's why.

Reason 1 – The right fit is based on a score

If I were to take on this engagement, initially there would be a lot of work just to ensure that my CV would get me in the door. Too much work and potential bending of the truth to get me in. Not the way I want to start a gig. I would rather chat with someone about the job, have them agree that I'm a fit, and then sign me up. Even if I don't have all the technical skills.

Reason 2 – I'm not sure that the job is a fit for me

Many opportunities that pop up have a title that is appealing, and technical in nature, but they often end up being more paper-focused. I'm currently looking to get as technical as I can. Therefore, although this job is something I could do, and the money is great, history dictates I would be miserable after a short period of time.

Reason 3 – It's a contract gig, and I'm going to be a dad

I've currently got some other irons in the fire, and I'm hoping that they pan out. They are for full-time gigs rather than contract opportunities, which I believe is more of what I need right now. I'm going to be a dad this year, and I will require time off, preferably with pay. I'll also need a flexible environment that is results-based versus butt-in-seat-based.

Anyways, it's not like I needed to justify the decision, but I figured I'd jot down my reasoning to maybe help anyone who's in the same boat. If anyone reads this blog someday, maybe they'll find what they need!