It was four months ago when I had no idea what was the difference between SQL and Python. Data analyst to me implied a fancy job description of someone who knew how to format excel sheets. I had no tech knowledge, I did not have a degree in math, no coding experience. What I did possess was an ever increasing restless feeling about my own content-writing career and a simmering desperation of doing something that would be more meaningful.
That desperation put me in a rabbit hole of career-switching possibilities, with data analytics repeatedly making appearances as “the new hot thing.” After one internet search I was up to my knees in articles, videos, and influencer posts discussing the need and demand of analytics positions and salaries and the infinity of online certification possible. That was when I realized how daunting and especially, how overwhelming it would be in terms of the data analyst course duration and fees, which could range anywhere between a few thousand rupees as per a weekend crash course to lakhs in case of a one year diploma. Anyway, they all insisted on coursework that would result in you being in a position to get a job.
I did not need additional marketing claptrap. I needed a little light.
Speed or Substance?
Having talked to some individuals who have already been working in the field of analytics, I started to understand that the quickest path is not necessarily the wisest one. One friend said that he passed through a six-week bootcamp only to take another three months to seal the cracks in his knowledge. One of them described how they selected a somewhat more lengthy program with practice tasks in the real environment, and as a result found employment since they could demonstrate what they had studied.
Then it occurred to me in a flash. I had to seek organization, substance, and time to train--rather than pursue the shortest route or the lowest fee. I later arrived at a middle sized course and it focused on real skills, not certifications. The data analyst course duration and fees was viable to me, however; what really meant a lot is that the period enables errors, suggestions, and vivacious practice.
Month one: We crash, we learn
It would be nice to say I got a handle on it fast. I didn’t though.
I was humbled in my first few weeks. Python was a foreign language — because it was one. Simple syntax escaped my understanding and error messages drove me crazy to quit. The only thing that kept me going was that most of the learners had said the same at the onset. I recall sitting in front of the computer for five hours so as to clean a dataset that had missing values, then, to find that I had missed a comma.
But in week four something happened. I started to realise patterns. SQL finally made sense. I designed a dashboard with synthetic e-commerce data, and, it was the first moment I felt that I was working with something real. It wasn not perfect, but it was mine and it worked.
The Shift: Theory VS Reality
In the second and third month, I switched the strategy of learning the tools to solving problem. I performed mini-projects in sales trend analysis, customer segmentation analysis and retention analysis. Every task was pushing me to re-learn something I learned previously, and the repetition like that was what made everything stick.
What I have learned is time is more than people believe. It is not about the rapidity with which you can overcome a course but how long you have to correct errors, revise them and internalise ideas. Otherwise, it can happen that just concentrating on data analyst course duration and fees can lead to choosing the course that will take you a short period of time but will fail to equip you with skills that will help you in real life working environments.
It was at this time that I started my portfolio. I also put my projects on GitHub and created visual dashboards as well as started writing notes on my thinking process. It assisted with being able to explain my choices in my interviews and demonstrate my work more than simply telling them I took a course.
Making it all to the Final: Interviews, Rejections and Breakthroughs
By day 120, I was not only completing assignments, I was job interview ready. I didn’t get success overnight. There were two of my initial interviews which ended up in awkward silences as I was floundering with the questions. However every experience made me be better prepared towards the next.
One day I was talking with one of the hiring managers, who said something I will never forget, he said, “You do not really have a conventional background in tech, but your work indicates that you know how to think in data.” That was the recognition that I did not realize I needed.
Looking Back
I would say to the past version of myself that was afflicted by the swirls of mixed opinions: you shouldn’t go chasing after glitzy promises. It is not about time or expenditure in job-readiness. It is all about honing talent, drilling and drilling and drilling and it takes time to get things to click.
Of course, compare courses on data analysis in length and cost. But that is not all. Look deeper. Find out what you will construct, who will teach you, and how much help they will give when you are stuck. The fact is that when you go out to the job market, nobody cares what course you did. They’re asking what can you do.
Sign in to leave a comment.