|
Introduction
As a CodeProject reader you are continually on the forefront of the latest technology and software development information. Are your long-term career goals on the
technology forefront, too? Are you prepared for all the twists and turns your
employers and co-workers will put you through?
Career 2.0 is a series that will share success tips, tricks and
strategies to help you upgrade your career. Catherine Burk and Andi Levin are
experienced career guides and senior technical recruiters who will offer in-depth concrete steps
and proven career strategies to help you reach your career milestones:
- There
are job opportunities today, but employers draw candidates from a larger
and stronger pool than in recent years.
How can you prevent losing out on your dream job, and not think
"I e-mailed company X my
resume for a job I’m 100% qualified for, but it went into a black hole?
- What
strategies and skills do you need to receive a job offer that you want
today?
- Which skills must you add to, or
improve, in order to ensure long-term career growth and future job
opportunities?
- Are you currently able to identify
and resolve workplace conflicts from company financial and organizational
health issues; office politics; individual personalities, and with
management?
You solve technical
challenges through a series of logical steps or other contacts here on the
boards. You define the problem, analyze
business needs, then consider and test multiple possibilities to create the
best solution. And, no matter how
successful the first release is, you always evaluate that solution to develop
improvements for V.2
Conducting a successful
career search and utilizing on-the-job strategies for career advancement
follows this same framework. We will
cover each of these sections in depth in future articles.
Step
One: Lay the foundation.
Program
in terms of the problem - what problem do you want to solve? What is your goal?
Where does your job search process fall in the black hole? Do you ever hear back from a live person
once you’ve emailed your resume? If so,
what are the results of your interview(s)?
Do you receive a job offer from the company? If you received a job offer
that you did not accept, how should you fine tune your search model to better
target your efforts to receive offers that you will accept?
Step Two: Requirements Gathering
What job responsibilities are you looking
for? Do your experiences and existing
skills match the requirements for this type of job? If not, what will it take for you to meet those
requirements? What best describes your
“employer of choice?”
Who is the best person at the company to
approach? What is the best way to
approach that person? Do your interview
skills reflect your professional experience and abilities? What is the company’s hiring bar? How can you improve your skills to exceed
that bar?
Step
Three: Construct a Successful Routine.
Knowing what
solution you seek; now you determine which job search skills to obtain or to
polish:
- Do you have strong professional
networking skills in order to hear about potential or currently open
jobs?
- Are hiring managers actually seeing
your resume?
- Does your current resume generate
interviews?
- Do your interview strategies result
in offers?
Step
Four: Test and Fine-tune Routine.
Debug as appropriate. Repeat as necessary
through offer receipt and acceptance.
Step
Five: Evaluate Solution for Future
Improvements.
There will always
be ongoing skill and performance improvements as you grow in your new job; when
you seek new job opportunities within your company; or when you begin a job
search with another company.
Now
– how do you get there from here (wherever here is)?
Job opportunities
are out there, even in today’s market.
Where are the bugs in your job search process?
Problem:
Resume and application go into a
black hole; you are not contacted to interview for the job.
|
Routines to
check
|
Optimization or
Workaround:
|
- Do you meet all of the required
skills and experience for the jobs you applied for?
|
To succeed in today’s job market; target your
efforts to companies with open jobs that match exactly your skills and
experience. With a lot of good people
in the job market, companies are holding out for exact candidate matches.
Apply for your dream job if you find it posted, even if you do not meet all
the requirements, but focus your efforts on obtainable goals.
|
- Are you applying to local
companies, or would the company need to relocate you to the job?
- Would you require international
relocation for this employer and job?
- Will you need visa sponsorship if
hired for this job?
|
In today’s market, many companies only consider
relocating candidates for very senior jobs, or jobs with complex or unique
skill sets. Companies are very selective when international relocation is
involved – it is expensive and visa requirements can be tough to meet. Be sure you can qualify for a work visa
for the location and job you apply.
|
- Do you list your experience and
skills on your resume in a clear and easy to understand way?
|
Many company recruiters are not that technical, and search for key words which
match their open jobs.
You may need to customize your resume for a particular
job and company.
To do this, use the job requirements as your
résumé’s framework. Today many
companies hire candidates they perceive as making a lateral job move or even
a step back – your next job may be a promotion, but are you prepared to bet
your house you will land a job that is a step up?
|
- Are hiring managers seeing your
resume?
|
If you apply through the company website, you
usually are one of many people. There
is a very good chance the hiring manager did not see your resume.
To solve, CC: the middleman (i.e., corporate human
resources), but submit your resume, either directly or indirectly, to the hiring
manager.
|
- What format is your resume in?
|
For now, a good general rule
is do not submit your resume in .pdf format – not all resume tracking apps
read .pdf files – so this could limit the number of recruiters and hiring
managers who will retrieve your resume using a SQL query. Not good!
|
Next...
Our next column focuses on
tips to help ensure your resume is read by the hiring manager.
Now, it’s your turn.
This is your column; please e-mail us with career and job-search
questions or post your comments or discussion ideas here. We can help.
| You must Sign In to use this message board. |
|
| | Msgs 1 to 21 of 21 (Total in Forum: 21) (Refresh) | FirstPrevNext |
|
|
 |
|
|
The real problem in the software industry today, is that many human resources departments have not evolved from personal departments, they have only glorified the name.
We often see the wrong people getting the best jobs.
This is the failure of the HR departments, not the failure of the candidates.
Look at the heading "Career 2.0 is a series that will share success tips, tricks and strategies to help you upgrade your career."
The HR deptartment wants people to either decieve them or to play their little office political games, they are not out to find the best person suited to a particular position !
Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Yep... That explains some additions to my workplace.
Alberto Gattegno Software Engineer http://www.itgil.com
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
I spent some time dealing with them, it's really funny. People who barely know what a computer is working through checklists and asking what your skills are. Interviews with people with whom you are mutually incompatible. Jobs that are yours until the employer gets a chance to hire someone who is not through an agency and can save himself a fee.
In contrast I have interviewed for three jobs I sourced myself, one interview they failed and the other two jobs I got.
Christian
Hey, at least Logo had, at it's inception, a mechanical turtle. VB has always lacked even that... - Shog9 04-09-2002
During last 10 years, with invention of VB and similar programming environments, every ill-educated moron became able to develop software. - Alex E. - 12-Sept-2002
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
My tactic (because I can afford to) is to interview the company (even if they think they are interviewing me), and in the process, they learn a lot about me based on the questions that I have and the ensuing conversations. I find this technique works a lot better, because I gain control of the interview and can cull the companies that I don't want to work for (but used to discover that fact after 2-3 months!)
Most interviewers to this day don't know how to conduct an interview. Take advantage of that fact. The rest seem to rely on technically oriented tests. Study up. Work with a recruiter that knows the company, even if you're applying direct. Many will be happy to work with you because they may get someone on the "inside" simply by sharing some information.
Marc
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Got to agree with Marc here.
I find that if I approach it from "Why should I work for you" angle, I do better in the interviews. After all, this is a place I'm going to spend most of my waking hours.
Again because my CV is pretty impressive, I can use this kind of tactic. I'm not sure that it'd work for people without lots of experience.
Michael
Programming is great. First they pay you to introduce bugs into software. Then they pay you to remove them again.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Yes, well may be it works but you are luckier than the average candidate.
Being an inquirer as you explain it makes yourself communicate more aggressively to the interviewer, even if you think you have the right tone. Not only interviewers are not used to it, they are unlikely to provide you with adequate answers.
I admit it does not necessarily mean you have an aggressive face when asking questions. But eh, only very open, stress free people, or people in their 30s-40s are able to do this. And when you have such a state of mind, you usually don't end up with a job as software developer or the like.
To succeed with such behavior, you also have to maintain a neutral face and avoid mimics, to show that you are really interested, not just trolling or laughing at them.
An interesting point is to check how the HR or technical people answers your questions. Bubbling or hesitating answers reveal quite a lot indeed...
Finally you can figure out that, at this level of this recruitment process, what counts more is human communication. Not technical skills, there will be plenty of time after you are hired to go on with it...
PS : the idea of having a contact with an "insider" is great. Both parties can take advantage of it, and this is likely to result in better and more long term recruitment. Unfortunately, in France for instance, very few HR people do so (HR have quarter objectives and have signed an EPM, don't forget it).
-- modified at 10:05 Saturday 8th October, 2005
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Have to disagree a little bit.
I'm less than 30, however, I consider the interview as both ways and it works well. When looking for a new job (I prefer to quit before to search), I KNOW that I will succeed before to retire in a few decades, so the interview is never the "last chance" but an opportunity to find THE dream job. After all, I will not work for them but we will work together, right?
Now this doesn't mean to be aggressive, but dynamic, very attentive and self-confident. It can be done almost seemlessly: "Yes, I used to work with SourceSafe and CVS and, btw, what tool do you use? None? Ok, I can bring you that if there is interest on your side." 
Of course, it's easy with no house, no kids and a job market that I am blindly confident is still strong enough for people like me. Anyway, if I fail, then it's maybe time to start on my own...
Eric China PRC
P.S.: the article forgets the unit tests: the probation period...
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
The way you see it is very positive, and as such it deserves its own purpose.
However, the one person at the origin of the thread talked about questions such like "why should I work for you?" which could mean the person has a lot of ego.
The sentence "I used to work with SourceSafe and CVS and, btw, what tool do you use? None? Ok, I can bring you that if there is interest on your side" is open and constructive, that's totally different.
-- modified at 10:06 Saturday 8th October, 2005
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Right on. Another idea would be to run the Joel test on the company.
Cheers, Simon
"Sign up for a chance to be among the first to experience the wrath of the gods.", Microsoft's home page (24/06/2002)
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Loved the "Joel Test". I had to laugh, because "do you use version control" is always the first question I ask. I have yet to get a "yes" answer. Thanks for the link!
Marc
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Marc Clifton wrote: "do you use version control" is always the first question I ask.
I always ask "what version control do you use", assuming that it's obvious in any team work environment it's impossible to work without one.
Marc Clifton wrote: I have yet to get a "yes" answer.
I thought it's only happening in the "one man show" companies to not use version control. However it's usually possible to run your own since you are the only guy writing the software anyway.
In any place that many people are working on the same code it's a must.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
I agree. Recently, I interviewed as a contractor for a "educational" game company in CT. Every programmer and graphic artist said "we'd love to use version control, but nobody knows how to set it up".
More recently, I was talking to the network admin for a company in Rhode Island that does telemarketing via fax, and he was asking me if I thought version control would be useful, because there's about 8 programmers on the project. Good grief.
I used to work for a game company in San Diego (Software Sorcery, now defunct) that used version control, but they tied it in to the build process for each programmer. The batch file automatically checked out any latest code before building. Talk about instability!
And my best story is this: An "integrating" company in San Diego had one team using a bootleg copy of version control. Why? Because the senior management didn't want to spend $600 per seat for PVCS or SourceSafe. Instead... they thought the programmers could WRITE THEIR OWN, and then SELL it as a product. Hahahahahaha.
Marc
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
I'm a one man army show now and don't use version control, but back when I worked in a team environment, the version control was all done by the (one) designated coordinator. I can't remember it being that difficult. The only way I'll really know if its any good is to use it I guess. But maybe ab article here at CP about the advantages of version control would be useful to enlighten some of us antiquated folk.
Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
This article looks like it was in a server cache since a couple of years, and only came to the surface now, as it comes with soooooo many stereotypes that have burned 1000 times and proved wrong since the internet debacle.
IMHO, one of the smartest path to return to a new appealing job is to improve the ability(ies) to communicate.
That's not a matter of technology. If that was, you HR people would have been phased out a million times already.
My -0.5 cent.
-- modified at 10:05 Saturday 8th October, 2005
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
StephaneRodriguez wrote: as it comes with soooooo many stereotypes that have burned 1000 times and proved wrong since the internet debacle.
Can you give specific examples of what you mean by this. I've read the article through a couple of times and I'm lost to what you are referring too.
Thanks,
Michael
Programming is great. First they pay you to introduce bugs into software. Then they pay you to remove them again.
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Ok, I have taken this to discuss with : "Do you meet all of the required skills and experience for the jobs you applied for? "
- "Required skills" means nothing. More than 80% of software developer job offers will simply list a series of languages or systems...just for you to end up doing C++ 99.99% of the time.
- Required skills evolve all the time. Do you know what CLI, J#, EJB mean ? Are you a loser if you cannot describe with a simple sentence what each technology is and used for ?
- You are required 3 or 5 years experience with technologies that just came out.
- Required skills cannot be discussed with HR people.
- Required skills such like technology names is an insult to software developers. It's much like saying that the only way to discuss a developer is to use those keywords.
- "Required skills" corner you as a specialist with the so-called skills, while what you are looking for is to begin your job, but you are willing to train and learn new technologies troughout the years, hence new skills. The Required skills thing by definition tell you that you won't be trained. In fact, if you are a passionate guy and like new technologies, you'll end up with self-training. That's not bad at all, but that's a non industrial training.
- "Required non technical skills" such like the ability to work in a team is 1. obvious, 2. useless in being named, 3. a way to avoid to discuss the real projects you would work for.
-- modified at 10:05 Saturday 8th October, 2005
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
Stephane,
This is pretty much right. The whole nature of IT recruitment is flawed. Everyone is obsessed with buzzwords. In many cases any competent programmer can get to a reasonable degree of proficiency in a new technology within a few weeks and is often at least useful well before that. But willingness to learn seems to be regarded as a black mark against you.
See also Debunking the Myth of a Desperate Software Labor Shortage (This is long, but see sections 7 and 10)
Kevin
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
That's a great paper everyone should read as a replacement of this 'upgrading your career' crap published in Codeproject.
It is full of real stories, and that's what counts.
-- modified at 10:05 Saturday 8th October, 2005
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
StephaneRodriguez wrote: That's a great paper everyone should read as a replacement of this 'upgrading your career' crap published in Codeproject
Huh ??
All his examples in that paper are stated in order to make a case for stopping immigrants from coming into hi-tech industry in the US.
Matloff used to be all over immigration usenet newsgroups in the mid-90's bashing the H1B program in general and asian and indian immigrants in particular. Samples
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
 |
|
|
Nice article, good to have something from someone involved in the recruitment of techy positions. I am still an undergraduate but am aiming to get a 1st (as all students always do), but am currently comfortably in an upper 2nd position (not sure if you're aware of the UK grading system).
Anyway, I will be looking to get a graduate job when I leave, and would particularly like to target larger Companies doing development work. Whether that be applying to one of the consultancies such as Accenture or Logica, or working for a development Company itself.
What would you suggest as being the key things I ought to hone? On any application forms I send off should I be stressing technical abilities, or would that be considered a given and its a case of finding a person with the best attitude etc.?
-- Paul "I need the secure packaging of Jockeys. My boys need a house!" - Kramer, in "The Chinese Woman" episode of Seinfeld
MS Messenger: paul@oobaloo.co.uk Sonork: 100.22446
|
| Sign In·View Thread·PermaLink | |
|
|
|
 |
|
|
General News Question Answer Joke Rant Admin
|