News for hackers. Stuff that matters.
Re:Nobody Gets Promoted for Simplicity by tyre on Wednesday March 04, 2026 @09:19AM (#47247677)
So my cofounder was talking to Stripe about an acquihire (this was after I’d left.) As part of it, he had to do a systems design interview.

He got the prompt, asked questions about throughput requirements (etc.), and said, “okay, I’d put it all in Postgres.” He was correct! Postgres could more than handle the load.

He gets a call from Patrick Collison saying that he failed the interview and asking what happened. He explained himself, to which Patrick said, okay, well yes you might be right but you also understand what the point of the interview is.

They made him do it again and he passed.

Re:Nobody Gets Promoted for Simplicity by wongarsu on Wednesday March 04, 2026 @09:45AM (#47248169)
If the point of the interview was to test if the candidate can design something that can handle google-scale problems then maybe the interviewer shouldn't state throughput and availability requirements that can be satisfied by postgres
Re:Nobody Gets Promoted for Simplicity by jghn on Wednesday March 04, 2026 @10:55AM (#47249352)
It's both.

As a hiring manager I've had situations like this arise because there was a gap in my plan and I didn't realize it. When those come up, we thank them for their cleverness, apologize to the candidate, reframe the situation, and give them another shot.

But also sometimes I leave intentional ambiguity in the plan. Part of the goal is to see if they have a degree of common sense commensurate to their level. If they're interviewing for a high level position, I'd expect them to be able to spot silly flaws and push back that perhaps the whole problem needs rethinking. And of course, I also expect them to know the brute force solution as well. Do they only know one? Both? Let's fine out.

Re:Nobody Gets Promoted for Simplicity by sampo on Wednesday March 04, 2026 @12:27PM (#47250813)
> and give them another shot

Isn't this rather giving yourself another shot.

Re:Nobody Gets Promoted for Simplicity by jghn on Wednesday March 04, 2026 @12:36PM (#47250975)
Of course, but the point is you don't fail a candidate for this. Some people do, including some of the examples to which I was replying
Re:Nobody Gets Promoted for Simplicity by Aurornis on Wednesday March 04, 2026 @10:12AM (#47248654)
Postgres might have been a perfect answer, but the candidate needs to explain why and how.

The purpose of the interview is for the candidate to demonstrate their thought process and ability to communicate it. “Just use Postgres” doesn’t do that.

This would be more obvious if it was a LeetCode problem and the candidate just regurgitated an algorithm from memory without explaining anything about it. Yeah it’s technically the right answer but the interviewer can’t tell if you actually understand what you’re talking about or if you just happened to memorize and answer that works.

Interviews are about communication and demonstrating thought process.

Re:Nobody Gets Promoted for Simplicity by wadadadad on Wednesday March 04, 2026 @10:23AM (#47248837)
100% interviews are about communication and demonstrating thought process; after going through some rounds of interviewing candidates myself, any candidate who can adequately explain what they're thinking and how they arrive at their conclusions will be able to demonstrate their skills much more thoroughly than 'just use Postgres'.

That being said, it's also on the ones giving the interviews to push the candidates and ensure that they really are receiving the applicants best. The interviewers don't want to miss potentially great candidates (interviews are hard and nerve-wracking, and engineers aren't known for their social performance), and thus sometimes need to help nudge the candidates in the right direction.

Re:Nobody Gets Promoted for Simplicity by Aurornis on Wednesday March 04, 2026 @11:33AM (#47249970)
Fully agreed on the point that interviewers should prompt and push candidates in the right direction.

The best thing someone can do to learn how to perform well in interviews is to sit on the other side where you’re interviewing candidates. Some candidates will get stuck on arguing some irrelevant point or trying to fight against the interview question for too long in an interview. Once you see how much it hurts the interview process you learn to never do it yourself.

Re:Nobody Gets Promoted for Simplicity by jimmydddd on Wednesday March 04, 2026 @10:45AM (#47249189)
I went to law school and a few of us students were engineers. For our first set of essay exams, the professors all instructed us to "just answer the legal question" and not include extra analysis. After the exam, many of the engineers didn't do well because the professors *actually* wanted you to weave the whole sylabus into your answer (i.e., discuss hypotheticals that were not actually part of the question asked), not just answer the question. After that, we were fine.
Re:Nobody Gets Promoted for Simplicity by rawgabbit on Wednesday March 04, 2026 @10:58AM (#47249399)
This is also what I learned the hard way. In many situations the customer doesn’t say what they really want. There are a lot of reasons why. I usually have to write down a lot of hypotheticals. If X is the primary concern, we should do Y. If U is the issue, we should do V.
Re:Nobody Gets Promoted for Simplicity by laserlight on Wednesday March 04, 2026 @01:07PM (#47251414)
I wouldn't expect customers to say what they really want. They are looking for faster horses after all. But law professors? Among all professors, law professors should be the ones saying what they really want.
Re:Nobody Gets Promoted for Simplicity by zelphirkalt on Thursday March 05, 2026 @05:47AM (#47260111)
Sadly, many interviewers will be fine with someone who simply memorized without actually understanding much, and not fine with someone needing to think and slowly coming to a solution, being able to explain it, because oh that did take more time than the interviewer had allotted for the task. Sadly, many interviewers and the adjacent HR departments are utterly failing in the communications part too.
Re:Nobody Gets Promoted for Simplicity by wiseowise on Wednesday March 04, 2026 @11:52AM (#47250291)
The point is that you’re supposed to kiss clown’s ring and do the dance.
Re:Nobody Gets Promoted for Simplicity by inerte on Wednesday March 04, 2026 @01:26PM (#47251690)
Maybe 10 years ago I interviewed both for Netflix and Facebook.

At Netflix, I used a state machine library to handle the project they gave me. Got rejected because I didn't show I knew raw JavaScript enough.

At Facebook, I wrote a calendar dropdown from scratch. Got rejected because I should have used a library.

Interviews sometimes is just a lottery...

Yes I know both companies should have set the expectation, but you can set the expectation for EVERYTHING, otherwise you give candidates all the answers you're expecting. There's always going to be some chaos due to the huge number of variables.

Re:Nobody Gets Promoted for Simplicity by Folcon on Wednesday March 04, 2026 @09:21AM (#47247719)
I feel like if that's the thought process, that should be stated up front

There's a ton of incredibly talented neurodivergent people in our ecosystem who would trip up on that question just because of how it's framed

Because how is the interviewee to know if you're testing for the technically sophisticated answer no one in their right mind would ever write or the pragmatic one?

Re:Nobody Gets Promoted for Simplicity by wreath on Wednesday March 04, 2026 @09:41AM (#47248085)
I dont even think you need to be neurodivergent or anything to answer this question like the parent’s cofounder did.

From one side, we call ourselves problem solvers, on the other hand we are not satisfied with simple solutions to these problems. If im interviewing for a job, i should be expected to behave and solve hypothetical problems the way id do it on the job. If that screws up your script, you probably suck at hiring and communicating your expectations.

Re:Nobody Gets Promoted for Simplicity by johnnyanmac on Thursday March 05, 2026 @04:19AM (#47259478)
We also aren't mind readers and interviews are a crapshoot. Some companies do in fact want you leveraging tools and API's in your solutions. Some want to probe your foundational technical knowledge. Ideally they will poke you towards the answer they want, but not always. But few will let you know ahead of time for some reason.
Re:Nobody Gets Promoted for Simplicity by wongarsu on Wednesday March 04, 2026 @09:46AM (#47248192)
Or just add a couple zeros to all the requirements until postgres is a worse solution than whatever the interviewer envisions. Isn't that the point of stating throughput requirements?
Re:Nobody Gets Promoted for Simplicity by wpietri on Wednesday March 04, 2026 @04:27PM (#47254135)
Right? I'll often structure interview questions like this. I give a basic problem, hoping for a basic answer. Then I add complexity, seeing how they respond.

In my experience, it's much easier to train somebody on how to scale a basic system up in response to need than it is to get somebody who favors complexity to cut it back.

Re:Nobody Gets Promoted for Simplicity by mrweasel on Wednesday March 04, 2026 @10:31AM (#47248972)
It's probably more about your mindset, than about being neurodivergent vs. neurotypical. If you care more about maintainability and operations, there's a whole host of solutions you'd never built.
Re:Nobody Gets Promoted for Simplicity by anthonypasq on Wednesday March 04, 2026 @11:11AM (#47249609)
if your brain short-circuits at ambiguity, or you're completely incapable of understanding intent and you take everything literally, that is a negative hiring signal.
Re:Nobody Gets Promoted for Simplicity by giveaccountpls on Wednesday March 04, 2026 @01:12PM (#47251482)
> neurodivergent people in our ecosystem who would trip up on that question just because of how it's framed

If anything, it's neurodivergent interviewers. If I insisted on a different design I'd either ask a question that's not solved by "just use postgres" or follow up with "ok, that would work, but what if <something that would prevent postgres from working>". Just failing a candidate for a correct answer is a prime example of why interviewing is so bad.

Re:Nobody Gets Promoted for Simplicity by twodave on Wednesday March 04, 2026 @11:20AM (#47249739)
This is just an indication that it's a poor interviewing technique. If you ask a question expecting the answer to be predictable then you had better cover all possible ambiguity in leading the candidate to the answer you want to hear. But then you're no longer asking the candidate to be creative, are you? As an interviewer I might be more inclined to allow such an answer and then follow up with questions of my own to test the limits of the candidate's knowledge of and confidence in Postgres as a technical choice for serving all the different constraints of the problem space. This way either I discover how well-reasoned the answer is or else (for a good candidate) it prompts them to adjust the design to better fit the problem. In no case would I expect they need to fit their answer into some key and then scold them for not playing along with my imaginary game.
Re:Nobody Gets Promoted for Simplicity by fatnoah on Wednesday March 04, 2026 @09:56AM (#47248384)
> He got the prompt, asked questions about throughput requirements (etc.), and said, “okay, I’d put it all in Postgres.” He was correct! Postgres could more than handle the load.

I had this happen in a Google interview. I did back of the envelope math on data size and request volume and everything (4 million daily events, spread across a similar number of buckets) and very little was required beyond that to meet performance, reliability, and time/space complexity requirements. Most of the interview was the interviewer asking "what about" questions, me explaining how the simple design handled that, and the interviewer agreeing. I passed, but with "leans" vs. "strong" feedback.

Re:Nobody Gets Promoted for Simplicity by btilly on Wednesday March 04, 2026 @12:34PM (#47250928)
To be fair, the simple answer is not so simple within Google.

The issue is that Google achieves reliability by insisting on n+2/n+1. Globally your service is in at least 2 more data centers than is required for full load. In each region in at least 1 more data center than is required for full load.

If you're using the Google toolchain, all of the scalability and fallover problems are automatically handled by the layers that you're relying on. Which everyone expects you to use, because they are already integrated into the environment.

But if you go to use Postgres as a data storage layer, then you also need to take care of replication, failover, backup, and make sure that this is integrated with the automated systems that Google already has to detect when this is needed. Even after you've done that, people from outside of your team will need to be convinced that you've done that. Simply because you're doing things differently, you'll get extra scrutiny.

As a result, even if Postgres would have worked perfectly well, it is usually not the optimal answer for someone who is working within Google's environment. Don't think of it in terms of, "Does this do the job?" Think about it in terms of, "Can those in the broader organization easily certify that this does the job?" That certification is easier when you use standardized parts that are themselves already certified within the organization.

My guess is that your interviewer was aware of this. And was left with, "What about that question that I didn't think to ask you about?"

Re:Nobody Gets Promoted for Simplicity by dmurray on Wednesday March 04, 2026 @02:31PM (#47252609)
If you're interviewing at Google, the expected answer to the interview question can't be to use Google's internal tools. "Use Postgres" is the standardized, understandable answer for anyone outside Google who needs to solve Postgres-shaped and Postgres-sized problems.
Re:Nobody Gets Promoted for Simplicity by fatnoah on Wednesday March 04, 2026 @02:38PM (#47252706)
FWIW, that was the second time I interviewed at Google. The first time, which resulted in strong yes across the board at L7, the first system design was to design Youtube Video Upload. The second was a more practical problem about replacing a high-volume logging component where correctness was critical but environment was space-constrained (i.e. no ability to run old + new in parallel).

Those were my favorite system design rounds ever, thanks to the problems being interesting and the interviewers also being very dynamic. It was also pre-Covid, so it was just awesome whiteboard design sessions.

sigh I miss in-person interviews.

Re:Nobody Gets Promoted for Simplicity by btilly on Thursday March 05, 2026 @10:31AM (#47262779)
No, that can't be the expected answer. And indeed, use Postgres was an accepted answer.

But when the interviewer keeps pushing back, that's an invitation for the candidate to ask why, and ask what about the environment might make that not a good fit within Google. Doing that gives a stronger hire signal.

Re:Nobody Gets Promoted for Simplicity by eptcyka on Wednesday March 04, 2026 @09:54AM (#47248360)
If they don’t want to hear the correct answer, let them modify the question to exclude postgres answers. Interviews are a 2 way street, you will miss out on great candidates by being this stupid.
Re:Nobody Gets Promoted for Simplicity by lo_zamoyski on Wednesday March 04, 2026 @11:12AM (#47249627)
On the one hand, interviewers can suck. They can be uninterested in understanding and embrace instead the role of a trigger-happy interrogator looking not for a good response - something that may very well require effort and considering new ideas on the part of the interviewer - but an excuse to cross you off the list. The interview begins to look like a game of "Guess what I'm thinking". Interviews should simulate a colleague asking you for help.

On the other hand, interviewees can give poor answers with no explanation. The interviewer should press for an explanation in those cases, of course, but perhaps some are trying to see if the interviewee instinctively provides at least some basic rationale behind the answer without having to be prodded each time, in which case it is a matter of communication habits and skills. Communication is essential, and it is under-emphasized and under-taught in so-called 'STEM' curricula.

Re:Nobody Gets Promoted for Simplicity by Gooblebrai on Wednesday March 04, 2026 @10:08AM (#47248615)
> They made him do it again and he passed

I'd assume that if he got a call from Patrick himself and a second opportunity to get interviewed, that's already a cue for interviewers to pass him regardless of what he says?

Re:Nobody Gets Promoted for Simplicity by coldtrait on Wednesday March 04, 2026 @11:05AM (#47249503)
That was what I felt too. Why even need an interview for an acquihire when you have a direct link with the founder/CEO?
Re:Nobody Gets Promoted for Simplicity by baobabKoodaa on Wednesday March 04, 2026 @04:41PM (#47254318)
To maintain the illusion of meritocracy
Re:Nobody Gets Promoted for Simplicity by smallnix on Wednesday March 04, 2026 @09:37AM (#47248019)
> you also understand what the point of the interview is

Exactly, it's also a test of ability to conform. Especially useful to weed out rogue behavior picked up in startups.

Re:Nobody Gets Promoted for Simplicity by jkubicek on Wednesday March 04, 2026 @09:44AM (#47248141)
No, the point was to demonstrate how you’d design a complex system.

If a valid answer was “just use Postgres” then it just wasn’t a very good interview question.

In real life, the answer almost certainly would be “just use Postgres” and everyone would be happy.

Re:Nobody Gets Promoted for Simplicity by chrisandchris on Wednesday March 04, 2026 @09:54AM (#47248357)
No, it was a perfectly fine question IMHO. it is a broken incentive - it is expected that you design complex systems regardless whether they are useful or not. Try to interview for the role you have to fill, nor for a role you a dreaming you would love to have whenever you're Google2.

If the interview wants you to think about stuff that never happens in your role, I think it is a sign that in your role, you're expected to solve the problems like in the interview.

Re:Nobody Gets Promoted for Simplicity by pjmlp on Wednesday March 04, 2026 @10:08AM (#47248618)
This is the part I would say thank you, and pass on the opportunity.

And yes, I have done this on a second Google interview about 15 years ago.

Re:Nobody Gets Promoted for Simplicity by badosu on Wednesday March 04, 2026 @09:44AM (#47248145)
Sorry, I didn't get it. What was the 'right' answer?
Re:Nobody Gets Promoted for Simplicity by munchbunny on Wednesday March 04, 2026 @11:36AM (#47250008)
It depends on the situation.

Sometimes you just have a bad interviewer who is looking for something specific from you but isn't telling you. If you're experienced in these interviews, you catch the signs and adapt by asking questions to suss out which direction the interviewer wants to take it.

Sometimes your answer is plausible but the interviewer wants to see you justify it. Sometimes your answer is wrong but the interviewer wants to see if you can reason your way through it, and maybe come up with an alternative.

If you're junior/inexperienced, it's often hard to tell and it'll feel arbitrary/unfair, and unfortunately that's just how it goes. As a more senior/experienced candidate, you can often figure out which situation you're in by asking questions to feel out the interviewer and then try to pivot during the interview, though it still takes valuable minutes out of the interview that you could have otherwise spent showing your competence.

Re:Nobody Gets Promoted for Simplicity by badosu on Saturday March 07, 2026 @08:37AM (#47287534)
Thank you!
Re:Nobody Gets Promoted for Simplicity by wccrawford on Wednesday March 04, 2026 @10:37AM (#47249053)
"Postgres, because..."

They want a conversation to see how you think, not an actual answer.

Which is stupid, because they asked a question that the person didn't need to think to answer. So they didn't get to see them think.

Re:Nobody Gets Promoted for Simplicity by koakuma-chan on Wednesday March 04, 2026 @09:50AM (#47248276)
distributed virtual abstract factory
Re:Nobody Gets Promoted for Simplicity by tracker1 on Wednesday March 04, 2026 @11:54AM (#47250315)
You need the StrategyFactory in case you need further variances to the Factories you're making.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Re:Nobody Gets Promoted for Simplicity by sejje on Wednesday March 04, 2026 @11:20AM (#47249737)
nosql on serverless
Re:Nobody Gets Promoted for Simplicity by alistairSH on Wednesday March 04, 2026 @12:53PM (#47251216)
Apparently some combo of kissing the arse and reading the mind of the interviewer...
Re:Nobody Gets Promoted for Simplicity by MrBuddyCasino on Wednesday March 04, 2026 @09:46AM (#47248190)
> They made him do it again and he passed.

I would hire the "just use postgres" dude in a heartbeat without re-testing, if the numbers made sense, and perhaps give a stern talking-to to the interviewers. But then again I'm not a unicorn founder, so what do I know.

Re:Nobody Gets Promoted for Simplicity by lucianbr on Wednesday March 04, 2026 @10:17AM (#47248735)
My read of the story is that the decision to hire was already made, the interviewer goofed but was then set on the right track by his boss.
Re:Nobody Gets Promoted for Simplicity by layer8 on Wednesday March 04, 2026 @11:45AM (#47250177)
The question was bad if using Postgres would really be a better solution than designing and implementing a bespoke system, under the stated constraints. Either they should provide a better problem statement, or at least immediately follow up with “okay, suppose you can’t make use of an existing system like Postgres for $reasons”.
Re:Nobody Gets Promoted for Simplicity by PKop on Wednesday March 04, 2026 @09:51AM (#47248300)
Eh, it's a good answer and shows good instincts, but they still want to know how he would design a system if one was necessary. There's no need to be ridiculous about any of this from either perspective, which is why it should never have been a "fail" without the original interviewer simply saying "That's a solid answer now tell me what you would do if you had to build something new". I mean look how much time he wasted for everyone including his own CEO by being stubborn about it.
Re:Nobody Gets Promoted for Simplicity by MrBuddyCasino on Wednesday March 04, 2026 @10:12AM (#47248662)
If the numbers can be satisfied by a Postgres then thats the correct answer. The interviewers fucked up, because they sized the problem wrongly.

This is the same issue that was prevalent when the industry switched from HDD to SSD: some system design questions suddenly became trivial, because the IOPS went up by magnitudes. This is not a failure of the interviewees, who correctly went with the times, but a failure of the interviewers.

Re:Nobody Gets Promoted for Simplicity by LPisGood on Wednesday March 04, 2026 @10:43AM (#47249155)
What kinds of system design questions got destroyed?
Re:Nobody Gets Promoted for Simplicity by danenania on Wednesday March 04, 2026 @10:59AM (#47249404)
The correct answer is “Postgres would handle it, but if it needed to scale even higher, I’d…”

The point of a system design interview is to have a discussion that examines possibilities and tradeoffs.

Re:Nobody Gets Promoted for Simplicity by darkwater on Wednesday March 04, 2026 @11:49AM (#47250243)
And people weeded out by this kind of questions are probably rightfully so. I for one could not ever work with someone that says "my answer is correct, period.". Part of the answer and the discussions made by mature individuals must ask for feedback, incorporate it in your design, be open to compromises sometimes but also to die on a hill when it makes sense. And in an interview context, you ought to show the hiring manager all these faces.

Then, there are hiring managers that suck and you might be discarded because you didn't follow the script. Sure, but that's a bullet you dodged.

Re:Nobody Gets Promoted for Simplicity by PKop on Wednesday March 04, 2026 @07:07PM (#47255779)
> then that's the correct answer.

Obviously. But they don't care about that answer, they care about the design of a new system so I'm saying the interviewer is dumb for not just asking directly for the solution he wants to see (while also giving credit for the original right answer).

The interviewee is dumb (if he wants the job) to not know this is what they want to hear, so he can just say "I really do think Postgres would satisfy the requirements here, but as an alternative a custom solution would look like.."

What is the point of not demonstrating your own well rounded knowledge when given the opportunity? Is it not obvious what they want to hear? Then why not tell them, again given that he did want the job

Re:Nobody Gets Promoted for Simplicity by marcosdumay on Wednesday March 04, 2026 @10:38AM (#47249070)
Well, yes, doing the interview again is the right choice.
Re:Nobody Gets Promoted for Simplicity by eunos on Wednesday March 04, 2026 @09:41AM (#47248094)
> okay, well yes you might be right but you also understand what the point of the interview is.

So the point is? I honestly dont understand.

Re:Nobody Gets Promoted for Simplicity by praptak on Wednesday March 04, 2026 @10:22AM (#47248805)
The point is the interviewers are sometimes obtuse.

Sometimes the point of the interview is to see if the candidate knows an existing solution and "just use postgres" is the good answer. Sometimes it's to test the technical chops and pretending postgres doesn't exist is the point.

The candidate shouldn't be expected to always guess right, unless the position says "a psychic". The interviewer should notice if the candidate is solving the wrong kind of problem and nudge them in the right direction instead of punishing the candidate for the wrong guess.

Re:Nobody Gets Promoted for Simplicity by LandR on Wednesday March 04, 2026 @09:57AM (#47248419)
The point isnt to give a simple answer, even if it's a correct answer. The point is show how much you know and how smart you are.

The question is framed to you as a way for you to show you know x, y and z and talk about x, y and z.

Even if a valid solution is just do a, that's great. But the interviewer has no idea if you actually know about x ,y and z do they ?

Re:Nobody Gets Promoted for Simplicity by lucianbr on Wednesday March 04, 2026 @10:23AM (#47248832)
> The point is show how much you know and how smart you are.

I like that this sentence can be read both as a productive, well-meaning view on interviews, as well as a highly cynical one.

Also makes me wonder if the person will keep showing how much they know and how smart they are after they are hired, and if that is a good thing.

Re:Nobody Gets Promoted for Simplicity by Aurornis on Wednesday March 04, 2026 @10:08AM (#47248608)
In an interview you need to explain your thought process and demonstrate that you’re making an informed decision with supporting evidence.

Saying “just use Postgres” and then providing no explanation for why you believe Postgres is sufficient for the job, a general explanation of what type of hardware and architecture you’d use, and other details is not answering the question.

Re:Nobody Gets Promoted for Simplicity by flubijeq on Wednesday March 04, 2026 @10:53AM (#47249311)
The best way to get promoted at stripe is just self-marketing and social manipulation. Good engineers are leaving meanwhile tecnical leadership is being replaced with designers and marketers. Internal performance metrics are heavily manipulated as well. Patrick has completely surrounded himself with extreme sycophants at this point - he has no idea what is actually going on in his company beyond curated metrics produced by manipulative sociopaths.
Re:Nobody Gets Promoted for Simplicity by getnormality on Wednesday March 04, 2026 @10:59AM (#47249405)
Patrick Collison sounds like a lovely, trusting, scientifically-minded man who needs to learn the constructive power of destruction. The power of rage and contempt for bad solutions and bad communication (regardless of intent).

With a smiley face front-end, of course. Wouldn't want to seem not-nice!

Re:Nobody Gets Promoted for Simplicity by flubijeq on Wednesday March 04, 2026 @03:33PM (#47253401)
Agreed, I really like Patrick - he is smart, humble, hardworking and trusting. But his kind and trusting nature is being aggressively exploited by some truly despicable people.
Re:Nobody Gets Promoted for Simplicity by anal_reactor on Wednesday March 04, 2026 @10:01AM (#47248498)
I realized that my manager really confuses complexity with robustness. Case in point: we have a very complicated script that runs at deployment time to determine the address of the database. It's been the source of a few incidents - database wasn't discovered because it was restarting and the script passed an empty string instead of stopping the deployment, script failed because of python update and empty configuration was passed, shit like that. I've been arguing "bro why can't we make terraform create a config file with all the addresses that is directly passed to the app at deployment, or better yet, just copy-paste the database addresses into a file in the repo because we change something there once a year at maximum" but my manager took it as a sign of incompetence and my inability to understand complex systems.

I feel like lots of people just follow the happy path and don't understand that complexity incurs real cost.

Re:Nobody Gets Promoted for Simplicity by PKop on Wednesday March 04, 2026 @09:48AM (#47248243)
It's crazy the original interviewer allowed it to come to this which sounds like a waste of time for everyone involved, instead of simply saying; "Very good that is a legitimate solution to the problem. Now let's pretend you have to build something new, what would you do?"

Why on Earth did the company have to be so willingly obtuse and stupid about it including what sounds like the CEO (well at least he gave him another shot, but there doesn't need to be implicit assumptions about the "point of the interview", just come out and address it head on explicitly.)

Re:Nobody Gets Promoted for Simplicity by renegade-otter on Wednesday March 04, 2026 @09:58AM (#47248431)
I always find it funny that "engineers" straight out of school who barely know how to create a PR are expected to "ace" planet scale design questions. It's. Just. So. Dumb.
Re:Nobody Gets Promoted for Simplicity by yieldcrv on Wednesday March 04, 2026 @10:57AM (#47249391)
“There’s no right answer we just want to see how you think” is gaslighting if there is a right answer and wrong answer.

This should go straight to the DOL, EEOC, FTC and other bodies as some form of abusive labor practice that excises it from the employment process under threat of economic sanctions

Re:Nobody Gets Promoted for Simplicity by alistairSH on Wednesday March 04, 2026 @12:49PM (#47251169)
Completely idiotic on the part of the interviewer. Failing somebody for a correct answer - what a waste of everybody's time. If you want the candidate to pursue a particular technical path, tell them to do so while they're there in the office.
Re:Nobody Gets Promoted for Simplicity by inaros on Wednesday March 04, 2026 @12:59PM (#47251291)
That is why they say, as a candidate, you are also interviewing the company you would be working for...
Re:Nobody Gets Promoted for Simplicity by h3lp on Wednesday March 04, 2026 @02:22PM (#47252495)
Great example, and a lost opportunity in the interview---they should have asked "What are the requirements that would invalidate this answer? and what would you design if the requirements were changed in this way?". Maybe even "how long is the runway for your Progress solution if we consider future scaling up of the requirements"
Re:Nobody Gets Promoted for Simplicity by wpietri on Wednesday March 04, 2026 @04:22PM (#47254077)
> yes you might be right but you also understand what the point of the interview is

To make the interviewer feel smart and powerful? To hire people who will do the thing the boss wants whether or not it makes sense? To find people who will overdesign things to maximize resume impact and the ability of their bosses to talk about what sophisticated systems they're running and for which they therefore need a much bigger budget?

Re:Nobody Gets Promoted for Simplicity by wpietri on Wednesday March 04, 2026 @06:30PM (#47255489)
Just to be clear, I'm absolutely not kidding here. E.g., this is the kind of hiring process I favor: https://williampietri.com/writing/2015/slightly-less-awful-h...

To rethink hiring, you have to spend some time understanding why most hiring is terrible both in terms of candidate experience and actual result. In my view so much of both hiring and general business operations is about managerial status and ego. https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...

Re:Nobody Gets Promoted for Simplicity by bhk on Wednesday March 04, 2026 @04:29PM (#47254152)
Let me guess: the point of the interview was to see if he was a "team player".
Re:Nobody Gets Promoted for Simplicity by kermatt on Wednesday March 04, 2026 @09:26PM (#47256718)
They failed him because of that one question?