Music to Public Policy to Tech. That’s the path I took to get into data science. It’s not the most direct route, but every stop taught me something I use daily as an engineer and product builder.
Music: Practice Makes Progress
I started as a music major. The single most valuable thing I learned was that skill is built through deliberate, daily practice — not talent, not inspiration.
Coding works the same way. The people who get good at it are the ones who show up every day and write code, debug code, read other people’s code. There’s no shortcut. When I was learning Python and SQL, I approached it the same way I approached scales and sight-reading: repetition, incrementally increasing difficulty, and honest assessment of where I was weak.
Music also taught me to perform under pressure. Recitals and auditions have a lot in common with demos and presentations — you prepare extensively, then you execute in a moment where there’s no redo.
Public Policy: Communication and Statistical Rigor
I moved into public policy, where I picked up two skills that turned out to be career-defining.
First, communication. Policy work is fundamentally about taking complex analysis and making it understandable to people who will act on it. This is exactly what data science requires. The best analysis in the world is worthless if you can’t explain the findings, the methodology, and the implications to stakeholders who aren’t technical. I learned to write clearly, present confidently, and tailor explanations to my audience.
Second, statistical thinking. Social science statistics and econometrics are rigorous in ways that transfer directly to machine learning. Understanding experimental design, causal inference, confounding variables, and the difference between correlation and causation — these fundamentals matter more than knowing the latest framework. When I eventually moved into ML, the conceptual foundation was already there.
Tech: Working Smarter
When I finally made the jump into tech, the pace was a shock. Tight deadlines, shifting requirements, and the constant need to prioritize. But the adjustment taught me to work smarter — to automate repetitive tasks, to invest time in tooling that pays dividends, and to say no to work that doesn’t move the needle.
This mindset eventually led me to AI-assisted development. I’m not just using AI tools because they’re new. I’m using them because they’re the logical extension of the “work smarter” principle I learned when I first entered tech. Every hour I spend setting up an automation or learning a new tool is an investment that compounds.
The Unconventional Advantage
The through line across all three careers is this: the best work happens at intersections. Music gave me discipline and performance skills. Policy gave me communication and analytical rigor. Tech gave me execution speed and a bias toward automation.
I wouldn’t change the path. The people who take unconventional routes into tech often bring perspectives that are missing from teams built entirely of CS graduates. If your path looks different, that’s not a weakness — it’s what makes your contribution unique.