I thought about expanding my skills to include Project Management but a manager with my long-term client talked me out of it. He told me not to do it at least with them. The reason is that I am actually important and needed long-term but the main job of the Project Managers we use is to take the blame and get fired at the end. I thought back through the projects I have worked on and he had a very valid point. Only one PM that I have worked with is still around and that is just because he is unusually good and charismatic. The others never stood a chance.
I sure see a ton of job ads that have a long laundry list of very specific requirements, even for the “one man departments”. A lot more people are capable of doing these kinds of jobs than employers are willing to hire. It’s the employer’s loss, of course. But it ticks me off hearing about “skills shortages” when there are people like me out there applying but we don’t get the time of day.
A related peeve: I often hear hiring managers comment that something like 8 out of 10 candidates they try to hire fail the drug test. I don’t do drugs, so they wouldn’t have that problem with me. But again, I don’t even get a phone call because they’re too busy looking for that 100% matching skillset. They don’t seem to work their way down a list of potential candidates, but instead re-post the job to continue looking for that perfect match. Re-applying when they re-post doesn’t seem to work.
IT is too broad of a term without knowing what your skills are or what your interests are. Previous posters have listed the wide variety of IT work, but most won’t apply for someone just getting into the field. I think the term should be narrowed; what was the OP’s friend suggesting?
I teach at a community college where we have a computer science/programming program and a network administration program, with some overlapping classes. I wouldn’t label programmers as “IT workers” but graduates of network admin certainly are. “IT workers” configure systems, servers, set up networks, handle help desk operations, monitor security logs, that kind of stuff. IT work is “work” in that you’re often physically doing things, versus programming which is more desk-bound.
Another distinction is the hiring requirements. Employers looking at our network admin students usually ask for both the two-year degree PLUS certifications.
On the other hand, our programming students may get hired with a two-year degree, but most go on and obtain a four-year degree. I tell my graduates to apply for jobs that list a bachelor’s degree as a requirement even if they don’t have one. If they get past the HR screeners, they can talk through their skill set.
We don’t see programming job listings ask for certifications in programming, mostly because that’s harder to test, although Oracle has some certifications. Searching the Web for programming certifications hits some sites where some say programming certifications are actually detrimental on a resume; they only show you know how to pass a test. Better would be a GitHub open-source project or a published app that shows what you know what you say you know. Because of that, we don’t have our CS/programming students pursue certifications or any sort.
Yeah, I can see that. I took a contract PM job at a big, well hated, financial services company a few years back. The contract only lasted one year. And they actually liked me. I had a couple months notice before the contract ended. They took me out to a nice farewell lunch. Even bugged me to run on their Corporate Challenge race team (I had signed up prior to the contract ending). I still keep in touch with my VP and some of my colleagues.
The contractors they didn’t like or who didn’t work out typically had a message sent to their agency at the end of the day to not show up again and that they would receive their stuff in the mail.
I also later found out that on my PMO team of 5 PMs (3 full time, 2 contract), I was the only one who was actually working on a real project over the past year. The others were mostly doing “busy work” like putting together decks for monthly steering committee meetings.
Unfortunately, the nature of project management is that projects, by definition, are of finite duration.
Ironically, during that time, I also received a full time offer to go back to a firm I had previously worked at up in Boston. I ended up not taking it though. I had just worked for a startup and wasn’t sure if I could tolerate the firms similar “tech cult” mentality. Plus they seemed WAY too eager to hire me as a PM for some “important” client engagement. If it’s so important, why are you hiring some guy right off the street and not putting your A team on it? It just seemed desperate like I would be walking into a shit-show.
This, IMO, is what it should be, except it’s not a menial or lowly task - it requires serious skill and credibility to be able to manage stakeholders so that they accept and uphold their responsibilities.