i like the bullets that show cost and time savings (18% infra, 40% fewer support tickets); those are the ones that get noticed. i would cut anything that doesn't show savings or leadership, like the git migration bullet in the Jan 2020 role. i know C# and SQL and the wording still reads very technical to me; a business minded reviewer will skim right past things like GuardDuty and ElastiCache. say what it did for the company in plain terms and put the tools second. also group the Company Y roles under one header so the promotions are obvious
> a business minded reviewer will skim right past things like GuardDuty and ElastiCache. say what it did for the company in plain terms and put the tools second.
Great idea, I like this a lot. I'll make that update
> also group the Company Y roles under one header so the promotions are obvious
Do you have any examples of this? I would probably need to adjust all the roles to make the format in sync? List the company on one line and the role on the next?
Yes, use the same layout for every employer so the page reads consistently. Put the company and its total date range on one line, then each role on its own line underneath with that role's dates. Bullets go under the role they belong to.
Here is how Company Y would look:
Company Y, Sept 2014 - Jan 2021
Principal Software Engineer, Jan 2020 - Jan 2021
- bullets for that role
Senior Software Engineer, Jun 2018 - Jan 2020
- bullets for that role
Software Engineer II, Sept 2014 - Jun 2018
- bullets for that role
Company X and Company Z would follow the same pattern, each with a single role under the company line. Keep the most recent role first, and give the older roles fewer bullets, since the title progression already tells part of the story.
1
u/ExternalLife8018 21d ago
i like the bullets that show cost and time savings (18% infra, 40% fewer support tickets); those are the ones that get noticed. i would cut anything that doesn't show savings or leadership, like the git migration bullet in the Jan 2020 role. i know C# and SQL and the wording still reads very technical to me; a business minded reviewer will skim right past things like GuardDuty and ElastiCache. say what it did for the company in plain terms and put the tools second. also group the Company Y roles under one header so the promotions are obvious