Tuesday, December 21, 2010

travel required

So my company recently opened up some new positions for 2011. I won't go into too much detail about them, though. Speaking of that — I don't know if you noticed, but I don't like to talk about work-specifics on my blog. Those of you who know where I work might understand why, but honestly it really wouldn't be that big of a deal. Still, I'd rather be safe, than sorry. Anyways, back to the position. It's interesting and a completely different position than software engineering. The catch? Well there's two actually: one, I'm not quite qualified (d'oh), and two, it requires the ability to travel up to 50% of the time.

The reason I'm not quite "qualified" is that the lowest engineering position they opened up is still higher than my current position, which I just got promoted to last year. By their standards, I probably don't have adequate experience. And as for the travel thing... I'm undecided honestly. The position will include some great experience for me, so having to travel frequently would simply be a trade-off for that. Also, there is probably no better time in my life to have this kind of position than now. As you get older, the ability to travel as part of your job becomes harder. That isn't to say it wouldn't be hard now, since I'm in a relationship, have a dog, etc. It would be easier now than later, though.

Whoa, whoa. I'm getting ahead of myself. I'm going to apply, but the likelihood of landing this job is pretty low because of the aforementioned experience qualifications, and that there are only a handful of positions opening up (and we have a lot of engineers in our company).

I won't be disappointed if I don't get the job, but I might be disappointed giving up a potentially good opportunity without even trying.

No comments:

Post a Comment