[shawnfrompdx]

thank you for taking the time. If i was petty i could share the past 5 versions of my website and resume i created in the last year which precisely followed most of what you recommended here. I had a completely vanilla narrative resume by version 3, and was getting nowhere. analytics and my own vibe check was making me think that all of that was too verbose and it wasn't being read. I was feeling unseen and began retargeting things to create an impression in 2 seconds, enough to hopefully hook someone to want to talk to me to learn more. the latest strategy was to try to emphasize within 2 seconds the point that im all about ai coding, while having a conventional cs/agency background at the same time.

Because you have taken the time to review this stuff and make these same recommendations that everyone else has here, i am going to refactor the site and resume yet again according to these recommendations.

I would love it if my career arc had one through-line narrative that made sense, but I'm afraid it doesnt necessarily. I started as a data architect and backend developer for the first many years, never touching front-end. I had to expand to tackle front-end to meet the changing market demands. in later years, the distinction of what were primarily front end vs back end tasks or roles has become a lot more fuzzy, as things have turned into "all-js-all-ts-everything-everywhere!" I've adapted, and been working full stack ts roles.

I often feel my data architecture / problem-solving skills are overlooked when my last few roles show that i've been developing with a vue ecosystem, pigeonholing me as a front-end dev, something i have never identified with.

[aembleton]

It might be good to expand on your data architecture work more in your CV. Write a paragraph about the data architecture work you did at your last company. You could remove some of the older jobs to free up space.