How to apply for a job

1. Make sure you are qualified for the job you applying for

Often applicants tend to apply for jobs, what they want to do, but sometime they are not qualified to do.

Yes, it is normal to go for the next step in your career. From a recruiters point of view, it's anyways more important to match your background and experience with the recent job profile, rather than matching the applicants future vision with the job profile. Of course the job should meet your expectations as well! 

2. Writing your application

An application should first of all include your resume. Make it smooth for the company you are applying at to read your application. Avoid sending too many documents! If possible, PDF them to a max. of three (resume, transcripts, references&certificates)

Resume:

Be clearly and structured in your resume. Your resume should include information about your education (university, degree, GPA), your professional experience (company, job title, description of YOUR responsibilities) and any additional information (e.g. publications) which could be relevant for the company or job you are applying for. Most people who review CVs like bullet-points today, because it's clear and not overloaded with "sales language without content". :-) 

Please do not put in any collection of keywords, where you are not really experienced in. 

Imagine you get interviewed with questions focused on everything you mentioned in your resume! 

Find some more tips about writing a resume here.  

For technical positions (software engineering), please list your used technologies (programming languages, operating systems, frameworks, etc.) for every of your previous jobs.

If you add an overview about the technologies you used in your resume, make sure you add your key technologies first (for example: programming languages: Java, C++, Scala, Pascal - if Java is your primary coding language, followed by C++).

Some resume reviewers (like me), like to have kind of a short summary (5-6 lines) in your resume as well. Describe quickly in what you are experienced and in what you are interested in.

Overall, your resume should not be longer than 5 pages, depending on your experience, layout, etc. this is a bit flexible of course. 

I also recommend to read the book "The Google Resume":

 

This is extremely helpful lecture - not just for applying at Google! 

Coverletter:

It's pretty simple, most guys who review applications review the resume first. If this is convincing enough, you don't need a coverletter. If it isn't convincing enough, most of them will not even open your coverletter.

In general, every company is treading this topic different. I personally recommend to spend more time in customizing your resume , than creating a cover letter.

3. Take ownership

- This is not a "must-do", but I often made the experience, it could be an advantage if you email your contact person (recruiter) from time to time about the current status. On the one hand you express your interest with that, on the other hand you make sure not to loose time for any reason. But, do not stress your recruiter, if he told you, he will come back to you as soon as he got new information. Except there are some weeks in between...

- Be honest with your recruiter! Often they have the possibilities to find flexible solutions if necessary for everything. So if you need some time to prepare for the interviews or you have specific questions about it, feel free to discuss them. If you have another offer and you need to make a decision, discuss that with your recruiter.

4. Prepare well for your interviews

This might be the most important part! At this point the company you applied for, is considering you as a potential candidate! This basically means, if you now confirm there expectations or even overachieve them, you will most likely be hired...

So don't miss that chance, because of some social events, movies in TV or whatever. 

Review your application, the company profile, their products, recent news about the company etc.

Also review your documents from your studies and last trainings, if they could be relevant, do exercises (e.g coding), if necessary, review your own thesis and prepare whatever you think you should/could prepare. 

Remember, you should already have asked your recruiter what exactly will happen in your interview.   

If you are a software engineer, the following links might be helpful for you.

5. You want to apply for a job at Google?

Send me your application to andreaslein@google.com