4 ms·
"audition style may work if you're a consultant trying to convince a client to hire them" That's one of the main reasons I'm self employed. Getting a job is m
by k__ 9y ago
"audition style may work if you're a consultant trying to convince a client to hire them"
That's one of the main reasons I'm self employed.
Getting a job is mostly doing dumb interviews, tests and crap.
Getting a project is mostly telling the client that I can do it for an amount of money they find okay.
- chatmasta 9y agoAs a consultant you are much more in control of your working relationships than as an employee. A consultant has many clients; an employee only has one employer. That alone provides sufficient leverage to dictate the terms of the role, which is a major advantage of self-employment.
- jaggederest 9y agoI think it's basically the same deal PG is always talking about: Nobody is willing to pay triple for an employee which is actually three times as productive, but a consultant can honestly charge three to five times as much in order to provide equivalent return on investment. I also find that in general, people who won't listen to an employee are excited about collaborating with a consultant - even when you're the same person making the same contributions. I find it pretty frustrating - I have long-term views and I want to make a significant, long term impact on the companies I work for, and being a consultant means it's all about quarterly results. That being said, I'll take sober consideration from day one over "time over grade equals seriousness" any day.
- kelvin0 9y agoTotally agree, as a veteran Software Dev, been consulting for 2 years now. Most customers want some degree of assurance that you can solve their problem and that you also have a track record of proven success (no FizzBuzz BS). The downside is that most customers are also non-technical, so it becomes challenging (for me at least) to explain some concepts which impact the ongoing project. This is where I think building trust within a business relationship is important, and why you should avoid any customers who distrust you and your credentials. Because the bottom line is : if you can't explain all the finer details to someone, but they trust your judgement and ability, everything else becomes much easier.
- scarface74 9y agoTrue early on in your career or you’re interviewing for large company, you have to go through the crap. I avoid large companies like the plague. At some point in your career, your resume can start speaking for you and your salary requirements are going to automatically start filtering out positions where they are going to ask “what’s the difference between a class and an object?” and start asking questions about previous projects, how you architected them, etc. One company I worked for, I came in expecting the standard questions but the first question I was asked was what was my 90 day plan to create a modern development department - I didn’t know he was looking for a team lead. Another, they were using AWS but none of the developers knew how to take advantage of AWS services fully.