I am quite concerned that Doctors in the medical field have limited to no understanding of statistics. IMO, stats should be second nature to anyone with 200 level math courses.
Regarding doctors and stats, I share your concern. But I disagree with the statement that stats should be second nature to anyone that's gone through the courses. If I've learned one thing while going deeper and deeper into stats, it's that there's a lot more nuance than I originally understood, and I'm still not there. Just when I think I have a thorough understanding of p-values and the like, I'll read some "I can't believe everyone doesn't understand THIS" blog and see that there was more to the story still again. It's hard to know what you don't know.
0.9% are 100-200 level math problems.
0.1% are beyond that, but at that point, hopefully your 200 level skills have taught you enough to learn about solving that.
In my lifetime, I only had 1, beyond 200 level problem that required research on math to understand. And technically, it was optional, but I volunteered.
Everything else was algebra.
An exception might be if you see "Publications in top-tiered journals" as a requirement. Those positions likely actually target PhDs with relevant publications. They might overlook a lack of a PhD if you're a recognized expert in the field, of course. But I interpret this requirement as "we want an academic", and there primary job is likely research and publishing papers. A Research Scientist at AWS is not an academic, as someone at Google Brain might be, but rather someone building applied ML solutions.
But if you happen to have those things without a PhD, then do apply anyway and I'm pretty sure they'll be interested.
If you don't have those things, then you may not be ready for these kinds of jobs.
There are several very successful academic and industrial CS researchers without PhDs - Simon Peyton Jones for example - so it can be done.
To get into RS position, just know your ML/stats basics well and be proficient in SQL. Nothing super hard about getting an RS role.
Although, it's conceivable that being both ABD and not specifically in CS is seen as a bridge too far.
Not sure if this is a reason for or against.
It's true, but I'm glad it happened this way. I don't want to work at any company that doesn't recognize the value of this degree. I'm a SWE in a FAANG now, and I think I do much more interesting work than if I had just joined a company looking for a CS grad. And to be clear, I only have a Ba.
But, advice to other EngPhys grads looking for jobs or internships: don't mention the Engineering Physics degree until you've got the rep interested in you (by talking about experience, etc) or frame it in a different way. For example, my EngPhys specialization was computing, so I would talk about that first when I was at career fairs.
I love engineering, but physics is often theoretical to the point that its useless for macro application.
I imagine an Engineering Physics is an Engineer.
Heck, this distinction is even made when you enroll in the Master's program in Stanford CS instead of the PhD program. They are treated as different tracks that you can't move between.
One possible reason is that grad student funding was limited, and they didn't want to waste it on students who weren't going to contribute to research. All physics grad students were fully funded. I'm not sure this is true today.
So far as I could tell, this was strictly limited to physics. My graduate program was almost exclusively PhD students, and the terminal Master's was used as an escape hatch. On the other hand, those students did just fine in the job market, so it could be just a peculiarity of the academic culture that is not reflected outside of the academe.
Working in industry after my degree, I encountered people with Masters in physics, who were doing just fine, and they did not strike me as inferior -- they just didn't want to stay for a PhD.
It could be on behalf of their employer - they have a shortage of a certain class of student at the university.
or it could like engineers who too easily recommend extremely over-powered computers for friends and family not in the industry who are thinking about buying a computer.
My own college didn't have a graduate program. This was based on multiple advisors having similar expectations about applying for grad school.
I have been able to utilize my understanding of physics to work on things like designing sensors into products that require real world math (motion, position, motor control, etc), though not as extensive as it could be if it were academic research. And have used my circuits foundation to understand how to get answers in the realm of embedded micros.
The thing I emphasize the most though, is understand where you want to have an expertise and make it happen, work on it. Mine is embedded software with a user focused design process.
Fresh out of college, your degree is not going to separate you unless it's coupled with experience from internships, school projects, or personal projects.
My opinion is that a degree in engineering provides foundation, but real world experience is where you grow and learn for your career.
Side note: You mentioned "other than learning code", I think that is a valid option to supplement this degree. I started writing code in eighth grade, so it was something I was already doing and interested in. I never wanted to be a plain ol' software developer, so this path was good for me.
TL;DR Went to school for Engineering Physics, I am happy with my career path, but took it upon myself to find a way to provide value beyond the name of my degree.
Oh, you resonate with me (not sure if. I am going to start an undergrad in physics soon, and started doubting my choice after this thread. I got into programming from 9th grade. I am still interested in it, but I kinda grew over my crush on being a dev in FAANG and silicon valley startups. I have the opportunity to got to a SE program, but I don't like the lack of humanity(and other) electives in eng programs. I am also accepted to a CS program, but the school with the physics-math program have a better name and opportunities around it. The CS program is in a mainly-undergrad school in a suburb-ish city.
Do you think I would still be good sticking with physics and complement it with personal projects and CS electives/minor? (This is Ottawa, Canada)
Where I went to college, all engineering physics majors concentrated (which is essentially a minor) in one of the other engineering disciplines (mechanical, electrical, civil, computer science, etc).
If you want to work on digital only products that don't utilize what you learn with a engineering physics degree, then you may want to consider another degree.
I can't speak directly about a physics only degree, since I did engineering physics, where I took all of the same core classes as engineering students.
Motivation, experience wherever you can get it, and knowing people / networking, will get you pretty far, so I would also say, take the path that's interests you the most. Also, physics is hard.
They're different people. And a lot of then value living their lives over slaving away and are OK with that.
Students who do a Master's before going on to Ph.D. are usually more competent and more useful to the university. This is FUD created by graduate students to prevent competition.
Oh, and a bachelor's in engineering physics seems to lead to nothing as well. Have had quite a few friends go to career fairs and every company rep lost interest as soon as they heard the words "engineering physics". They just went on to grad school in plain old physics since they had 0 other options besides learning to code.