Earlier quoted context omitted.
Not sure if this is sarcasm, but people aren’t machines. My reply rate rose considerably by changing from my first(unique) name, to my middle(common) name. People judge, if you’re going for a new job why give them any chances to ding you?
So, should black candidates bleach their skin because "people are not machines"? Making excuses for wrongful prejudice only perpetuates the prejudice.
Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
121–130 of 142 posts
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#122I've hired about half a dozen ML engineers/architects in the past six months. Several of them have EE backgrounds. There's a good bit of ML that touches on hardware (think integrated cameras and similar) so it can be really helpful. You're mostly on track with your plan to build something. You do need to demonstrate that you have the skill set, but building one giant thing isn't the answer. There's so much that goes…
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#123Earlier quoted context omitted.
Random side note, but when is the 'FAANG' acronym going to die? MSFT is killing it, prob the top tech company around these days. Needs to be included in that list.
FAANGMUA is the latest I've seen...Microsoft Uber AirBnB, I believe.
Linkedin, Cloudera, Redhat, Quora, Robinhood, Asana, Salesforce, Dropbox
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#124Earlier quoted context omitted.
Great reply. My question based on this comment, >My advice is assuming you’d like to be a person that trains/deploys ML models to solve problems in industry. This is much different than an ML Engineer, who’s implementing algorithms in low level languages and squeezing out efficiency. Obviously that would require a much deeper understanding of SWE. And a totally different person is an academic researcher that’s develo…
I think it’s unlikely to become expert in all of those things. If you do, it’s over the course of an entire career, not to get started. I guess it comes down to how much expertise is “enough” for you. Naturally, if you split your time across 3 domains you won’t be as expert as someone who dedicated all their time to going deep in one. In the context of a big company, I think it makes sense to have a specialized workf…
I suppose my question is more along the lines of, if someone is specializing in deep learning in a PhD program then shouldn’t they at the very least be able to implement models and also know optimization tricks?
In other words shouldn’t they be able to develop enough skills to go deep in one area but also know enough to be dangerous in the other three domains?
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#125I basically did what you’re talking about. Masters in physics, then went into semiconductors as engineer and materials scientist, then switched to Data scientist at a bank for 18 months, and now have been a research scientist in AWS for almost two years. In Amazon, it’s easy to move around, but not between job families. I think it’s a bad idea to join as a SWE and try to transfer because they want people that have do…
I am deep into semiconductors, and am facing the dilemma of giving up my expertise so far, to join a startup as an entry level engineer.
I have done a couple of MOOC specializations and am trying to find projects within my industry to gain some credibility. Also trying to stay active on Kaggle to build some basic data analysis portfolio.
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#126I have a PhD in EE, working in semiconductors. I have done a couple of MOOC specializations on Coursera, and am trying get some data science projects on my resume. Also trying do some Kernels / Scripts on Kaggle to build up a basic portfolio.
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#127Hi, I am in a similar boat, and would love to network with you either in person or online. I have a PhD in EE, working in semiconductors. I have done a couple of MOOC specializations on Coursera, and am trying get some data science projects on my resume. Also trying do some Kernels / Scripts on Kaggle to build up a basic portfolio.
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#128I basically did what you’re talking about. Masters in physics, then went into semiconductors as engineer and materials scientist, then switched to Data scientist at a bank for 18 months, and now have been a research scientist in AWS for almost two years. In Amazon, it’s easy to move around, but not between job families. I think it’s a bad idea to join as a SWE and try to transfer because they want people that have do…
Great reply. Just out of curiosity, did you end up giving your semiconductor job before joining the start up with a data scientist title ? I am deep into semiconductors, and am facing the dilemma of giving up my expertise so far, to join a startup as an entry level engineer. I have done a couple of MOOC specializations and am trying to find projects within my industry to gain some credibility. Also trying to stay act…
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#129Earlier quoted context omitted.
Random side note, but when is the 'FAANG' acronym going to die? MSFT is killing it, prob the top tech company around these days. Needs to be included in that list.
How may I ask is MSFT a top tech company?
Re: Ask HN: Engineers from non-CS background, how did you pivot into ML/AI?
#130Stop focusing on MOOCs and youtube videos and study textbooks. Do exercises. Treat it like academic studying, and you'll end up with a decent education. It's important, because it's often easier to make a thing work okay than to understand why it works, so you'll get false confidence working through a tutorial. But then you want to apply that to something else and it doesn't work quite right, you won't know why it do…
For purely professional purposes, it's probably a better idea to take a non-academic approach.