February 26, 2007
Professionals Don't Just Say "Yes"As someone who's been in that position more than once, I've built up a knack for spotting those jobs where all they really want you to do as a consultant is provide "independent" vaidation of decisions that have already been made by the person hiring you.
Take this job advertisement for a .NET architect:
My major blue chip client is looking for an Architect/Lead Designer for a high profile contract position in Basingstoke (with occasional travel to Bracknell*). The successful candidate will act in an architect/lead designer for a systems integration project. The project is delivering a .NET solution for a service based integration of an existing Mainframe solution into a graphical user interface.
The candidate will be responsible for acting as lead design to a team of developers, defining the design & development standards, acting as the single point of contact for the customer and managing customer communication.
The candidate should have experience in SOA, iterative development, Web Services, .NET and C#; experience of Mainframe integration especially VME integration through HostTalk would be beneficial. The candidate should also have knowledge of various orchestration tools such as WebSphere and Biztalk and be able to offer advice and guidance to the customer in this area.
Now, I don't know about you, but it sounds like quite a lot of the high-level technical design decisions an architect might make have already been made by someone else.
I'm guessing that if I went for this role - thankfully I'm too busy - all they'd want me to do is come in, take a look and say "yes, that's how I would have done it". A doctor who let's the patients write their own prescriptions is arguably not a professional...
* Be still my beating heart!
Posted 14 years, 1 month ago on February 26, 2007