You don't say what it means for you to have under-emphasized it, or what the consequences were, but my changes mostly consisted of changing the preamble of my resume to be clearer that I was willing to take dev jobs, though I was really only likely to apply in "sciency" roles.
When I said I was disappointed when I didn't get the job in the story above, what I meant was that I was disappointed that they didn't offer me the SWE job, and I kicked myself for telling them I didn't want it. But really I only knew that I wanted it after I didn't get it.
Wouldn’t hurt. (The key thing is; have you done work which involved serious linear algebra? I was an electronic structure person, so I’m not familiar with the geophys stuff.)
I would very much be interested in this but there's nothing in my CV that suggests that I'd be good at it, except for some basic electronics I did for fun.
Thank! I actually worked with people in that article :) Now I'm based in Europe so my grad school friends work at companies in a different continent, so so far, no luck there.
This is a good suggestion and probably the most realistic path. The only trouble is that I'm in a small-ish city in Europe and have to work remotely, which makes networking hard. I worked at a company where I sort of tried to do this before but it was really hard to have casual connections with science people.
> As a hiring manager, if someone shared a profile of a person with a PHD in earth sciences and 8 years of “full stack” experience I’d immediately assume they were a generalist with surface level familiarity and no mastery or depth in any one area.
I learned that the hard way. I used to think my science background as an asset but I stopped mentioning my science background after seeing people's reaction in interviews.
