Comment by econ

Ive quite often thought job descriptions should describe absolutely everything they do, should do and have done.

I've had the joy of being the company glue quite a few times. I simply ask myself if everything needed by everyone is actually there.

Then one day I learn how invisible this work is. I had a funny conversation aimed to get paid for my official job description that in stead resulted in demotion. I told them fine, from now on i'll do precisely what I'm hired for and nothing else.

Then I watched everything descend into a chaos much worse than I could have imagined. Everyone blamed everyone else and no one got along. People even got fired.

One dumb example out of many. If you look which new employees, clients and contractors will visit today after noticing no one is at the gate you can let them in. Then they want coffee and then they want the things needed to do their job. If those things are repeatedly not there they do crappy work (if any) and have a terrible mood. Its just one example, already takes way to many words to explain while the actual instances are far more hilarious than described.

Just put it in the job description. Clients don't spawn at your desk but you wait for them at the gate, you arrange a parking spot, you make sure the coffee (that should be there) is actually there.

Then when you install chargers update the text to give them a spot to charge and update their profile with their type of car and if they want milk and sugar.

It sounds preposterous but if you do it like that you can consider putting someone at the gate.

If it is in the job description and you measure great performance you can put the pair programmer on a different team that needs him.