In general, I think the following rule applies to any tech company:
1. Keywords present or CV goes to trash
2. Good intro (2 lines) at the top of CV. Good structure (don't list a "Skills" section just hanging around alone. Put the skills you have used next to the jobs in which you have used them). Don't say "Used Java and K8s and CI/CD to build microservices" but "Built a microservice to handle incoming email requests from a third-party company" (or something better). This is for Engineering Managers who read CVs (not all of them read CVs)
3. Good layout/fonts. If your CV looks like it has been generate with Latex or similar, that leaves a good impression. This is for Engineers who read CVs (not all of them read CVs)
So, in general make sure you know that your CV is going to pass through all the layers tech companies have nowadays (e.g., if your CV is the most strucutured and beautiful latex-generated CV in the world, but it doesn't include any of the keywords HR is expecting -> it goes to trash)
Comments
In general, I think the following rule applies to any tech company:
1. Keywords present or CV goes to trash
2. Good intro (2 lines) at the top of CV. Good structure (don't list a "Skills" section just hanging around alone. Put the skills you have used next to the jobs in which you have used them). Don't say "Used Java and K8s and CI/CD to build microservices" but "Built a microservice to handle incoming email requests from a third-party company" (or something better). This is for Engineering Managers who read CVs (not all of them read CVs)
3. Good layout/fonts. If your CV looks like it has been generate with Latex or similar, that leaves a good impression. This is for Engineers who read CVs (not all of them read CVs)
So, in general make sure you know that your CV is going to pass through all the layers tech companies have nowadays (e.g., if your CV is the most strucutured and beautiful latex-generated CV in the world, but it doesn't include any of the keywords HR is expecting -> it goes to trash)