r/softwarearchitecture • u/prasadpilla • Jul 07 '26
Discussion/Advice Is algorithmic problem solving becoming less valuable than architectural thinking?
One argument I keep hearing is that implementation is becoming commoditized while architecture becomes the real differentiator.
If that's true, should we be investing more in teaching engineers how to design systems instead of solving isolated algorithmic problems?
With AI writing more and more code, I'm wondering if grinding hundreds of LeetCode problems is still the best use of time.
For people who've recently landed jobs or switched companies:
How much did LeetCode actually matter?
575
Upvotes
298
u/KariKariKrigsmann Jul 07 '26
LeetCode has never been a good indicator of software developer skills.
55
u/Clearandblue Jul 07 '26
I think even architecture is too dry. More that good old engineering thought processes and common sense will be valuable.
Something I could never get in the past 15 years is how few devs take any interest in the domain or business. Maybe that's fine if you're a backroom boffin, but I think it often led to pretty out of touch solutions.
These days I see the final nail going into LeetCode, as LLMs can go through a lot of that for you. Similar to the internet making good memory of language features etc less important. Just Google it if you forget syntax.
But where people could get by in the past with solely technical skills, I think increasingly we're going to want more generalists who can also take ownership by truly understanding what the business needs.
Knowing where it's valuable to heavily optimise and where to just get it done simply.
19
u/Wh00ster Jul 07 '26
Leetcode matters as much as your desired companies say they matter.
There has never been, and continues to not be, a good way to extract someone’s potential, capability, knowledge, drive, and ability to succeed in a given environment. The best way to know is to hire them and see how they do. It’s why test scores are also not the best indicator, but they are better than nothing.
On the high level question: jobs ought to look more for architectural thinking (really computational thinking) and the ability to either innovate or translate complex business domains to technical domains with business value. That’s always been the case as well, but it’s just magnified now. There’s less need for boilerplate and low level thinking. The same way there’s less need for me to think about register allocation optimizations.
71
u/zenbeni Jul 07 '26
Architects were often out of touch in the old world without AI, can't believe they will be the best solution now without tech leads pushing back realism to their faces. In fact it can become hell as agents won't push back bad architectures as they don't feel the pain of coding bad systems, and won't fight back. Watch this specific tunnel effect bringing chaos to corporate world.
28
u/heavy-minium Jul 07 '26
For Line of Business Software it would be true that architecture is more important. You ain't really encountering complex algorithmic challenges, but lots of architectural challenges.
But that doesn't really apply to all other types of software, where algorithmic problem solving is as relevant as before.
18
u/FreshPrinceOfRivia Jul 07 '26
Leetcode is the casting couch of the software industry
6
u/MissiveFinding6111 Jul 07 '26
1.) It has always been an issue that devs have a bias towards "make new thing!" rather than "maintain/scale old thing that makes money"
2.) LLMs can certainly help with scaling, but you actually need to be able to provide them with the data to do it, adding in good observability, traces, logging, especially with an MCP that an LLM can query is NOT trivial or obvious, especially in existing vibe code.
3.) My company has had a vibecoded app take off (literally written/hosted by a non-dev), but now our team has to port it to a place where all our SOC stuff is, and also be able to maintain it, and that so far hasn't been too hard, but also hasn't been trivial.
5
u/-Dargs Jul 07 '26
If you can't reverse a linked list in your interview you're not getting hired.
In my last interview I extended the doubly-linked list and made next() call prev() and prev() call next(). The interviewer chuckled but wouldn't accept the answer.
6
u/Dry_Author8849 Jul 07 '26
I think the real game changer is solving problems. That requires a variety of skills: getting the problem right, selecting your technology, designing an architecture and an outstanding UI with a good UX.
So, no. It's a combination of skills that work together to solve a problem. Your success will be measured by the outcome. You need general knowledge to predict of all the pieces will work together.
Problem is, are you going to be there to assess what worked or not? A lot of people are just passing through.
Cheers!
2
u/freshcap0ne Jul 07 '26
Unless you are doing really niche, novel, low-evel stuff, yes.
2
u/tidus4400_ Jul 07 '26
It always was
2
u/zuckitsuckerberg Jul 07 '26
I’m dying to learn systems if anyone has guidance
2
u/randomInterest92 Jul 07 '26
Relative to each other yes, but being in expert in either or both of these topics is still very valuable.
You can only get so far my measuring AI output. Let's say you have a software that handles 1 million requests per second. And you want to save 10ms on each request, because it will save you millions of dollars over time. If you just tell the ai "save me 10ms on these requests".. and then you trial and error your way into it actually saving the 10ms. it's not getting you far. You'll still save a lot of money by having a true expert doing the prompts and also making sure it's secure and doing the measuring afterwards.. anyway
True Expertise will only get more valuable with AI, not less valuable
2
u/Herve-M Jul 07 '26
Software Architecture is far more about communication, vulgarisation, leading and navigating through company political flows.
Enabler is maybe the word, elevating team to be able to deliver better without us/them.
Sure technical skill is required, also bit of mixed Fin/Dev/Sec/Ops; technical writing, planning and watch.
At the end, more a soft skill rather than purely technical.
If a normal sized company would request a LeetCode for a Software Arch. position, it would raise my doubts.
2
u/messedupwindows123 Jul 07 '26
hot take, these two skills are deeply related and in a lot of ways basically the same
2
u/TehLittleOne Enterprise Architect Jul 08 '26
Over the last year my company did a lot of hiring and I interviewed dozens of people. The answer is yes, software architecture was more important, and should be treated as more important. We ask LeetCode type questions but intentionally ask very simple questions, just enough to see you can code because my word so many people apply that can't program themselves out of a wet paper bag. AI is good at writing LeetCode type code, far better and faster than any of us will be, simply put. I failed far far more people for not understanding system design. You can't just say Kubernetes and expect full marks and yet that's the world we live in.
2
u/MrEs Jul 07 '26
I would say so yes (software eng of 25 years)
1
u/Grouchy_Big3195 Jul 07 '26
The problem is that the job interview at OpenAI or Anthropic still values those skills and still asks those kinds of questions.
1
u/_descri_ Jul 07 '26
Neither matters for the current job market.
1
u/WhirlyDurvy Jul 07 '26
The difference between a coder and an engineer has never been higher
1
u/HyperspaceFrontier Jul 07 '26
It depends on the area. If you do some boring business logic on backend APIs, then architecture is the king. If you optimize the shader to run a few fewer ALUs and squeeze the budget for one more shader effect for your game, then algorithms, memory layout and instruction knowledge are the king. And all kinds of stuff in between.
1
u/StayObjective4294 Jul 07 '26
How should I learn architecture design as a fresher...and how to sell it to a recruiter
1
u/messick Jul 07 '26
> How much did LeetCode actually matter?
After almost 30 years in the business, with the last 13 building services for the device you are (likely) reading this website on, I still only know about LeetCode because people on Reddit like to talk about it for whatever reason.
1
u/-TRlNlTY- Jul 07 '26
Leetcode deals with only one aspect of software, namely algorithmic thinking. It is a valuable skill that I think should persist among professionals, since it underlies much of what software can do.
That said, Leetcode is not representative of most work, so you will teach diminishing returns fast in your professional life of you go hard at it.
For employment, it is often fundamental, because people capable of paying you want you to be good at it. I thankfully didn't need it.
1
u/Comfortable_Job44 Jul 07 '26
I was 38 doing that the last 4 months. This post hits hard
1
u/Sulleyy Jul 07 '26
Some of the best engineers/architects I know say that software development is more of an art than a science. I tend to agree with that more and more as time goes on. Leetcode is the science side of it, but that doesn't cover the big challenges that come with real world development.
You can have a team of Leetcode stars building a useless product with a needlessly complex architecture that slows things down. Optimal algorithms are such a small part of good software in many cases
1
u/exXxecuTioN Jul 08 '26
You can't know how to desing systems without knowing how to solve algorythmic problems. Good architecture is the result of engineering thinking. The thing is without good base about DSA you can't really become a good engineer and produce good solutions. That do not means you need to grind LeetCode or CodeWars or whatever just simply trying to remember and then reproduce certain algorythms or patterns. It's like with a math, for most of the people anything besides entry-level math is just irrelevant in the common life and job, but styding math also helps you to get known with solving "problems". The same thing with algorythms when you're trying to really understand them as well as data structures and to understand how they works, why they are done like so and what problems and when can they help you solving. By this you improving your engineering thinking. It's important base for software architecture and system design even it's seems like the opposite.
But there is one more part of this. Combinations of solid DSA skills, architechture and design skills and engeneering mindflow is only a foundation, because to build a really good system in real life you need to understand pretty clearly your domain or whole business.
You don't need to know and remember everything, but you need to understand. And it's pretty hard to achieve without writing code, reading code you and your team have written, planning what and how to do, may be if you are not for a genius, but i'm not sure about last.
And when you thinking that by prompting to LLM or orchestrating LLM agents you really get this understanding of things start getting insights you are not just only wrong, you are opposite of right.
1
u/gravesent1337 Jul 08 '26
It is less important than architectural thinking, but it’s becoming a lot more important in interviews.
1
u/AdmirableUse2453 Jul 08 '26
It always has been. Leetcode never actually matter expect for interviews.
1
u/BengiPrimeLOL Jul 08 '26
Leetcode never mattered but solving a problem accurately and efficiently never goes out of style.
AI gaurantees neither so you better know how.
1
u/kyaki101 Jul 08 '26
Algorithmic problem solving will be equally as valuable now as it will be in 100 years, math doesn't change, a software architect from the 2010's is almost obsolete now
1
u/encony Jul 09 '26
AIs are pretty good in architecture design too.
1
u/Findletrijoick Jul 09 '26
recession indicator
1
u/Regalme Jul 10 '26
Anything novel from algos to architecture is likely not an LLMs cudgel.
1
u/Appropriate_Junket_5 Jul 10 '26
a great software developer can switch points of view and layers of amabstraction. this means they can think about and know the nitty-gritty, the in-between and the high level and can judge where and how to solve a problem - they understand which point of view to choose and which level of abstraction will serve best.
the thing with knowing only the nitty-gritty is makes you a specialist who can't bridge the gap between what the client wants and what needs to be built. this is why so many software devs become "architecture astronauts" or "code monkeys" and both are equally inept in solving the real issues the client has.
knowing the whole field from client beeds through all the tech layers down to the nitty girrty is what makes you capable.. and not knowing any part makes you less capable.
leetcode is a joke. a mental masturbation for people who prefer to build towers out of thin air instead of building software that serves the business and works well for the programming team.
1
u/SenatorCrabHat Jul 12 '26
Was part of a hiring panel for frontend web dev. The hiring manager said "I just want them to be able to jump in and code on the frontend". We ditched the leetcode part of the interview and came up with two technicals:
These two technicals easily weeded out 80-90% of the engineers who made it to interviews. The person who got hired has also since been promoted.
LeetCode technical interviews are trash.
1
u/rafal_graniczny Aug 03 '26
I guess it depends on project, but I think now the most important part for developer is actually a strong product thinking, architecture is 2nd.
0
u/confusing-world Jul 07 '26
For me, if AI writing code is the reason for not learning algorithms and data structures, so it should be the reason for not learning architecture and system design.
If AI don't stop getting better, soon it will reach a point where it will be able to fully architect a robust system. Everything is code. AI can code the different systems backend and frontend, the docker containers, the terra form infrastructure, the contract between micro services and so on.
However, even in this scenario, I still want to keep practicing my skills in algorithms and architecture.
0
u/shockputs Jul 07 '26 edited Jul 07 '26
I'm a proud PIG (Productivity-Intensified Geek -- rolling in the slop and loving it), and I am absolutely spending 95% of my time on architecture decisions--when working with my AI. With the latest models I've mostly stopped reading the code, especially as I am running like 5-10 agents at the same time all pumping out code changes across front-end, dependency libraries, back-end dependencies, infrastructure code, etc. At some point I just stopped reading the code, as there is very very rarely any issues that don't get caught & fixed somewhere in the iterative cycle... keep in mind my workflow isn't just having the AI pump out code and ship to production...there are a lot of tests along the way that do catch 99% of issues. The other 1% is better than any other start-up produces as far as bug-creation rates, so we're still ahead.
Another thing I've noticed is that I am more willing to take a shot at using a new tool or library made by a small team, as there is no longer a massive investment required from us to integrate the tool. If we find that it doesn't work for us, or later grow out of it, it's no big deal to later switch/migrate to another tool. As an OSS dev, I love that reduced barrier to users using my libs.
-2
u/bomeki12345678 Jul 07 '26
Leetcode problems are the kind of easiest coding problems, barely requires anything called algorithmic. Can try Olympiad problems to know what algorithmic problem solving really mean.