A while back, a client called me in to look at a system whose author has left years ago. It was a mess. And for no good reason, it used Docker extensively, and would only work with a specific pre-release version. I searched and discovered that the guy had stayed just long enough to do a talk on this then-hot new technology before getting a better job elsewhere.
It was the clearest example of Resume Driven Development I'd ever seen, but no means the only one.
I worked at a startup that locked all the architects cronies in a room for a number of months to build every white paper he was interested in. Told rest of company to adopt this new world order… within a year of the rewrite they laid off 2/3 of engineering and sold the company off shortly thereafter. Architect accepted a role at FAANG for experience gathered. I remember a lunch with him where he joked “I usually leave companies worse off than when they started.” Self-indulgent psychopath.
The things the original commenter wants to know are exactly the things that will count in an interview. The reasons behind the decisions. Not the actual implementation.
Implementing anything, even something of significant complexity is trivial with frontier agents now. So build your experience / knowledge in a technology-agnostic way. The language/app/stack is superficial.
Edit: Speaking anecdotally; it’s what I’d look for in a candidate if I was hiring today
They got to put ClickHouse, DuckDB and Trino on their resume & LinkedIn. Problem solved!