I never planned to work with computers, much less become a Data Engineer. I was a musician. A struggling one. The year was 2021, I was 20, and I was studying Music Composition, writing scores for student films and piss-poor videogame developers while earning a magnificent average of 15 bucks a month.
My journey began not with a career plan, but with a girlfriend who was losing her mind over her Econometrics class. Her biggest enemy? StataCorp and their fuck-ass software called Stata. She ranted endlessly about how the stupid computer would correct her but never auto-fix her errors.
“I’ve always had my way with computers,” I thought. So, I grabbed a pirated copy of Stata MP and started digging in.
The Overture: From MIDI to Munging
I roped my best friend (who was also in the class) into the chaos, and we started tackling the semester’s econometrics project. I began by throwing together some Do-files, following the TA’s instructions, and moving data around.
My scripts were notoriously cautious:
* DONT REMOVE THIS OR IT BREAKS
clear all
set more off
* load the csv (CHANGE THE FOLDER TO YOURS)
import delimited "[...]", clear
The early grunt work was data cleaning, which was about 80% of the project. I quickly realized that the process required intense patience and attention to detail—something I was surprisingly good at. The repetition pushed me into learning my first loops and functions.
The learning curve was steep but hilarious. I spent two hours fighting the simplest concept: the backtick.
This took me about 2 hours to get working. I’d never used backticks in my life, so I was writing ‘var’ instead of `var’, thanks StackOverflow!
foreach var of varlist q87-01 q88 q90-07 { replace `var' = 0 if `var' == . }
My best friend and my girlfriend got great grades, and I found a bizarre new hobby. That settled it: I was the designated programming guy.
The Crescendo: Free Money & Python
After a couple more semesters of painful Stata clean-up, I was exhausted. I searched YouTube and discovered how easy and fun the process was in Python. It felt like pure magic. I’d run a script, and the job was done. I genuinely felt like a hacker.
The best part? The Python community on StackOverflow was a goldmine for pre-made code, making it infinitely easier to handle weird edge cases than it was with Stata.
I finally accepted my destiny and started doing homework for other students (for a fee). It was fun, easy, and made me a ton of money compared to music gigs. I was suddenly tutoring half the class, teaching them how to clean data in R and make 🔥SICK GRAPHS🔥 with ggplot2. My university performance, naturally, tanked.
The Cadenza: ChatGPT and The Detours
I fell deeper into the tech spiral. Python became my go-to for everything: automating homework, miserable early attempts at websites (pure Python + HTML, because I refused to even understand whatever the fuck was going on in the web world), and even programming music using PureData and Max/MSP.
Then came the legendary (and infamous) ChatGPT. It was insane! I could get answers in seconds, boosting my self-education immensely. I even briefly toyed with becoming a videogame developer.
That dream lasted exactly as long as it took me to install Unity and look at a single line of C#, got spooked, and promptly fucked right off that whole scene. I was starting to see how tough it was to be a full-time musician, and how much easier programming was, even if I doubted anyone would pay big bucks for “simple” Python skills.
The Symphony: The Unlikely Pivot
I graduated in December 2023, finally freeing myself from the shackles of singing atonal music and practicing piano 2 hours a day.
The job hunt was brutal. My resume was mostly music and arts stuff. My girlfriend and mom encouraged me to broaden the search into Data Analytics or IT—the kind of jobs you don’t understand until you’re already doing them.
I found an opening at a company called Datawalt, a company I’d never heard of, and applied with almost non-existent experience. I was transparent: my coding background came from helping students cheat on econometrics homework, and had zero formal education in the field.
The interview was hilarious. They asked about my music, my hobbies, and the video games I played. The skill test, however, was a disaster: I got 2/10 questions right. I took it home, hammered it out with a little help from my new best friend, ChatGPT, and sent it back three hours later.
To my absolute shock, that was enough proof, they hired the music composer as an Intern BI Developer.
Within a year, that music composer was leading their first Data Engineering team and designing the company’s main data platform.
What Actually Mattered
Interview: Make them laugh. Show you fit the vibe. Graduates don’t know shit—be eager to learn what they actually need.
Skill Test: Don’t stress perfection. Show how you handle gaps. It’s a taste of the real job, not a final exam.
On the Job: Be honest about your skills. Communication beats technical skills—explaining what you build gets you promoted. Crunching gets you noticed, but use it like a turbo button—only when you really need it.
Now
I’m still figuring it out. The team processes millions of records daily for clients across LATAM. Sometimes we deal with massive historic loads that take forever to run. I still do BI work for some clients; can’t shake the habit that got me here in the first place.
TL;DR
Broke music student with zero job prospects helps girlfriend with Stata homework, accidentally becomes the class unofficial tutor, applies to random data company with music degree, flops the interview but gets hired anyway, and somehow ends up leading a data engineering team a year later. Still doing homework, just with a fancier title.