shell geyser
I like the bullet points because they convey what you did, the impact of what you did(metrics), and also the technologies you used to make the impact
But here are a couple suggestions:
- The bullet points contain a lot of technical jargon and recruiters(or even engineers without the necessary experience) will have a hard time digesting each one. One thing that I think would help make your impact more digestible by readers is by beginning each bullet point by stating the impact you made in simple terms, and then ending the bullet point with how you made the impact along with the tech stack(this part can be more technical). For example, for the third bullet point, I would rewrite that as:
"Enhanced up-to-date documentation accessibility for all teams by implementing system to generate YAML file for Swagger documentation during Docker hot reloads"
In my opinion, the above bullet is friendlier to most readers
- Something I've seen in a lot of successful resumes is bolding key technologies within the bullet points. I think this helps a lot especially for non-technical recruiters that are looking for resumes with their target technologies. So make sure you bolden terms like TypeScript, SQL, etc.
restive breach
serene gyro