Beyond the Linear Path: Sandeep Bansal’s Evolution from EMT to Senior Data Analyst

Sandeep Bansal’s journey to an insights profession didn’t follow a straight line—it unfolded through uncertainty, quiet resilience, and a persistence that refused to let circumstances define the outcome.

He graduated from the University of Maryland, Baltimore County with a degree in Biology, carrying with him a clear intention: to build a healthcare career. Like many who choose that path, he believed in service, in impact, and in the idea that his work could directly improve lives. He spent the next 4–5 years working across healthcare roles, as a medical assistant, a pharmacy technician, and later as an EMT. Each role came with long hours, emotional weight, and moments that tested both stamina and empathy.

In the clinic, he learned how to stay composed when patients were anxious. In the pharmacy, he saw the importance of precision and trust. As an EMT, he experienced urgency in its rawest form, decisions made in seconds, where clarity and calm could make all the difference. These weren’t just jobs; they were proving grounds. They shaped how he approached problems, how he handled pressure, and how deeply he understood responsibility.

But somewhere along the way, Sandeep began to feel a quiet shift. He still valued healthcare, but he started to question where he could create the most impact. The work was meaningful, but the path ahead felt rigid, and he found himself searching for a different kind of challenge, one that allowed for creativity, problem-solving, and continuous learning.

Then came COVID.

For many, it was a time of pause. For Sandeep, it became a turning point.

As the market began to shift and the demand for data professionals accelerated, he made a decision that would change everything: he would teach himself an entirely new field—technology. There was no structured program, no roadmap, and no guarantee of success. Just a belief that he could figure it out.

He started with Python.

At first, it was overwhelming. Lines of code that didn’t make sense. Errors that felt endless. Concepts that seemed abstract and distant. But he stayed with it. Late nights turned into early mornings. He built a makeshift workspace, sometimes a literal whiteboard in his parents’ basement, breaking down problems piece by piece. He wasn’t just memorizing syntax; he was learning how to think differently.

Then came SQL.

He learned how data lived in tables, how relationships formed, and how insights could be extracted with the right questions. It wasn’t easy. Queries failed. Joins didn’t work. But each mistake became a lesson, and each lesson-built momentum.

Then visualization tools - Power BI and Tableau.

Here, things started to connect. Data wasn’t just numbers anymore; it became stories. Patterns emerged. Trends made sense. He could see how businesses made decisions, how performance was measured, and how insights could influence outcomes. What once felt foreign began to feel intuitive.

But the most defining part of this journey wasn’t the technical skills, it was the discipline. There were no deadlines forcing him forward, no professors grading his work. It was entirely self-driven. And there were moments, many of them, where quitting would have been easier.

Applications went unanswered. Interviews didn’t convert. Doubt crept in.

Still, he kept going.

He built projects. He refined his resume. He reached out to recruiters. He recorded videos explaining his work, not because anyone asked him to, but because he believed someone eventually would. Every step forward required effort without immediate reward. That’s where perseverance stopped being an idea and became a habit.

Eventually, that persistence paid off.

His first break came with Citizens Bank as an Application Support Engineer. It wasn’t just a job, it was validation. Proof that the countless hours of self-teaching meant something. In that role, he gained exposure to systems, data flows, and the operational backbone of technology, learning how data moved, how systems interacted, and how reliability mattered just as much as innovation.

From there, he stepped into Capital One as a Data Engineer, where his foundation deepened. Here, he wasn’t just supporting systems, he was building them. He worked on scalable data pipelines, optimized infrastructure, and contributed to decisions that impacted millions of customers.

Then came CNN.

At CNN News, Sandeep took on the role of Data Scientist, stepping into a space where data met storytelling at scale. He analyzed audience behavior, engagement patterns, and digital performance. The same curiosity that once drove him to learn Python now helped him uncover insights that shaped how content reached people across the world.

His journey continued at The Walt Disney Company as an Analytics Engineer, where he bridged data engineering and analytics. He built data models, enabled reporting, and translated complex datasets into insights that business teams could act on.

He later joined Nike, first as a part-time associate, an experience that grounded him in the customer and retail environment at a personal level. During this time, he also worked part-time as an Uber rideshare driver, balancing multiple responsibilities while continuing to grow professionally. These roles strengthened his communication skills, adaptability, and ability to connect with people from diverse backgrounds.

That perspective came full circle when he returned to Nike as an Insights Consultant. In that role, he partnered cross-functionally, using data to optimize retail performance, improve customer experience, and influence strategic decisions.

Today, Sandeep is a Senior Data Analyst at Comcast NBC, continuing to build on that momentum. He works at the intersection of data, business, and strategy, translating complex information into insights that drive decisions at scale.

Each role built on the last, but none of them erased the journey it took to get there. If anything, they highlighted it. Because behind every dashboard, every model, and every insight was the same person who once sat in a basement trying to understand his first line of code.

What makes Sandeep’s story compelling isn’t just the transition from healthcare to tech. It’s the way he approached it. He didn’t wait for the perfect moment or the perfect opportunity, he created one through consistency.

There’s a certain kind of perseverance that doesn’t announce itself loudly. It shows up quietly, day after day, in the decision to keep going when progress feels slow, when results aren’t immediate, and when the outcome is uncertain.

His path wasn’t linear. It didn’t come with guarantees. But it came with something stronger: the willingness to start over, to struggle through the unknown, and to keep moving forward anyway.

And in the end, that made all the difference.