|
yeah thats you not being very helpful
Bryce
MCAD
---
|
|
|
|
|
First, are you using your resume as bait (for head hunters to call you) or as a key to get you into a specific interview.
If the former, then pepper your CV with the terms that you will get your resume appearing on resume searches that best suit you. Ditch the adjectives and list the stuff you know.
For the latter, craft your resume specifically to the job your after and ditch the extensive. If I'm hiring I always do a phonecall first and within 2 mins I know the level of experience. I smell a liar and the phone's back on the hook.
So: look for jobs that are specifically OK with your level of experience. Then there's no reason to be shy. Second, build up that experience. Experience does not have to be paid experience, it simply means how long you've been practicing, honing and using your skills. I'd employ someone who's spent a year learning and playing with node.js in their spare time and has then posted 2 CodeProject articles on the topic just as much (if not more) than someone who's been doing it as part of their job for 2 years.
Number 1 thing employers in Tech want is someone with a brain, someone who can learn new things quickly, someone who wants to get the job done and leaves the ego at the door, and someone who has the basics of software development (eg OOP, SOLID principles) down pat. Everything else is just details.
|
|
|
|
|
Chris Maunder wrote: Number 1 thing employers in Tech want is someone with a brain, someone who can learn new things quickly, someone who wants to get the job done and leaves the ego at the door, and someone who has the basics of software development (eg OOP, SOLID principles) down pat. Everything else is just details. |
Unless of course its a non technical person doing the hiring. Then they need boxes ticked to cover their own arses.
I.e. Christan Grass himself wouldn't get a job coding .net in a Government Dept if he didn't tick all their HR boxes.
(you know what I mean) - so (as Chris -one pint- Maunder says) tailor the CV/application to the institution/company.
Bryce
MCAD
---
|
|
|
|
|
I read that as "Le Christian Graus" so I think I'm just going to call him Le Graus from now on. Yeah: him and HR in any place that favours paperwork over results. Not pretty.
And it was an extra large pint, that one. I swear.
|
|
|
|
|
Chris Maunder wrote: And it was an extra large pint, that one. I swear.
relevant[^]
Bryce
MCAD
---
|
|
|
|
|
It was a schmiddy, and light beer at that.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
it wasnt beer he was having - twas 4x
MCAD
---
|
|
|
|
|
You could always move to a city where the development market is still hot and they don't mind your low amount of experience. If you're willing to do that, then you won't have to stay unemployed long.
|
|
|
|
|
Wow. Thank all of you guys for your quick replies. It means a lot. I can't relocate right now; don't have the money, and I might have to rely on my emergency stash to survive past December.
1.) I have my resume out on Monster and my state's Talent Bank, but am not aiming for recruiters/staffing agents (though they've been calling me about it from Monster). I don't know anything about them, and I want a direct hire (no contract work) in the first place. So, I haven't been paying them the most attention. Should I start using them? So far, I've been applying to postings that match my experience, and that hasn't gotten me too far.
2.) Whenever I find a position that matches my experience, I typically keep the same resume, but craft a cover letter where I try to match all of their listed requirements with my qualifications. Should I be morphing the resume as well? As of now, I only change the resume if the posting says they don't want Cover Letters.
3.) Does work really heat up in Feb-May? My unemployment isn't going to last past December. I've got money to last for about 2 months after that (barring no disasters). Crap.
4.) As I mentioned before, I plan on making a portfolio I can show off to prospective employers once I'm done learning what I can about C#. However, I don't know what project I can do or how to set up a site on a webhost (told you I'm rusty). I can probably scrounge around on sourceforge for projects to help with or code to inspire me, but do any of you know of a good, cheap web host I can use for a site that won't see very much traffic?
|
|
|
|
|
More often than not, companies don't necessarily care that you know a particular language, they are more interested in what you did with it. For example, "Used <language> to integrate accounts payable with the distribution center inventory, resulting in a 15% reduction in time spent gathering parts."
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
"extensive experience" already looks weak.
|
|
|
|
|
Do you think it be something concrete, like "Over 2 years academic and personal experience writing small programs in C++, Visual Basic and [all the other languages I've encountered], with over 50 programs written."
|
|
|
|
|
It helps to have a solid article (with your code) on CodeProject, showcasing your original work. When I was looking out to for a change, I quoted a couple of my CodeProject articles on my resume; my current employer looked at that code, and I believe, was convinced enough. Of course, you need to work on an original problem, making sure that none of the work done for your past employers is getting posted.
Also, I feel that employers look for problem solving capabilities using a language, rather than expertise in that language itself (unless it is a compiler company you're applying for).
|
|
|
|
|
'Qualified and trained in C++, Visual Basic and SQL.'
'Commercial experience in FoxPro and .Net'
Currently gaining experience in........
?
You should be working on home projects for the last one. The world is your oyster.
Just supplying a piece of paper and saying 'yes please' will not get you employment.
|
|
|
|
|
Instead of "extensive", you may use "experienced/skillfull in" something. In my opinion, the experience gained from course work is considered to be good experience as long as you are confident for what you learned. Certainly it might not be the real business world solution you coded. But the technology involved and skills required are all applicable to the real world.
TOMZ_KV
|
|
|
|
|
If you lie cheat tweak your experience in the world of software, you will be busted the first week of a new job (unless you're working by yourself). Tell the truth and express the level of enthusiasm you have. Software takes two things: aptitude and enthusiasm.
|
|
|
|
|
Look, the purpose of your resume is to help a perspective employer determine if you are what they are looking for.
Never overstate your skills. I have questions that tell me your C level of experience, and the minute I detect dishonesty, you are out.
On the other hand, if you are willing to learn, have mostly college experience, then you should stating that. In my opinion, you are an entry level developer. You should try to go back to the CC/Univ you have attended an enlist help from their Career Development, check their job postings. They are looking for people with your skills. Also, if your are NOT listing your GPA (at least your major GPA), it is a red flag to me. I have a perfect GPA in my major, I list that...
Next, the biggest mistake people make (IMHO) on a resume is telling me what they DID. I want to know what IMPACT you had. (So you wrote reports, big deal. But developing a set of reporting templates to allow managers to more easily generate their own reports. That is IMPACT.) Don't lie.
Finally, having worked in Career Development at Mich. State... Let me emphasize:
1) The purpose of the cover letter is to introduce and point out what on your resume should interest them
2) The resume exists to see if there is a match, determine what type of skills, and provide a basis for further questions, which hopefully requires an interview to go over. The resume should get you the interview, not the job.
3) The interview(s) get you the jobs.
Note: on an interview, I brought a BRAND NEW day planner with me. The guy asked if I used it, liked it, etc. Then he asked me to hand it to him so he could flip through it! Luckily I was honest up front and said I just started using it because of the interviewing schedule!!! (2 weeks back, it was all blank!)
I wish you luck.
|
|
|
|
|
I must confess that this problem is not new to me. My advice to you is to have 2 resumes. One should represent your true status, and then the second should represent your desired status. Your field is quite easy to develop some experience. When you develop a project (using codeproject and other resourceful websites), understand the project thoroughly so that you can easily explain it. If it's a web application you can host it on the internet. Then you can put something on your resume about this project.
Like someone said, it doesnt have to be done through paid employment. Use the desired technologies and have faith in yourself, then you will get your job.
Fortēs fortūna adjuvat.
|
|
|
|
|
Be honest. You don't have "extensive experience" but do have experience.
On my resume, I list the number of years I've worked with Windows and Windows CE/Embedded, since those are the jobs I want. Then I list "Key Technologies" without any reference to how experienced I am with them. In the jobs section, I repeated which technologies I used in that job, letting that speak for itself. During the interview, I expand on them in response to inevitable questions, giving specific examples on what problems I solved, how I solved them and how they helped the company and their customers.
Job interviews are a two way street. Not only am I trying to sell myself to them, I'm trying to determine whether I want to work for them. Their questions and what they concentrate on tell me a lot.
Finally, if you put VB on top, you'll get VB jobs. Is that what you want? It appears you want to de-emphasize the VB itself. Change your resume to reflect that. In other words, your resume is a sales tool and if you scream "I DO VB" on it, don't be surprised when those are the only interviews you get. In your case, you are a junior programmer, so I'd emphasize your problem solving skills. And be patient. You may need to take one job and work into another (no just fiction; this happened at the company I was at three years ago and was starting the process with a PHP guy at my current place before he jumped ship to another company.)
And, to repeat myself and advise above: DO NOT LIE. (If I even suspect a lie in a resume, I toss it.)
|
|
|
|
|
Yeah, I feel really stupid that I had "extensive experience" on there now, without even thinking about what that meant outside my context. This resume is mostly a carry-over from my fresh-out-of-college days with my latest work history in there. At the time, I did feel pretty confident in C++/VB. Now I'm looking at intermediate interview questions to get an idea of the things I should be studying and my brain is melting. So, I have to do something more accurate.
Thank you guys again for all your help. I have a meeting scheduled with my Alma Mater's Career service today. I'll let you know how it goes.
|
|
|
|
|
Hey guys. I just got back from a meet with a lady at my college's career center, and a talk with a previous professor of mine.
When I voiced my concerns about exaggeration, the lady suggested several things, like:
-"Course work completed in [all the languages listed in my resume]". This seems very weak to me, but is the most accurate.
-"Experience in [all the languages listed in my resume]". Just cut off the "extensive." This seems like an easy fix. However, what if an employer calls me in and I still don't have the experience they're looking for?
The professor recommended the second one above, but said later that he probably isn't the best one to talk about these things (he hasn't had to apply to a job in years). He's going to refer me to someone else who might be better. Still, I think it's a toss up between the two above. I don't know which one to go with though. Like I said, I want to be accurate without being scoffed at (even though I'm aware people aren't expecting those 2 years out of college to have serious company experience under their belt)
|
|
|
|
|
......It's a holiday tree! 
The difficult we do right away...
...the impossible takes slightly longer.
modified 3-Dec-13 20:08pm.
|
|
|
|
|
|
Do I take you correctly that you're saying the post is trolling?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Troll the ancient yuletide carol.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
