Live data from Hacker News

Ask HN: How do I bridge the gap between PhD and SWE experiences?

news.ycombinator.com

31–40 of 69 posts

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#31
post #22

“Bridging the gap between PhD and SWE” would be a good subtitle for my career. I started out writing software for scientists, psychologists, first at a university, then a small company. After eight years of that I went to grad school and got a PhD in CS (ML/AI), and did a postdoc, before going into industry, and eventually landed a role in what was then called “data mining”, later “data science”, then “machine learni…

> I’ve been out of the job market for 15 years now

Wow - that's a long time at one company, or being without a job. Could you share more on that? Simple curiosity, thanks.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#32
post #23

I would use your software skills to get in the door as a software engineer, then weasel into a sciencey position. That is: 1. Find a company that has non-software jobs that you like. Look at what companies advertise on their web sites; go to a few conferences (or watch talks) to see if some talks strike you with "ah, I can and want to do this" vibe; reach out to folks you went to grad school with, etc. 2. Apply and j…

Good point, get into the right company and move to a place you like. I did that way back moving from lab to customer service (right company and right country) to get into the R&D I wanted. Easier to execute in a company that is rapidly expanding.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#33
post #30

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’d then look over the profile trying to disprove my assumption. Lacking a very strong signal in mastery of something, I’d pass on the profile. Only at small scales are full…

> Only at small scales are full stack engineers valuable.

Seems like the ideal career is to start somewhere big and successful enough that allows you to specialize (after some poor generalists sabotaged their own careers by making it a thriving environment for specialists). Because even small scale businesses think they should start by hiring specialists.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#34
Personally I don't have a PhD, but do have several advanced degrees. From experience, I'd suggest look into deeptech companies that are looking for SWEs. Deep tech companies typically need folks with the ability to pursue scientific enquiry with a SWE / Product mindset.

I work at a company that is hiring folks that have a background in (helio)physicists / quantum (I think we have about 3 nobel prize labs represented right now in a team of 9) with SWE / ML experience (EDIT: and Full Stack Developers), to build products for the aerospace industry. Not exactly earth science, but if Heliophysics / Physics is of interest, my masked email in profile.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#38
Consider laboratory automation?

I work in that now. I am going through the same issue as you after studying science (there are many of us!). Jobs rarely overlap, wanting both skillsets. Am I ever going to do this scientific work I learned about? I feel entering this area has been progress.

I'm on the 'science' side right now, after doing CAD, software and firmware for a few years. The previous robots I made were not for scientific work. Now I make liquid handling robots for laboratories and I hope that my scientific skills will be valued in the workplace.

In the workplace, people mostly seem to want you to choose a box and stay in it rather than using a varied skillset. Right now I can say I "make robots" but mostly I take parts, put them in the machine we make and use them for a bit then send them on their way as tested items. The robot is largely a black box - I'm not allowed to see the CAD, software or firmware it runs, certainly not use my skills in those areas. But I'll keep trying - to bring value to the employer and find more interesting/valued work using the skills I've gained over the years. Entering a workplace for whatever they want then moving within it over time is a time tested strategy, especially in government because they are unionized and very rarely fire anyone.

Keep in mind funding sources during your search. In Canada we have SRED, which is a tax rebate for scientific work and easy to get. People, even if they studied science, seem to perceive scientific work as expensive and mostly useless so subsidies like this really help. Since it's a rebate that means you must work for a company that already has revenue, not a small startup. Look for a company with at least a room they call a lab and they will keep time sheets for all "R&D" work.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#39
I happen to have a background at this interface as well, as the founder of DeepEarth and Ecodash.ai. I can tell you that I would greatly value such experience in collaboration, although I am not currently hiring. While having such a specific interdisciplinary niche can feel limiting, I also see it as a potential superpower in excelling in a very important domain. I'll also add that machine learning and other modeling techniques are a great bridge between classical natural sciences and modern tech today, that I would look for in collaborators. More specifically from the earth sciences, "GeoAI" would be a key focus.

Re: Ask HN: How do I bridge the gap between PhD and SWE experiences?

#40
post #23

I would use your software skills to get in the door as a software engineer, then weasel into a sciencey position. That is: 1. Find a company that has non-software jobs that you like. Look at what companies advertise on their web sites; go to a few conferences (or watch talks) to see if some talks strike you with "ah, I can and want to do this" vibe; reach out to folks you went to grad school with, etc. 2. Apply and j…

This is the way. I've seen this successfully done many times. The barrier to entry is much lower once you already work at a company and just about everybody needs more software engineers than they can find.
Post reply on HN