Answer the question
In order to leave comments, you need to log in
What to write in a resume for a novice programmer?
With an experienced one, everything is clear: we describe our previous places of work, projects, technologies used in them, etc. But let's say that I am a student, I have 0 work experience in my specialty, I want to work. What to write in a resume? I have 2 options:
1) we write in the heading "beginner", in skills we list EVERYTHING that I encountered at the university, starting from C ++ and ending with Matlab and PowerPoint. Those. In fact, we do not care where they will take, if only to find a job. Such a resume, as I understand it, does not make sense to send out to organizations, but hang it out on hh and wait. By the way, this is exactly what many of my classmates did.
Pros : because of all the skills, there will be more resume views, more chances to get at least somewhere.
Minuses: you can receive offers such as concluding contracts with Rostelecom or supporting the site of a store selling lingerie (examples from the same fellow students).
2) we write in the title what we want to develop (for example, a .net developer). In the skills of c#, asp.net, ms sql server, entity framework + horizons (html, css, js), we attach a link to a github with a couple of projects on pure ado.net and some kind of CRUD with an entity framework. And nothing more, so that they pull less ... It's probably already possible to send it to a couple of companies, they say I want to work for you. But damn it, wouldn't it be arrogance? that "haven't worked yet, but you write that .net developer".
Pros : More likely to get your first dream job
Cons : More likely to be out of a job altogether due to fewer options.
Or maybe it's all nonsense at night looking and it should be completely different? What's the best way to do it?
Answer the question
In order to leave comments, you need to log in
passive search is a hundred times worse for a beginner than active
, so send out
calls
, go to interviews
, and it would be nice to make each resume for a separate vacancy
Write what you can do, what you worked with at the university, write what you want to learn how to do, what you aspire to.
Write what you developed at the university or for yourself, or in general what you did was practical.
Write everything about yourself (hard-working, clean, disciplined...)
You don't have to sit and wait, send out your resume, first where you want to work. They will answer, there is either not there, or an interview. If they don't answer, go to other companies.
No need to write anything at all)) If you want to grow in the direction of ASP.NET, then why do you need possible offers related to Matlab and PowerPoint?
From the point of view of the employer:
1. If the resume is written for NM years of experience, but in fact 0 - this is very suspicious.
2. If, again, there are a lot of things, the image of the applicant “blurs”, in the sense: it is absolutely not clear at what level, what he knows and what he is going to do. This is even though you specify the level of knowledge.
3. Projects on github are a big plus, it means that the applicant knows how to git, if there are badges from travis, etc. stick it - it will also be a plus, the applicant knows how to test his code.
In any case, your first job will be for gaining experience and growth, so do not rely on a high salary if there are cool specialists next to you - your growth will be faster. You can find out at the interview and during the trial period (IP is for both the applicant and the company). If you are put on a project alone, this is bad, you will not have anyone to learn from.
Recently I heard about such garbage: "the test period is not paid", if they tell you this, say goodbye and close the door behind you.
Get fit for any job. From the moment you enter, take your time looking for something better.
Create a resume for a specific vacancy. If you are looking for a job as a programmer, then focus on programming skills.
Please note that in large companies, the HR employee looks at the resume first. And they cut off everything superfluous on formal grounds. They have a parser inside their head to search for keywords.
If no one responded to your resume, then most likely no one saw it. In this case, try to contact your boss or team leader. Social media can help you. Boldness borders on confidence. Just don't get arrogant at the interview itself :)
Remember: the task of the resume is to organize the interview, and the interview is your assessment.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question