Tip: Don't load up your developer CV with technical jargon!

If you want to apply for a dev job in a large company, chances are very good that your CV will first go through the HR department before it ends up on the desk of the development department. Of course, the Head of Development or CTO, or the person who defined the ad, would understand the complicated jargon in your application, but it is more likely that the HR person who looks at your CV in the first instance will be able to tell the difference between e.g. does not know ”C++” and “Perl”.

Because of this fact, it pays to keep your resume as simple as possible. List your skills and programming languages ​​you have learned, summarize the projects you have already implemented in a clear way, but save in-depth details for the personal interview.

"I was primarily responsible for identifying technical problems and solving them," is a good summary. "Applied statistical techniques to build and update predictive models for using pricing" can also work well.

But a list like: “Mastery Of Source Code Revelation, Remote File Inclusion, Cross Site Request Forgery (CSRF) or Open Web Application Security Project (OWASP)” might be a bit much. There are too many technical terms without a description, which is why the listed techniques qualify you for the advertised job.

When describing your work experience, you should minimize the number of technical terms when in doubt and instead focus more on how you positively influenced your previous job.

Do you still have the desire to sprinkle technical terms in your CV, simply place them in the "Abilities & Skills" category.