#8 YOE Review - Am I selling myself poorly?

1 messages · Page 1 of 1 (latest)

scenic sand
#

I'm looking for a job at the senior level at a bigger company (not necessarily FAANG or FAANG adjacent, but something with structure and growth opportunities).

  1. Is my format and content ok? I wanted an interesting looking format but now I'm wondering if I'm harming myself with the bigger companies' bots. Also unsure if using "Architect" in the title is hurting me. I don't have an official title, I can say whatever I want there.

  2. Should I be looking at mid-level or senior roles? I feel like I'm in a weird spot where I'm overqualified for mid-level jobs but underqualified for team lead roles.

  3. Should I remove my side hustles (the two part time gigs listed)? I wanted to show those off and I learned a lot from them but I don't know if they add value or are a distraction.

Screen_Shot_2022-08-17_at_9.30.39_AM.png
errant aspen
#

i would change the format, you have so much wasted space on the left side ! 😦

#

and tbh nobody really cares about an interesting format (unless you’re in like a UI/UX field). Whats interesting to them is the YOE, which you have !

#

i would change to maybe “jakes resume on overleaf” (can google that or navigate to the pinned post and google doc and its in there) or a format somewhat similar to that.

#

in terms of the actual content, give me a moment to look through

steel roost
#

What role are you looking for? SWE?

errant aspen
#

^ good question!

#

“Created and maintained a full stack…”

  1. can probably drop the bit where you re-mention that its for the cloud services team, its a bit redundant and not THAT important to re-mention anyway.
  2. you say full stack but the only tech listed is react, what else did you use? this will be helpful if you are trying to move towards swe
#

“ Lead small team of engineers”

  • Lead team of X engineers, ensuring work completion and finding solutions for problems when they arise.

just a consideration to change it to something similar to this. Main difference is maybe being a bit more concise with the language, like removing “small” and removing the unnecessary pronouns (their, them).

#

the first bullet of senior architect for CDC could be more concise. I think the things you mention could probably be saved for the interviews. For example, I think you can dwindle down the phrasing to sound something like

“Created open source tools to increase adaptation efficiency of new technologies and resourcing the public for …”
—————————

#

full stack dev

feel like you can drop the last sentence in first bullet, seems a bit redundant.

“used node…” feel like this could be two bullets:

  • Built and deployed to Docker containers to Google Cloud Platform using NodeJS, Python and Kubernates.
  • Created a communication pipeline between deployed microservices using Kaftka.
#

your last (or oldest) full stack dev position also seems to have a bit of fluff in it. Last bullet is fluff, 3rd bullet, half of it is fluff (if youre being chosen frequently, i think we can safely assume its because youve shown good ability to do the task well), i believe the first part speaks for itself.

First bullet, you say full stack and then you say “supporting front end back end ..” , this is redundant as its kindve expected that this will be happening when developing full stack applications. You also dont really mention any programming languages or tech used for these pages.

#

as for ur questions

  1. u can go for senior, theres really not much harm to do so. If anything, let the company downgrade you to midlevel or whatever, dont downgrade yourself.
  2. nah i think theyre fine
#

you also have zero metrics for all of your jobs. You should sit down for a couple minutes and try and think about sny numbers you can add to these job experiences. You did all of it for a reason so what was it? To increase developer efficiency by 20%? save a company thousands monthly? increase reliability and scalability? etc etc

scenic sand