Landing the Internship or Full-Time Job
fires_of_heaven writes "Faced with some technical site interviews, I decided to rummage the web and came across a blog titled Landing The Job. I found the advice on the blog far more useful than the other random tidbits I found, so I emailed its author a quick note of thanks. The next day I found Landing the Internship or Full-Time Job at my doorstep. Normally, I don't bother with career books, but this title is written by people that have recently landed an awesome job at companies like Google and EA Games rather than a hiring manager or recruiter. It even includes the resumes they used to "Land The Job." Read the rest of Paul's review.
Landing the Internship or Full-Time Job During College
author
Robert R. Peterson
pages
299
publisher
iUniverse
rating
9/10
reviewer
Paul Gerken
ISBN
0595366813
summary
A guide written by those that have recently landed jobs at Google, EA Games, Intel, Amazon, IBM, and others
The book starts out with a foreword by an IBM Executive and then covers 10 chapters which I comment on individually below. Each chapter is followed by a profile from either an intern or new hire at a fortune 50 company. The profiles include a Q&A and the resume of the individual. I found them to be practical and honest. For example, Ben Lewis who is profiled as an Xbox developer said that he sometimes feels that he can't make a difference at Microsoft.
As a busy computer science student, I can really appreciate how the contents are written. Each chapter has a "Bare Minimum To Do" list with suggestions on how much time each item should take. They also include "Common Mistakes" sections. I especially used the to-do list for the company research chapter.
Another observation I should share is that everything is by example. When cover letters are discussed, there are two example letters--when rejecting an offer is discussed there are example emails. There are even example dialogs for behavioral interviews and for salary negotiation. I think most career books endlessly rant on about methods and rules. Landing the Job seems to be more centered in reality.
The only complaint I have is that there are a few minor grammatical errors. Overall, I think this book is going to be a classic. I haven't had all my site interviews yet, but I know it will help me land my future job.
Chapter 10. HR Interviews and Salary Negotiation
In my opinion, this chapter should be first because it is the best one. It starts off by talking about why recruiters act the way they do. Then it covers salary negotiation which includes a sample dialog between a student with an offer and a manager. I used the "Offer Comparison" section and am sure I will use again. It walks through how to evaluate the worth of an offer step-by-step. It even has a sample offer letter that it walks through as an example.
Chapter 1. Building Unmatched Credentials
If you are like me you often skip the first chapter of books. I didn't read this chapter at first because it talks about how to get experience while you are in college before you are looking for a job. Since I am already looking for a job, it doesn't really apply to me. After looking over it again though, I think it has really good advice. For instance, it recommends that spending endless hours to increase your GPA by a tenth of a point is not as important as finding personal projects or interests in your field.
Chapter 2. Crafting a Successful Resume
This chapter walks through writing a resume from a brainstorm to text and pdf versions. I didn't follow the entire process because I already had a resume, but the examples really helped. I also used the resumes from the profiled new hires and interns at the end of each chapter for ideas.
Chapter 3. Writing a Strong Cover Letter
I didn't have a cover letter prior to reading this. This is one of my favorite chapters because it is a short and sweet guide to getting together a nice cover letter. It includes two sample cover letters written by a mechanical engineer and a computer scientist. It also explains when to use a cover letter. For example, it suggests that a cover letter on-top of a resume can be mailed to any company address--say their customer service department--generating job leads outside of typical HR channels.
Chapter 4. Researching an Organization
I used this chapter less than the others, but it does answer some vital questions--what you need to find out and where to find it. It covers research with the internet, at company career sites, and at libraries. It has a profile of an IBM new hire at the end explaining how company research helped him.
Chapter 5. Secrets of Applying Online
This chapter is amazing. I didn't know how to put together a text resume properly until I read this chapter. I didn't know that many online forms accept unicode 2.0 not ascii so you can add bullets, underlines, and other characters to text resumes. The end has a profile from an Intel new hire and how he got his job by applying online.
Chapter 6. Mastering Career Fairs
This chapter wasn't that much use to me since I've been to a lot of career fairs. However, I agree with all the advice which is basically to know what you are going to highlight from your resume, how to act calm and confident in front of a recruiter, and to pay attention to who is attending a fair. It also cites references of where to find career fairs.
Chapter 7. Learning the Art of Interviewing
This chapter covers interviewing in general and topics that are not specific to behavioral or technical interviews. I read this chapter twice and I think I'm going to read it again before my next site interview. It covers how not to be nervous, getting safety offers, phone interviews, dinner interviews, and what you should try to emphasis about yourself during an interview (as well as what not to say). The end profiles a PhD student deciding between Google, Amazon, and Microsoft.
Chapter 8. Behavioral Interviews
Although I don't often do behavioral interviews and I don't think they are that big of a deal, I found this chapter useful. It explains why employers like behavioral interviews so much (in a nut shell they are assume future behavior will reflect past behavior). It also has an example behavioral interview and example questions--they are hard ones too.
Chapter 9. Technical Interviews
It is clear that the author has had some serious technical interviews. This chapter covers brain teasers to quality assurance questions to hard-core programming questions. It has a huge section on example questions and solutions (which takes up about a 4th of the book). It covers how to write good pseudo code, how to handle the situation when you haven't a clue what the answer is, and even technical questions for non-computer majors like civil engineering and mechanical engineering.
This is an excellent book for any major in college."
You can purchase Landing the Internship or Full Time Job During College from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The book starts out with a foreword by an IBM Executive and then covers 10 chapters which I comment on individually below. Each chapter is followed by a profile from either an intern or new hire at a fortune 50 company. The profiles include a Q&A and the resume of the individual. I found them to be practical and honest. For example, Ben Lewis who is profiled as an Xbox developer said that he sometimes feels that he can't make a difference at Microsoft.
As a busy computer science student, I can really appreciate how the contents are written. Each chapter has a "Bare Minimum To Do" list with suggestions on how much time each item should take. They also include "Common Mistakes" sections. I especially used the to-do list for the company research chapter.
Another observation I should share is that everything is by example. When cover letters are discussed, there are two example letters--when rejecting an offer is discussed there are example emails. There are even example dialogs for behavioral interviews and for salary negotiation. I think most career books endlessly rant on about methods and rules. Landing the Job seems to be more centered in reality.
The only complaint I have is that there are a few minor grammatical errors. Overall, I think this book is going to be a classic. I haven't had all my site interviews yet, but I know it will help me land my future job.
Chapter 10. HR Interviews and Salary Negotiation
In my opinion, this chapter should be first because it is the best one. It starts off by talking about why recruiters act the way they do. Then it covers salary negotiation which includes a sample dialog between a student with an offer and a manager. I used the "Offer Comparison" section and am sure I will use again. It walks through how to evaluate the worth of an offer step-by-step. It even has a sample offer letter that it walks through as an example.
Chapter 1. Building Unmatched Credentials
If you are like me you often skip the first chapter of books. I didn't read this chapter at first because it talks about how to get experience while you are in college before you are looking for a job. Since I am already looking for a job, it doesn't really apply to me. After looking over it again though, I think it has really good advice. For instance, it recommends that spending endless hours to increase your GPA by a tenth of a point is not as important as finding personal projects or interests in your field.
Chapter 2. Crafting a Successful Resume
This chapter walks through writing a resume from a brainstorm to text and pdf versions. I didn't follow the entire process because I already had a resume, but the examples really helped. I also used the resumes from the profiled new hires and interns at the end of each chapter for ideas.
Chapter 3. Writing a Strong Cover Letter
I didn't have a cover letter prior to reading this. This is one of my favorite chapters because it is a short and sweet guide to getting together a nice cover letter. It includes two sample cover letters written by a mechanical engineer and a computer scientist. It also explains when to use a cover letter. For example, it suggests that a cover letter on-top of a resume can be mailed to any company address--say their customer service department--generating job leads outside of typical HR channels.
Chapter 4. Researching an Organization
I used this chapter less than the others, but it does answer some vital questions--what you need to find out and where to find it. It covers research with the internet, at company career sites, and at libraries. It has a profile of an IBM new hire at the end explaining how company research helped him.
Chapter 5. Secrets of Applying Online
This chapter is amazing. I didn't know how to put together a text resume properly until I read this chapter. I didn't know that many online forms accept unicode 2.0 not ascii so you can add bullets, underlines, and other characters to text resumes. The end has a profile from an Intel new hire and how he got his job by applying online.
Chapter 6. Mastering Career Fairs
This chapter wasn't that much use to me since I've been to a lot of career fairs. However, I agree with all the advice which is basically to know what you are going to highlight from your resume, how to act calm and confident in front of a recruiter, and to pay attention to who is attending a fair. It also cites references of where to find career fairs.
Chapter 7. Learning the Art of Interviewing
This chapter covers interviewing in general and topics that are not specific to behavioral or technical interviews. I read this chapter twice and I think I'm going to read it again before my next site interview. It covers how not to be nervous, getting safety offers, phone interviews, dinner interviews, and what you should try to emphasis about yourself during an interview (as well as what not to say). The end profiles a PhD student deciding between Google, Amazon, and Microsoft.
Chapter 8. Behavioral Interviews
Although I don't often do behavioral interviews and I don't think they are that big of a deal, I found this chapter useful. It explains why employers like behavioral interviews so much (in a nut shell they are assume future behavior will reflect past behavior). It also has an example behavioral interview and example questions--they are hard ones too.
Chapter 9. Technical Interviews
It is clear that the author has had some serious technical interviews. This chapter covers brain teasers to quality assurance questions to hard-core programming questions. It has a huge section on example questions and solutions (which takes up about a 4th of the book). It covers how to write good pseudo code, how to handle the situation when you haven't a clue what the answer is, and even technical questions for non-computer majors like civil engineering and mechanical engineering.
This is an excellent book for any major in college."
You can purchase Landing the Internship or Full Time Job During College from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
im looking. any good books for people in mid-career network admin positions?
written by people that have recently landed an awesome job at companies like Google and EA Games...
Okay, an awesome job at Google, I can see that, but at EA? Um...
Here is your chance to test a new law
After a little bit of Googling I found out that the "reviewer" actually works at publishers of the authors book! I'm sure the book just "arrived at his doorstep" - he probably has hundreds of copies sitting in his warehouse.
"this title is written by people that have recently landed an awesome job at companies like Google and EA Games"??
I thought the only thing a job at EA was good for was giving you a bleeding ulcer within 5 years...
----------- Theodusian -----------
I wouldn't recommend wasting your money on books. I've received offers from Google, Microsoft (ew), etc... The secret is being passionate about a project that you craeted or helped make. You need to be able to explain the struggles and challenges that you've faced with the projects you have worked on. If you have no experience in the field, I suggest you start a project for fun. Just write a list of qualities you would want for someone you are hiring, then make sure your resume addresses it. Otherwise, I would focus on programming tricks and questions. TopCoder or ACM like questions are useful for being able to do well quick and easily in an interview type situation.
- Ryan
The author is currently working on his next book, "How Not to Get Fired for Reading Slashdot All Day".
I'm a big tall mofo.
Trust ME!
I heart Cisco!
This is a great review breakdown, concise and to the point. I think slashdot should have a "Tip" button for good articles.
Some points from a guy with absolutely no experience in internship, but as someone who has performed mentorship programs, which are an old fashioned internship to learn a trade:
1. Offer the company you are interviewing the sense that you will be valuable in your position. Remember, in any market exchange, the manufacturer has to offer the consumer sonething for their money. You are manufacturing labor, the company is consuming it -- they are YOUR customer.
2. Understand that BIGGER is not always BETTER. Trying to get in with Microsoft, Google and those guys is a huge task, but if you're one small fish in a very big pond, is there a likelihood that you'll get far? Consider talking with smaller companies -- even much smaller companies. The most successful friends I know are ones who "interned" with small companies and then struck out to start their own: stock brokers, accountants and even retail store owners that all worked in much smaller corporations.
3. Time preference is key. The reviewer here points to that -- chasing after the 1/10th of a point of GPA doesn't translate into time well spent. The old adage that time is money is not really true actually -- MONEY is TIME. Make sure the time you're going to spend with this company translates to earning potential in the future. Don't be a lemming and don't always follow the masses, do proper research in finding out what the real benefits will be.
4. Search for the disgruntled. Use Google and other search engines to find out what made previous employees and interns mad about the company/ies you're talking to. Be aware of the shortcomings of the company, and even use it in your negotiations (although don't be specific, of course). When I lost a profitable business this year due to inept partners, it really hurt my short term ability to bring on new "interns." They point to the lost company (which had my name in big letters on the letterhead) and I know that I am in a decreased position of bargaining. Don't take advantage of the information in such an obvious way, but use it to your benefit. Companies with a sour public record for a given reason will likely be looking for people to help them not have another sour situation. I wonder if Sony is a good place to intern at.
I'm not so sure that the book is necessarily a must-read for those looking to get an internship. From the author's blog, it looks like it's simply an eclectic collection of "profiles" from soon-to-be-graduates that are in the market for an internship or full-time job. Heck, I could've written this book too. In fact, anyone with sufficient interviewing experience (which isn't hard to come by if you're going through recruiting in your senior year of college) can give the same advice. The book is just a collection of these experiences, re-hashed and aggregated into print form. Oh well, if you really want to check it out you can see it here too: Landing the Internship or Full-Time Job During College.
This is Noddy stuff, if you're leaving college or university and can't get hold of good sample letters you might need to buy this book. I had a halfway competent careers officer in my school and this book doesn't sound much better. I think I can also safely assume that the bullshit it is suggested you peddle to get your first job isn't going to work beyond that, and a lot of people who read Slashdot are beyond that somehwat awkward phase in career development.
Where's the Kaboom?
There's supposed to be an Earth-shattering Kaboom.
Getting my coop(now fulltime job) was the best thing I ever did in college. When i discovered how easy it was, i wanted to get my friends jobs, so i would go with them to speak to the person in charge there and make it so my friends were comfortable with her so they would go back on their own. and you know what? the people that went back to her on their own were the ones who got the internships, and the ones who didnt really bother with it too much didnt get it. but if you are in a university, take advantage of the internship/coop program. especially in CS/CE because everyone knows the amount of experience you have can make or break you in future jobs. lots of people are afraid because they dont have experience in what jobs are available. to be honest, i knew NOTHING about this job when i first started (other than i knew how to program java well), but getting the job is about selling yourself. if you can get them to understand that you may not know the material now, but you can learn it, thats all they care about. they will teach you what you need to know.
Here's how you get any job or internship: know someone at the employer who thinks highly of you.
Anecdotally, I'd say at least 80% of hires happen that way. You want to work at Company X? Get to know some people there first, either online or at their local hangout or whatever. I know it sounds like a depressing concession to nepotism, but people ultimately want to work with people they know they can stand to have around.
And if you don't have the social skills for meeting people you want to work with, you're probably going to blow the interview anyway.
Someone must be mistaken! this is slashdot. Around here, people BITCH about not having a good job -- they don't actually go out and find them. Seriously people, do your homework before posting an article like this around here.
Is landing a job at a company thats notorious for shafting it's employees really a "hot" job?
I wouldn't call landing a spot with EA the most awesome job.
How many companies do you call 'awesome' that have workers suing their employer?
I have been employed by EA Canada for almost a year now. I went through a "crunch period" and I've worked many late nights.
I do not agree in any way with the "Spouse of EA Employee" Letter that I read even before I got my job.
I worked hard to get this job, and EA gave me an opportunity that I might not have recieved from other tech companies; Now I have a long way I can go; and many career paths. Aswell as training from EA University.
While EA may have a bad reputation from the accounts of a few angry spouses; I love it here.
To get back to the book; remembering my application process I believe that this book would have been a great guideline; especially for anyone who is interested in the tech field.
I wrote this article years ago for junebug.com, now a defunct website.
How to Land a Job in Corporate America
Nowadays, recent college graduates have two options to consider after graduation: go to graduate school, or join the work force. For the interests of the captivated audience reading this article, I won't bother discussing graduate school (but if you're interested in grad school, I can forward you my other article, "What to do after being denied admission into your favorite grad school").
The problem with finding a job is that most recent college grads don't have the experience that most employers want, and on the other hand, most recent college grads want a job that will best compensate them monetarily. Obviously, most entry-level jobs pay meager wages and won't cater to a person's decadent lifestyle (that is, if you want to continue eating out every night and hitting the bars and clubs once a week). What's not obvious is that if you want a good job, you have to start out at the bottom and work your way to the top. Nobody is ever going to offer a position for an entry-level CEO. So, reality has to dictate the fact that success and wealth come later in life.
Evidently, success and wealth (at least the monetary kind - intrinsic wealth and success can be attained anywhere) can only be attained through the right job, and by the right job, I mean a career in Corporate America. Albeit, anyone can have success and wealth through any given vocation, but only through Corporate America can a person lose all that is meaningful to him and suddenly take on the values and responsibilities of a large group of people and do things for the interests of the company. Once this becomes ingrained in a person's mentality, then he is well on his way to success and wealth.
But, how, you may be asking, does a person go from a happy-go-lucky everyday joe to a person clawing and inching his way up the corporate ladder? Well, my first piece of advice is to network. Learn to make friends in the corporate world, attempt to maintain those friendships, and once those friends learn of your graduation from college (it doesn't matter what your grades were), take advantage of them and use your friendship as a basis for future interviews and job offers. Use them for all they are worth, because if they don't land you a job, then think of the money you wasted on the friendship.
If networking doesn't work, I suggest trying to attend information sessions hosted by corporations regarding employment opportunities. When you attend these info sessions, make not only a mental note of the people that are attending, but take down their names, addresses, and phone numbers. You can then begin to develop friendships with the people who share your career interests. Most likely, these people will have advice on resumes and would be glad to share their list of contacts with you. If they're not willing to part with such information, then sabotage them. If he's not with you, then he's against you, and competition lost is a position gained.
If neither of these two tactics work, you can always do everything by yourself and go directly to a company for an interview. Don't bother calling and mailing a resume. I always feel that this method of gaining a company's attention is a waste of time and stamps. Rather, if you go directly to the Human Resources office without an appointment and refuse to leave without being seen for an interview, they'll see how determined you are, and isn't determination a respectable quality of a potential employee?
Once at the interview, don't be nervous, but rather, be straightforward and honest. It's never a good idea to lie about skills and attributes that you don't have. Instead, wear revealing clothing. If you can't wear revealing clothing, flirt with the interviewer. If you don't know how to flirt, bribe them with money, jewelry, or sex. Bringing kneepads to an interview wouldn't be a bad idea.
If you follow my advice, you will be guaranteed a position pushing paper in a cubicl
semper ubi sub ubi
resumes. I have been looking for a job on Monster and got nowhere with the jobs I physically applied to, but just for kicks made my resume searchable. Nothing but a headhunter for a few months and basically I forget about it. Then about a month ago out of the blue I get an email from a person who wants to set up an interview, and now I am just waiting on the formalities before I get the job offer of my dreams.
Now it's time to share your job site stories; reply if you had
a)no luck with job sites and swore them off forever
b)got the job through going through the "official" application process
c)were contacted through someone searching your resume
d)If Cowboy Neal set you up with this awesome freelance gig.
Monstar L
I'm willing to believe that you're right. But clearly, you're better at googling than I am. Might you point us to a link or two that supports your statement.
Slashdot: Ads for Nerds. Stuff that's paid for.
It breaks my pluginses, my precious!
Don't believe the "benefits" they promote - you will gain all of that by working and being paid for your time and talent, like you deserve.
I suggest you read Slashdot
Obviously this gotta be a scam mostly because:
All those big 3 are using agencies to fulfill their needs in short term and contract basises.
Where the hell is networking in all of this, to keep things consistent with what people talk you should include the networking factor period.
Do you really think I'm gonna buy the "landing the job" crap when downsizing and financial restructuring are the trends nowadays.
C'mon this is a blogger page are you gonna fall for this that easy?.
Most of the content are regurgitations of many books and tips out there, gimme a break.
Dear God no! That is wrong on so many levels. I'm pretty sure that's contra the Geneva convention and several human rights treaties.
the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
Nice troll - short and to the point.
/. flamer and this post fits the profile perfectly.
Before modding this troll +5, it would be worth it to check his journal. The guy's a
Go fine someplace else to whine.
How's the Kool-Aid?
id read the book had not the author of the post been an 'employee' of the publisher... why do they even do this stuff? "I found it at my doorstep" well, if your work there you might! we should ban those people...
http://naerey.switch-case.org
(But yes, EA are naughty naughty bad people)
A tip I gleamed from an in-law is that at the end of the (formal) interview ask the interviewer(s) if they feel you have the ability to do the job. If they say yes, ask them for the job! I've typically phrased it from the point of view of saving them time, e.g. "so, why don't you save yourself some time and hassle, and just hire me now?" Has worked quite well I must say. One HR person (albeing fresh off the block) was actually taken aback and visibly impressed by my asking this and I had a job offer half an hour later (I was waiting for a lift home and he came over to make me an offer), while another was comfortable enough already by this point to say yes.
Then again, if you get a "no, we're not sure if you're quite right" there's not much point in pushing it unless you can first get past their issues.
Damien
1. Make sure you can direct the interviewer to the subject "Microsoft vs Linux" and make you distain for anything Microsoft known and that you think people who do not know the difference between copying and linking files are weenies.
2. Make your distain for anything corporate-America related known from the beginning.
3. Make sure they notice your pierced body-part. Bring up the subject if they do not mention it.
4. Make sure you let them know that intellectual property should be free.
5. Don't take the first offer they make. Hold out, you deserve better.
http://photos1.blogger.com/blogger/152/1924/1600/R hettAultman.2.jpg
Rule 0: The barber is your FRIEND!
Chapter 1. Building Unmatched Credentials
Dude, work hard and be nice to poeple. It takes 10 good references to make up for one bad one.
Chapter 2. Crafting a Successful Resume
I think that if you can not build a resume that is clear, with good spelling and clear ideas, you should not be hired. Get professional help (pay someone to help you) if you are clueless.
Chapter 3. Writing a Strong Cover Letter
Make it brief, leave you contact info, and be enthusiastic.
Chapter 4. Researching an Organization
Google around about the company for at least 5 minutes, DUH!
Chapter 5. Secrets of Applying Online
Brief emails with your contact information and resume attached (or a no-nonsense URL) is the only way to go.
Chapter 6. Mastering Career Fairs
Keep away from these evil wastes of you time. 1-on-1 in this market is best.
Chapter 7. Learning the Art of Interviewing
Well, you are who you are. Talk only when asked a question, speak slow, be calm (self-pleasure before interviews work well), and eat a little before you go in. There are some techniques you can learn to fake it, or give a "template" message - but dont go that route - people you want to work for can sniff that crap out. Be yourself, and give clear honest answered.
Chapter 8. Behavioral Interviews
Again, most people you want to work for will know if you are faking. Common sense during such interviews is best. If you dont have common sense, you are f'ed.
Chapter 9. Technical Interviews
The best answer I heard was "I dont know, but based on my previous experience, let me take a few intelligent guesses...." But in general, if you don't know it, do not try to fake an answer. That will be like shooting yourself in the foot a few times.
Chapter 10. HR Interviews and Salary Negotiation
Well, always aim high. If you ask for a low salary, you get a low answer. I also like having pay raise analysis every 1 year or 6 months in my contract. Please, it's not rude to be very clear and un-embarassed asking for a certain salary. These 5 minutes of negotiation will determine your fiscal outlook for a long time, so I say be bold of they will bowl you over!
Horns are really just a broken halo.
I work in the IT field in a retail business. I tried to recruit interns, paid interns, from the local university. I was suprised by the lack of response. Students these days do not appear to be interested in working while going to school.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
Come on all you lefties with mod points, prove me right!
Instead of proving you right, I think I'll prove you left!
Here's a tip...
Learn to count. Don't put Chapter 10 before Chapter 1.
1) Mass email your CV and let everyone see everyone else's email addresses.
2) Have a mini blog on your website/portfolio that says the city you're in "has design studios that are crap and all they produce is shit".
3) Send me links for work examples that don't work - if you're applying for a web developer job, I expect to see web work. Similarly if you're applying for a copy editing job, I don't want to see a typo on your CV.
3) Send me "questionable" work samples to review - that gay porn site that you got paid to put together might not be something you want to be remembered by.
4) Spell my name incorrectly if you're emailing me.
5) Call me when I specifically say on the job ad NO PHONE CALLS.
6) Show up late or not show up at all for the interview.
7) Inappropriate dress, demeanor at interview - you would think this is a given but it isn't.
8) Tell me your life story at the interview as opposed to your work experience.
9) List age, marital status, GPA etc. on the CV - this may be SOP in other countries but not in the U.S.
10) Send out your CV and cover letter without getting a friend to review it. If you have no friends, pay someone, get your mother to do it. Ultimatley, you're not "waiting for my replay" and I don't want to "TTYL".
I do not agree in any way with the "Spouse of EA Employee" Letter that I read even before I got my job.
That's fine, but does your wife?
Give me Classic Slashdot or give me death!
Networking! I have landed most of my jobs from attending seminars and conferences and networking. People like to hire people they have met and know. Get invovled with user groups and attend conferences and seminars in your area.
www.IBuyMacs.com
Bush doesn't suck? Man, that annoys me. Think I'll report this to DHS. That'll learn your anti-American booty.
Furor? Is that you?
Perhaps the reviewer isn't the person to ask. There's a few hints in the review that he still doesn't have a job. Ok, I admit that's totally unfair joke at his expense. It's a tough job market. I think it was a good review, despite the fact that he mentioned occasionally bad grammar as a downside of the book, then forgot to proof-read his own submission.
Having completely failed at it during my brief time of unemployment after graduation, I'm intrigued by the chapter on applying for jobs online. I seriously doubt any of the resumes and cover letters I submitted to online forms were ever seen by human eyes, regardless of whether I tried to write like a real person or match keywords in the job description. The worst part though, was their lax responses. For one job I applied at with Boeing, their online system showed my status changed from "Under Consideration" to "No Longer Under Consideration" the same day I submitted the application. That, however, didn't surprise me nearly as much as the (computer-generated) email I got, a full 5 months later, letting me know that they had selected another applicant and that they "wanted to let you know as soon as possible so you can pursue other opportunities."
1. Lie at all costs.
2. Forget the Constitution, deny everything.
3. If your mouth is open, a talking point or denial should be coming out of it.
4. Go to war on false pretenses without a plan; be sure to underestimate the enemy and say things like "bring it on" in reference to combat; also, be sure your troops are not properly supplied.
5. Be sure all contracts are no-bid to corrupt associates.
6. Profit.
"Im going to call BS if you say you have gotten every job you ever applied for."
I pretty much get an offer for every job I've ever applied for; the only one has been lately when I applied for a "C" level position at a company about to go public. I mostly lost out because I don't have "C" level experience, but it was down to me or the other guy.
It is possible. I make sure that the company actually wants me when I leave the interview. They always do.
I only disagree with your GPA comment. One of my friends wrote his (very high) GPA on his CV, and not only was he hired, he mentioned that he saw a copy of his CV on his interviewer's desk with the GPA circled in red. Of course if your GPA is middling, then don't write it.
The EA Spouse blog had a lot of truth from it, but that only applied to the Los Angeles studio. A LOT has changed since then. I was at the studio for about a year before that blog, and I found parts to agree with, but things have changed (around that time a new general manager took over the studio), and if that same blog were to be written now, I would consider it all lies. I was getting frustrated by the conditions around the time that blog came out, but now I wouldn't give up my job here for any other studio; I love it. I've talked to people at other publisher's studios (Sony and Activision), and they have insane hours now, while it's very family-life friendly at the EALA studio.
Apply everywhere you think you might want to work. Whether they are advertising something or not. The hundered or so bucks you'll spend printing up and mailing out several dozen resumes will get back to you when you get a job sooner than a more conservative approach would get you.
Put your resume on *every* jobs website that covers career fields you are trying to get into. Whether you actively monitor a given site or not, have a resume up there. Most of my contacts have come from sites I don't actively monitor, the two sure things(one I had to turn down because I was woefully unqualified, the other I took) were from sites I didn't actively montitor.
HOBBY EXPERIENCE COUNTS. Sure, formalized volunteer experience, or workforce experience, is better... but if you need to cover some time unemployed, a summary of hobby type experience can help. It's much better than simply "unemployed" being listed on your resume. My current job as an on site tech... the interviewer was mostly interested in my IRC Operator status I put on my resume... almost completely informal, definitely a hobby rather than a job or serious volunteer position, but it was a HUGE help in landing a job.
Have resumes focused on each major field you are going for. For a "job of a lifetime" application, focus it as tightly to that position as you can. Also, have a generic resume available in case someone asks for it and you don't have one that is especially fitting- but do follow up with a more targeted resume.
Register with every temp agency that covers your job field targets. Every single one. Even though those jobs aren't guaranteed to be long term, they are experience, and there are times that they do convert to permanent positions. My manager has basically told me that as soon as the red tape clears(beauracratic inertia is more powerful than God Himself) I'll be moved from temp to permanent. Just have to hit the ground running and work your ass off. Even if you don't get a permanent position, if you impress them, they will be solid references.
Ok, I'll bite.
I've had no luck with job sites *as an employer* because 99% of the resumes I receive are from foreigners( particularly Indian )studying or living in the US. Why is this a problem? Disregarding the visa sponsorship issue, it is my experience that Americans are best suited for transforming the problems faced by American business into viable software solutions.
Do I get any decent leads from monster.com in this regard? Nope.
I really am disappointed with monster.com. As a hiring manager, I don't know where else to turn. Headhunters are *far* too expensive and generally harbor incompetent people who cannot pass the technical interview process.
I knew this would fit in here somewhere...
I had a good GPA as an Undergrad in Electrical Engineering - 3.8 or so. This got me a lot of interviews, and I went to almost all of them. At least 20% of those interviews were obtained on my GPA alone, due to what I refer to as "The Lazy Recruiter Syndrome." The best example I have is a recruiter who did not know what type of engineer I was, and was asking me lots of specific questions from another unrelated field. When I mentioned to him what my major was, he got a little flustered, realizing that I knew he didn't read my resume at all, and said "let me tell you about our technology management program..." I said "No Thanks" and got up and walked out of the interview room.
A large publicly traded consulting firm had a very similar tactic, just going after anyone in sciences with a high GPA. The MIS (management of info systems) grads were drooling for these jobs, and the EE/CS guys were pretty bored.
heh bullshit. I work for ea and they have absolutely no idea how to develop software. there is so much cooperate bullshit going on that nothing ever gets done right. they have 300 people working on godfather ! and they still can't ship the dam thing! i'm amazed they can even ship games. if it wasn't for money out the ass and repetitive sports titles they would have died long long ago. the end is coming soon for this project and i guarantee that the whole team will be working 60-80+ hours to get this game out the door.
I have no problem *landing*, I just don't know when to quit =(. /getting walked all over for shit pay when I'm worth at least 2x what I get.
I've used to follow a lot of those tips when I was a newbie in the field w/o a CS degree. And I ended up with boring positions that went nowhere, no career. Then I took a few educated risks on some companies, and though the work wasn't as exciting, it gave me time to really figure out how to approach the task of building a career. I was able to meet lots of people, improve on my non-technical skills, and really see what it takes to participate in the industry--"what makes it tick".
I digress when I was entering the workforce, I was in the anti-social/networking camp--I thought you could make it big on merit/skill alone. Unfortunately I didn't start my own company, instead I was stuck in Corporate America.... In the end, the best jobs I had to date where either by being at the right place-time (i.e. internet boom) or by my networking skills.
Know the industry atmosphere, look for challenging work, and use your network.
That is what I have always done since, like yourself, I am experienced. It has never failed, and it has never taken more than a week.
Good luck out there!
"Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
Don't you think that this focus on internet related jobs (such as Google) is just a subtle continuance of dotcom? What's going to happen in five years when the government (any government) nationalizes this stuff? It's raining INTJ! Oh, the humanity!
I have an idea! Punch me in the face!