I'm hiring a senior full stack engineer with more than 6 years of experience.

I'm hiring a senior full stack engineer with more than 6 years of experience. I'm a software engineer that's been writing code for more than 10 years, and I run a startup backed by Google and the former co-founder of Twitter. In the past few days, I've looked at more than 300 applications and CVs, and these are three things that you should include on your CV if you want to stand out for a software engineering job. By the way, make sure you follow if you want me to help you on your programming journey. Let's start off with the most important thing that you need to do. This I thought was quite basic, but it's surprising how many people made this mistake. You need to make it super easy for the person looking at your CV to quickly understand your experience. That is to say, when it comes to listing out your work experiences, each one should have bullet points of exactly what you did there, and ideally avoid passive words, things like assisted, contributed, helped. I want to know as an interviewer exactly what you did and what you led on. The other thing is make it super easy for me to understand how long you've spent at a particular company. In bracket, put the number of years and months instead of me having to look at the dates and calculate that myself. That might sound silly and pedantic, but I'm looking at more than 300 CVs and make the assumption that many people will be applying for a job, so just make it a bit easier for your interviewer. Now, if you're applying for a full stack position, it's nice to have a quick summary at the top. A full stack engineer is expected to be able to work on the back end and front end. And depending on the nature of the company or the work experiences that you might have done in the past, you may have focused on one over the other more so, and that's not necessarily a bad thing, but that's just the nature of the position or the work that you are required to do. Now, in the summary, it's quite useful for me to understand how much of your focus is on the front end or back end. A summary on that top detailing that is quite useful for me. It can be in the form of saying that you've worked 3 years on the front end and 2 years on the back end, or it also can be a percentage split. Having that at the top is going to make it easier for the interviewer to understand your experiences as a full stack engineer. This is the last thing, and it's more of something that you shouldn't do. I understand these days that many CVs go through a number of recruitment tools, and these are automated tools that look out for keywords on CVs. As a result, I saw many CVs listing out more than 30 bullet points of every technical skill you can imagine. They listed out HTML, CSS, PHP, you name it. Now as an engineer, I understand and I do encourage doing this in some way, but don't make it an obvious bullet pointed list. Try and spread it around by highlighting exactly where you focused on said skills in your experiences, or apply some kind of scoring matrix to highlight which skills you're better at than others. Make that section useful instead of just listing a bunch of keywords. Now, this is a bonus tip, and ideally I don't want to be telling you this, but again, I've looked at more than 300 CVs and I'm surprised how many people still get this wrong. Make sure you spell check and use correct casing. There are so many CVs that I looked at where people made basic spelling mistakes and on top of that casing was also off with certain words. As software engineers, we care a lot about writing good quality code and we care a lot about the work that we do. Put that same care, emphasis and quality in your CV. A CV is meant to be a representation of your skills, experiences and essentially you. Take that extra effort to make it look really good and stand out. You're going to do it once and maybe change it here and there, but on the whole it's going to stay the same. So avoid the basic errors like spelling mistakes and casing issues, and ideally if possible, spend some more time to make it look good. Save this so you can come back to it. And if you stayed until the end, I know that you've got a good attention span. So if you do have more than 6 years of experience as a full stack software engineer, ask me for the link to apply in the comments below. If you found this helpful, follow for more.