From Petroleum Engineering to Data Science: Nobody Plans a Career Like This

I started college as a nursing and pre-med student. I am now a doctoral student in Computer Science building graph neural networks for drug discovery. If you had told eighteen-year-old me this is where I would end up, I would have had no idea what half of those words meant.

But that is the thing about careers. The interesting ones are never linear. And I think there is value in telling this story honestly, because a lot of people in data and tech feel like they need a perfect origin story. Computer science degree, internship at a FAANG company, straight shot to senior engineer. My path was nothing like that. And I think it is better for it.

The First Pivot

I started in nursing and pre-med because, honestly, that is what a lot of people around me were doing. It seemed like a solid path. But somewhere along the way, I realized it was not where my mind naturally went. I was more interested in the analytical side of things. I liked solving problems with numbers, not memorizing anatomy.

So I made what felt like a massive decision at the time. I changed my major to petroleum engineering and transferred schools. This was when petroleum engineering was booming. The demand was high, the salaries were incredible, and the future looked bright. It felt like the smartest pivot I could make.

The Dean's Warning

I remember this moment like it was yesterday. It was my final semester at the University of Wyoming. We were close to graduation, and the dean called us in. Not for a congratulations speech. Not for career advice in the traditional sense. He told us, in so many words, that it would be best for students in petroleum engineering to consider changing their major. Because there were not going to be jobs.

The oil industry had crashed a couple of years earlier, and the job market still had not recovered. The same industry that was in high demand when we enrolled had completely dried up by the time we were about to graduate. Years of engineering coursework, and the industry had pulled the rug out from under us.

I remember sitting there thinking: I just changed my entire career path to get here, and now they are telling me to change it again. That was a hard moment. Really hard.

The Oil Field and What Came After

I graduated anyway. Got a job working in the oil field, because that is what was available. I went in with the hope that things would turn around, that the industry would recover, that the work would lead somewhere. And I learned a lot out there. But I also knew, deep down, that this was not going to be the long-term answer.

During that time, I started hearing people talk about data. Data analytics. Data science. And something clicked. Because looking back, I had always been a data person. In petroleum engineering, we used MATLAB for analysis and modeling. We lived in Excel. I was always the one who wanted to dig into the numbers, find the patterns, figure out what the data was telling us. I just did not have the vocabulary for it yet.

So I made another pivot. I enrolled in a master's program in data analytics at Maryville University. And that was when everything changed. Not overnight, not dramatically. But steadily. I finally had a name for the thing I had always been drawn to.

The Lesson Nobody Teaches You

Here is what I wish someone had told me earlier in my career: never wait for a company to invest in your growth. Never rely on an employer to pay for your certifications, to send you to conferences, to keep your skills current. If they do, great. If they do not, that cannot be the reason you fall behind.

The data field moves fast. Unbelievably fast. The tools I was using five years ago are not the tools I am using today. Databricks, dbt, Delta Lake, PySpark at scale. If I had waited for a company to teach me these things, I would still be writing basic SQL queries and building Excel reports.

I have worked at companies where they had the tools and did not know how to use them. I have worked at companies where they were so comfortable with their legacy systems that they actively resisted anything new. Legacy bureaucracy, I call it. The kind of environment where suggesting a better approach gets you a polite smile and a reminder that this is how we have always done it.

Those environments can be suffocating if you let them define your ceiling. So I stopped letting them. I started investing in myself. MIT Applied Data Science certificate. Northwestern Product Management program. And now a doctorate in Computer Science. Not because any company told me to. Because I decided that my career trajectory was my responsibility, not my employer's.

Work Harder While Working Smarter

There is a phrase I come back to a lot: work harder while you are working smarter. It sounds contradictory but it is not. Working smarter means finding the tools, the technologies, the approaches that let you do your job more effectively. Working harder means putting in the effort to actually learn those things, even when nobody is requiring you to.

When I started learning PySpark, nobody asked me to. When I got into Databricks and dbt, that was on my own time. When I built the Anomaly Detection System and the Privacy Analytics Platform, those were not work assignments. They were projects I built because I wanted to prove to myself that I could ship real products, not just write reports.

And every single one of those investments paid off. Not immediately, not always in the way I expected. But consistently. The certification I got on my own dime became the skill that landed me the next role. The side project I built on weekends became the portfolio piece that showed what I could do beyond what any resume could describe.

The Non-Linear Path Is the Path

Pre-med to petroleum engineering to oil field work to data analytics to data engineering to leading teams at Fortune 500 companies to doctoral research in graph neural networks. That is not a career plan. Nobody draws that on a whiteboard during a college advising session.

But every step taught me something the next step needed. The analytical rigor from engineering. The real-world grit from the oil field. The technical foundation from the master's program. The leadership lessons from managing teams across industries. The research discipline from the doctorate.

Your path does not have to make sense to anyone else. It just has to make sense looking back. And if you keep moving, keep learning, keep investing in yourself, it will.

If you are reading this and you are in the middle of your own messy pivot, whether it is switching from a completely different field into tech, or wondering if that certification is worth the money, or sitting in a job that is not using half your skills, I want you to know something. The pivot is not the setback. The pivot is the story. And the story is what makes you different from everyone else with the same tech stack on their resume.

Nobody plans a career like mine. And I would not trade it for the linear version.

Previous Post Back to Blog