« Session Abstracts: Lotusphere vs ILUG | Main| Goofing Around »

What's Your Perfect Job? Perfect Employer?

I was thinking about this the other day and decided to write it down. I threw in some explanatory comments in case anyone wants to try and understand it, but mostly this one is intended for me.

I'm 41 years old (physically, that is - mentally, I might be 14 on a good day), so I've got roughly 20 years worth of experience in various positions at several different types of employers. I've worked for a college (and also a university), a manufacturing company, a consulting company, a tech support provider, and a major retailer. I've worked on level 1, 2, and 3 support at a help desk, been a network administrator, a Notes administrator and developer (many times), a technology-agnostic developer, an architect, a tech lead, and a department manager. Oh, and I've flipped burgers, too, but not since I was 18...

So when I look at jobs and employers, either the one I have now (at the legendary Acme, Inc) or potential ones I see posted or am asked to consider, do I use all of that experience to make sure I've found a good match? Well, not really. At least, not in any formal, structured way. Like most people, I ask questions and try to find out if the job is a good fit, but ultimately I tend to go with my gut reaction. And I think I should stop doing that, because sometimes it misleads me. So that's why I'm writing this down now, because I want to be able to refer back to it. It will change over time, of course - there are things on this list that I wouldn't have thought of 10 or even 5 years ago.

In no particular order, here are some of the factors that make a job a good or bad fit for me. There's not a job in the world that meets all of these requirements (well, I suppose I could start my own company and make all the rules myself), but if there are too many places where a job doesn't line up that should send up a warning flag.

The most important thing I want out of a job? In a word, it has to be challenging.

What do I want to do at work? I like Notes and Domino and various web technologies best, but I'm a geek - I like technology in general. I like solving problems and troubleshooting. I like designing systems from the ground up. I like writing. I don't necessarily *like* speaking in public, but I like the challenge of facing down one of my bigger fears, and I like the fact that I am (reportedly) pretty good at it. I like making decisions, in part because I don't like it when other people make bad decisions and leave me to deal with the consequences. I like helping people. I like finding ways to make people, processes, and systems more efficient. I like working with smart people, the smarter the better (I don't need to be the Alpha Geek on a team, though I often am).

What don't I want to do while I'm at work? I don't ever want to work phone support again (*shudder*). I don't want to be in pure maintenance/support mode as a developer, where I'm not allowed to build new things and spend all my time keeping old ones patched together. I don't like to be bored. I really don't like repetitive manual tasks (I do love to automate them, though), and I also don't like red tape and administrivia - which I consider to be a particularly pernicious form of repetitive manual task.

Technical Issues:
  • I want the ability to install tools on my computer without getting 23 approvals and having an official company representative install it for me...
  • Employees should be allowed, nay encouraged, to use open source software and freeware, not barred from it (grrrrrrr, recent pet peeve here).
  • Speaking of open source software, when I write something interesting that doesn't give the company a competitive advantage (or can't be sold), I should be able to release it as open source. It's good PR for the company, it gives us free testing and bug reports, and other developers will often improve on it and donate their improvements. Participation in the OSS community is *not* a bad thing...
  • I'd like control over what is and is not running on my computer (I know, what are the odds of THAT, right?)
  • The company should recognize that good hardware does make you more productive - multiple monitors, lots of RAM, fast processors and drives, etc.
  • It would be nice to have the ability to use Mac/Linux on my work computer (yes, Greyhawk, I am totally jealous that you convinced your boss to let you use a Mac! You rock, man!).
  • I need 24x7x365 access to email, whether Craicberry or iPhone or whatever device is more appropriate.
  • Everyone should have access to community tools (external Sametime servers and blogs and forums and newsgroups and ...).

Career Development:
  • Speaking at conferences and writing articles should not only be permitted, it should be strongly encouraged.
  • Blogging should be a given, not a violation of the rules or a "don't ask, don't tell" proposition.
  • Participation in IBM/Lotus partner programs - Business Partner or Design Partner or Global Customer Partnership Council - should be considered part of the job. Insert other primary vendor/partner relationships as appropriate.

Company Style/Work Environment:
  • People should be valued for who they are and what they do, rather than how they look or how well they play political games.
  • Dress codes are From Hell - and neckties are Evil (don't get me wrong, I have no issue with looking professional - I just firmly believe that I can do that without strangling myself); business casual is fine, but truly casual is preferred when not in "impress the client" mode, which really should be most of the time.
  • Offices are vastly preferred over cube farms, but that's almost impossible to find - the minimally acceptable alternative is a relatively quiet work area (I worked above a manufacturing floor once, and that'll never happen again).

Process and Controls:
  • I don't like working on systems that are subject to FDA regulation - been there, done that, was really annoyed by it.
  • I don't like SOX compliance - am there, doing that, pretty irritated about it (and yes, I realize that wouldn't leave many companies to choose from, but then this is a wish list, after all).
  • I don't like PCI compliance - am there, doing that, moderately irritated about it.
  • On the other hand, (and I'm on record as saying so, forcefully) I absolutely do not approve of people who let their developers loose on production servers - I *like* controls, I just want them to be appropriate to the risk and not one-size-fits-all.

Benefits/Compensation:
  • Look, we all like to get paid, but it's not the only thing that matters. Salary goes together with atmosphere, commute/travel, flexibility, and family-friendliness to me. It's the whole work/life balance issue, and money can't buy you sanity. Enough money can compensate for issues in other areas (though eventually that wears out, I've found); great situations in other areas make smaller salaries more reasonable.
  • Three weeks vacation should be the minimum starting point, preferably four for experienced professionals.
  • Attendance at Lotusphere is mandatory, whether I'm speaking at the conference or not. If there is no budget to pay for it, I can do that myself (and have done so, 3 or 4 times), but under no circumstances should it be considered vacation time.


Now that I've written all of that down and posted it here, I'm curious how other people would answer the same question. If you got this far, what describes or defines your perfect job/employer? Are you in that job right now? If not, do you look for it actively or do you wait until you're forced into action (could be reaching a particular level of frustration, could be economics, could be major life changes)?

Oh, and especially for those who know me particularly well, what did I forget to include?

Comments

1 - Great writeup, Rob.

Not sure if this is an expansion to the points you covered or a summarization, but it seems that the managers I've respected the most (whether they're managing projects, people, or both) are skilled obstacle hunters; they seek out and destroy anything getting in the way of the successful completion of my duties. It might be "busywork" that at some point seemed like a good idea but has since proven to be a distraction from more worthwhile activities. It could be an element of the work environment that's lowering morale and stifling motivation. Upon occasion, it might be a shortcoming in my own work habits that, with a bit of constructive guidance, can by its elimination enhance not only my productivity but also my pride in my work and satisfaction in my career. It seems to be a rare skill, but I've already been fortunate enough to work for several folks who are outstanding in that capacity.

2 - Yesssss! Excellent point, Tim. I definitely should include some characteristics of the good (and bad) management approaches I've run into.

I like your "obstacle hunter" description. I've informally called that "keeping stuff out of my way," and the stuff in question can be almost anything - and it's a very important skill for a manager (I wish I was better at it myself, as the manager of my team).

I also like my managers to have enough of a technical background that they can understand me when I describe an issue or a solution. I can explain myself well enough so that anyone can follow along, but it's nice to be on the same page with your manager without have to do the translation into "normal" terms.

When I revise this in a while, I'll add in these two points and see what else I can come up with that relates to the management area.

3 - I think you're right on the money. I was in my perfect job for about two years, during the middle of my tenure at my last company. It took me three years to finally get them to understand what I needed to be productive, and while I had that I was off the charts. Then they took all all that away, my job satisfaction evaporated, and ultimately I left.

I would have to say if there is one thing I would give up pretty much everything else for, it's an office. I can't work in a noisy environment, and that includes wearing headphones. A door I can close would be a blessing... as long as I'm not next to Loud Howard. Emoticon

4 - @2 - A technical background can be a double-edged sword: if your boss thinks they know more than they actually do, that can quickly translate into micro-management... and few obstacles slow a geek down more than a boss standing over their shoulder all day. But you're absolutely right: if they get the underlying concepts enough to support you - understanding why you're recommending a given strategy, for example - that can unleash you to be more successful, make them more successful, and provide maximum value to your customers (internal or otherwise). Everybody wins.

That's one of the many ways I'm so spoiled in my current position. My boss is a heck of a developer, so he understands what we need from him to be effective, but can also recognize our individual areas of particular expertise and can more easily shuffle us around to make sure he's throwing the best resource at each task. But we each also have the luxury of access to peers that are better than us in areas where we want to grow, and can occasionally lean on them to get up to speed. Pretty ideal, really.

Okay, I'll stop gushing now. Emoticon

5 - "Blogging should be a given, not a violation of the rules or a "don't ask, don't tell" proposition."

It's almost a requirement here, y'know. Emoticon

6 - @Charles: Yeah, I had an office for a few years, and it makes a HUGE difference. That's one that's worth fighting for if there's any chance at all.

@Tim: Dude! Your boss is reading your comments, isn't he? LOL. Seriously, sounds like you might be in your "perfect job" right now.

I get the potential for micro-management, but I've found that even bosses who lean in that direction pretty quickly realize that you don't need that level of supervision. Technical bosses want to make sure you aren't making terrible (or non-strategic, anyway) decisions, but I've never had any trouble demonstrating that they don't need to worry about me. Maybe I've never had a real micro-manager, though, so I could have been pretty lucky there.

@Nathan: You could make a decent case that it should be mandatory, given your industry. If I was your GM, I'd be really tempted to carve out a block of time (20 minutes a day? 1.5-2 hours per week?) and have you guys create blog posts then. Is there a better type of marketing and PR out there? Have your people write, speak, and blog, and by doing that you show that you have the best people in the field on your staff.

7 - @Rob - I really think I am. I hopped around for a while, and started to think that my standards were just unrealistic and would eventually have to resign myself to pick something and just stay there. But then I found this position. If I had to dig deep for a criticism, it's that I travel more than I'd like... but even the travel has some enjoyable elements. Barring some drastic unforeseen change, this'll be my last job.

8 - Rob, great post. Good points all around. Picking up on Tim's point about obstacle hunting, one of my big complaints has for years been a lack of administrative support at any of my employers/clients. Hire a team secretary/admin assistant/intern/whatever to handle supply ordering, travel arrangements, photocopying, faxing, expense report preparation, filling out all those stupid forms no one has asked us to automate yet, etc. , please!

I realize that technology has allowed these tasks to be carried out more efficiently and simply but they still take time and for developers in particular, who are often trying to stay "in the zone" creatively, are a massive productivity killer. Considering that senior IT folk often earn as much or more than their own managers, it only makes sense that they be given similar cosideration with respect to admin support. And it wouldn't take much in the way of productivity gain per person to offset the cost.

9 - @Tim - Yeah, travel can be an issue, no doubt. It depends on how often, how far, and how long the trips are, but being away from the family is always a negative factor to me. Life's good when you're in that perfect job, though, so make sure you enjoy it! I've been there twice, for roughly 5 years out of 20.

@Kevin - I hadn't thought of those particular items, but there are a lot of ways that senior technical people are not treated as well as equivalent (cost-wise) management types. This seems like the discussion about offices vs cubicles again, in a sense. It boils down to a question of whether senior technical people are valued as highly as managers of equivalent salaries, and the answer is usually an emphatic, "No." Managers start to get offices when they get senior, but geeks rarely do. Why? I don't know. I definitely rate an employer more highly if they recognize that senior technical people should be treated well, and when that includes an office I take that sort of claim very seriously.

10 - I'd take nothing away from your set if points and values, but I would add a few;
- an potential employer needs to show that they have a set of values, publishes them, is proud of them, and sticks to them. That shows you that they have something that they stand for, and even if there are items in them that you don't necessarily like, you have had fair warning. That set of values should also define to you how the company will react to a given situation, and shows that they care about not just what they do, but how they go about doing it.
-

11 - I'd take nothing away from your set if points and values, but I would add a couple. <br />- an potential employer needs to show that they have a set of values, publishes them, is proud of them, and sticks to them. That shows you that they have something that they stand for, and even if there are items in them that you don't necessarily like, you have had fair warning. That set of values should also define to you how the company will react to a given situation, and shows that they care about not just what they do, but how they go about doing it. <br />- The reward process should differentiate between what you have done, and what your potential and willingness to contribute is. The former should be rewarded with one-off bonuses, and the latter by promotions (to posts you want to fill, not to ones you don't) and salary increases.
Lastly, the company needs to have a philosophy and grading structure (if it has that at all) that does not force you into management as a way of moving you up a career ladder. Management is for some poeople a legitimate career goal, but it needs to recognise that many technical people want to progress in their chosen path. After all, management itself is actually just another technical skill.

12 - Found this related piece in Computerworld folks might find interesting:

8 Signs It's Time to Look for a New Job
{ Link }

13 - I think your list is good, but I also think any list like this should have a "what I am bringing to the organization" section. Having a wishlist is great, but you need to counter it with what you are giving back. I have seen many developers put together a wish list, and then expect to walk in around 9:30, take a long lunch, and leave right at 5.

Your list does scream of corporate employee though .. vs true consultant. Emoticon Not saying that is bad, just my impression.

14 - Trust. I've attended Lotusphere on my own dime several times. One experience was while an FTE with just enough PTO (Paid Time Off) to cover the week. They would not pay for my time because I might later claim reimbursement for all expenses. An employee is willing to invest several thousand dollars in education, and asks for a matching contribution form the employer. What does the employers see? Opportunity? No. They see Risk.

15 - And to answer the question. My perfect employer would be a startup building a product. No more than 10 employees. Hired on a handshake and a personal check. My boss would be the product manger and between the two of us, most decisions about requirements and implementation could be made in minutes. Add one sys-admin, the CEO and the sales guy. Forward velocity. Everything on the line. Those were the days.

16 - @Mick: Good points, an employer's ethics, career development philosophy, and compensation strategy are all key elements. Sometimes you can't find out those details until you're already working there, but a little creative research can help out a lot (Friends of friends or LinkedIn contacts who used to work there).

@Kevin: Nice article, thanks for the link. I also saw this today, which might be useful to some people:

{ Link }

Lifehacker is talking about the compensation issues, based on a Deloitte survey that shows technical employees are less impressed with pure monetary rewards than they are with more creative avenues. I think this post reflects a similar opinion on my part, and it doesn't really surprise me that I'm not alone on that question.

@John: I'm not sure what "direction" (for lack of a better term, sorry) you meant your "scream of corporate employee vs true consultant" to point. Did you mean that the things I've identified are mostly relevant to corporate employees? That would make sense, since I've only spent 1 1/2 years out of 20 working as a consultant - I've mostly worked for a corporation (or college). Or did you mean that, based on those items, you think I should be a corporate employee rather than a consultant?

By the way, I don't agree with the idea that *this* document should identify the value that I provide as an employee, though I can definitely see the point of having a document that does that. If I wrote something like this to try and sell myself, I would definitely want to include that sort of information. But the purpose of this document isn't to claim that I am the perfect employee, it is to help quantify what makes a perfect job or employer for me. It's the opposite orientation. Useful information to provide to a potential employer, sure. But not useful to me in evaluating possible opportunities.

I think this may be a case of the difference between our respective reasons for blogging, ultimately. Your blog represents your firm, to a large degree. Mine represents me, and has nothing to do with my company. If that changed, particularly if I was an independent contractor or consultant who might get business offers based on my blogging, I would never post a work environment or job wish list without also countering with the value proposition for hiring me.

@Dan: Yes, having employers who don't trust you is very disheartening. Risk, indeed. That's sad, isn't it?

Ironically, your next comment about your perfect job would represent more risk than I'd want to take on at this point in my life. I'm relatively risk-averse, which is why I've never jumped off and become an independent contractor or started my own company. I like a regular paycheck, and I like a stable company. Small startups usually have issues with those two areas. heh. Of course, as you say, the environment is going to be very stimulating, and the BS will be at a bare minimum.

17 - Well said Cuz!
I don't think i could have put it better myself, although i would have probably used much fouler language when referring to those automations of disgust SOX auditors... YES i know they are only doing the job.. but *$%^&^%!

Go mbeadh bhad gloine fút agus go mbrise an ghloine! Feisigh do thoin fein!

I do apologise to any irish speakers but they really do skunder my pish Emoticon

However if you are feeling glum. have a listen to { Link }
they are way to young, way to talented but they make a joyus noise and this one is about working to hard in an un-fulfilling job

Steve

18 - I'd like to work with professionals, not high school students.

Rob, in case you weren't aware, I quit my job last week (check my blog). I'm not sure where the next car payment is coming from, but, I may end up living in it.

Anyone looking for SAP Basis folks?

Thanks.

19 - One evening at a company party, they recorded the following video, for fun, on a single take. It wasn’t intended to be a recruitment video; it just turned out that way. Note, it takes about 40 seconds or more to get grooving and some of the words in a song you will hear are mature.

James
Alcohol Rehab and Treatment Centers

<a href="{ Link } Recovery North Carolina</a>

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::rolleyes:;-)

Captain Who?

Captain Oblivious is Rob McDonagh's blogging alias. So there. Want to know more?
Read on...

Posterous

Links