Ask HN: Why is it so hard to move from DA to software engineering?
I am a senior data analyst and I have been trying to move into a ruby/rails software eng role for more than a year now without success and it's frustrating. I went to engineering and business school, did a rails bootcamp and was among the best there, built and shipped to production two web apps www.discute.co and www.rimbaud.ai, created a ruby gem (https://github.com/fsndzomga/mistral_rb) and worked on plenty other projects in python, javascript. Yet no one wants to hire me as a software engineer. It is really frustrating. What kind of level of talent should I demonstrate for people to ever take me seriously and give me a chance ???
(
11 comments
| 2 points
| on HN
)
So rather than focusing on your newer engineering skills, you could focus on roles where your DA and business skills will enhance the engineering and make you more appealing than the others. Finding those roles is not going to be about the coding, but about your subject matter knowledge - look for roles where the coding supports DA or business processes. Or where the subject matter of the product matches past industry experience.
I do't blame them either because the difference between experienced and non experienced developers is bit hard to explain.
If you must switch - better would be to find some junior positions and stick to that position for a few years (3 years or so) and then gradually move up.
This is especially relevant if you're wanting Ruby jobs over a more mainstream language.
It's not about showing you're competent, it's not about being able to say you went to a bootcamp. It's not about listing the same AI projects that everyone else is doing on a piece of paper.
Seriously. Get to know people who are working in the ecosystems you want to target, and figure out a way to make them like you. That's all this economy is about. Raw skill is useless. Resumes are useless. Just get friends.
You claim DA skills -- in what industry?
You have an engineering degree? in what field??
If I were hiring for a ruby/rails SE, I don't see anything that anything that is relevant. I would be concerned that you are "too senior" for a junior SE role.
The only way to break the deadlock is to target companies where you can demonstrate domain expertise and have a number of specific, quantified examples of your contribution which would also benefit your target in comparable situations.