DSA or Not DSA

Software Engineers tend to split into two groups when it comes to Data Structures and Algorithms (DSA): those who practice them regularly to stay sharp for interviews, and those who don’t bother. For the longest time, I’ve been in the second camp.

I used to think being a great engineer was about way more than knowing how to reverse a linked list or balance a binary tree. Building solid systems, solving real-world problems, and working well with a team felt way more relevant to the job than solving abstract puzzles under pressure.

But, to be honest, my mindset is starting to shift.

Why DSA Isn’t All Bad

At first, DSA-heavy interviews feel disconnected from reality. It’s easy to think, “How does finding the nth Fibonacci number help me build scalable APIs or manage app state?” And honestly, that criticism is fair. But if the alternative is asking candidates to build random features, design auth systems, or solve a problem the company itself hasn’t figured out yet, I’m not sure that’s any better.

DSA questions, for all their flaws, are at least standardized. Everyone gets the same starting line. They test your problem-solving approach, logical thinking, and ability to write clean, efficient code when the stakes are high. Sure, it’s stressful, but it’s also more predictable than being handed a “build this feature for us” task that may or may not reflect the job you're applying for.

A Personal Take

Over the years, I’ve seen every kind of interview out there, and I’m starting to feel like DSA isn’t as bad as I used to think. It’s not perfect, but it does test a foundational skill set. And honestly, it’s how I got my first job.

I still remember sitting down during an interview and sketching out sorting algorithms on paper. At the time, I thought, “This is ridiculous.” But looking back, it was a fair way to see how I approached problems and how much I actually understood. That simple exercise got me in the door — and launched my career.

So, Where Do I Land?

I’m not saying DSA should dominate interviews. In fact, a good process will combine DSA with more practical challenges that reflect the actual role. But dismissing DSA outright feels shortsighted. It’s a shared framework, and when used well, it can make the hiring process a little less random and a little more fair.

So, maybe it’s not about DSA or not DSA. Maybe it’s about DSA and everything else that makes someone a great engineer.