[iteria]

Are you sure you aren't an expert? For me, i sell myself as "generally speaking a full stack developer based in dotnet and whatever for datastore and frontend, but also I've done 4 other middle tiers" I'm never the most knowledgeable in anything, except whatever the team is transitioning to. My specialty is codebase transition and requirements gathering. I'm the person you call to migrate from dotnet to $thing or from $thing to dotnet. I'm the person you hire because you need an engineer to talk to highly technical people in a different domain and try to translate their very complex asks into something you can deliver.

I'm job searching right now and while it's not where near as res hot as before, I'm having no problem gettinf interviews. I just have some requirements that make me a bad fit for a lot of companies like I must be remote.

I'd say look at what you've done and figure out what your specialty is and sell that. There's more to specialties than tech stack.

[throaway1991991]

Thanks for sharing your response. I like the idea of having a specialty in specific membranes like migrations or accentuating my requirements gathering work and soft skills, and building a reputation as a team lead or designer. I dread the thought of EM but that might be a relatively safe bet once I tighten up my resume and pitch.