News for hackers. Stuff that matters.
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @11:40AM (#20183861)
When interviewing people I usually push until I get the candidate to answer "I don't know" on SOMETHING, just to see if they can do it. Not everyone can, and a lot of people will happily come up with a technical word salad to hide their perfectly understandable ignorance on some obscure technical problem I just came up with. That way you get to hear how they ask technical questions. Asking questions is a valuable (and largely separate) skill too.

It's important to have someone who is able to stop and ask for help instead of going further down a blind alley. I've found it filters out a lot of the know it all types who never mange to get anything done.

I doubt that was the intent of the OP's interviewer, but you never know.

Re:I got asked LeetCode questions for a dev-ops systems engi... by skrebbel on Friday June 14, 2019 @11:48AM (#20183926)
That's a trick question. Trick questions are bad because they test interviewing skill and not programming skill.

It's a trick question because you want the interviewee to answer something different (I don't know) than what you're asking them to answer. Confident applicants might feel up to saying they don't know, but nervous people who are very self conscious in an interview setting may respond completely differently than they would if they were asked the same question on the job by the coffee machine. Their mind would be racing "oh no, I'll look so bad" and they'd go into full panic mode.

Don't ask trick questions. It's smug and useless. Plus you'll be missing out on great smart colleagues who happen to stress out about job interviews.

Re:I got asked LeetCode questions for a dev-ops systems engi... by wool_gather on Friday June 14, 2019 @12:00PM (#20184044)
You make a fair point, but an interview is not solely about programming skill. It's also about being a co-worker. And the question "what does this person do in X situation", where X is "they don't know the answer to something they need to know'" is highly relevant. So there may be a better way to go about it, but the parent's desire is reasonable.
Re:I got asked LeetCode questions for a dev-ops systems engi... by RijilV on Friday June 14, 2019 @12:25PM (#20184241)
The deal is when you’re interviewing me we’re _not_ co-workers. You hold all of the cards and decide my fate.

A big part of interviewing candidates well is breaking down that dynamic. There are many ways of doing it - I get up on the whiteboard first and write out my problem, and stay there until they’ve explained themselves and I need to get back to my notes so I don’t forget stuff. I phrase questions like “I need help implementing this function...” or “how are we going to solve this edge case”.

I don’t think either side of a tech interview is easy. The problem is only one side is evaluated.

Re:I got asked LeetCode questions for a dev-ops systems engi... by WillySchu on Friday June 14, 2019 @01:06PM (#20184592)
> ... The problem is only one side is evaluated.

I'm not sure I agree here. Granted I work for quite a small company, so it's pretty different than working at a company with a significant reputation to help candidates make decisions. But when I interview candidates I'm very aware that they are evaluating me whilst I'm evaluating them.

I actually think this is a good thing. It incentivizes me to make the interview a more pleasant experience, and perform it in such a way that it feels collaborative, like a real work situation, and not as standoffish as some interviews can be. That said, we still do ask hard technical questions solved on whiteboards or in code, and setting them up in such a way that the candidates feel comfortable asking questions on things they don't know / are unclear about is definitely challenging.

To be honest, something I think we (as in the software community at large) lose sight of some times is how unique and challenging performing interviews is. We see stories like this pretty frequently, and we're used to the idea that being interviewed is a fairly distinct skill, orthogonal to what we usually perform in our day to day work life. Something that's talked about a lot less frequently (understandably, more of us are getting interviewed than performing them) is that interviewing others is also a separate skill, and one that really isn't practiced or honed enough in my opinion.

Re:I got asked LeetCode questions for a dev-ops systems engi... by wool_gather on Friday June 14, 2019 @12:35PM (#20184322)
> The deal is when you’re interviewing me we’re _not_ co-workers.

Not yet, but the purpose of the interview is to figure out whether we should be. (And I disagree that it is one sided; this whole topic is about an interviewee's evaluation of the process.)

Re:I got asked LeetCode questions for a dev-ops systems engi... by lbotos on Friday June 14, 2019 @02:41PM (#20185508)
> The problem is only one side is evaluated.

I tell all of my friends that it's your job to interview the interviewer as well. The company is about to get 8 hours of your day for the next few years. figure out how you can figure out if it's the right place for you.

Obviously, if you are in dire straights and you need to take what you can get, sure, but the questions are still relevant and will prepare you for whatever poo you might find yourself stepping into.

Re:I got asked LeetCode questions for a dev-ops systems engi... by jstanley on Friday June 14, 2019 @11:58AM (#20184023)
It's not quite the same as a trick question (which I agree you should avoid). He's not looking for the interviewee to say "I don't know" to any particular question. The correct answer is a perfectly acceptable answer too. The unacceptable answer is to make up bullshit, which is precisely what he's trying to filter out.
Re:I got asked LeetCode questions for a dev-ops systems engi... by asdffdsa on Friday June 14, 2019 @01:49PM (#20185025)
Except that some interviewers say that when they hear "I don't know" it's a sign that the interviewee gives up easily and extrapolates that they will give up easily when they encounter problems while working. The point is that as an interviewee you're supposed to "know" an unfair amount of knowledge and have incredible spontaneous algorithmic skills to boot (the interviewer picks 1 question and has the answer while the interviewee anticipates and is expected to competently answer the set of all possible questions). What ends up happening is everyone crams for interviews by rote memorizing common system design and coding questions. From the interviewee's side it's a "damned if you do, damned if you don't" scenario when OP asks his trick question. This is similar to hazing where initiates are unsure of the correct way to conduct themselves because they are being judged by some vague, perhaps intentionally withheld ideal, standard, or cultural archetype. I'd imagine disenfranchised groups would disproportionately 'fail' this question, as they are already insecure of their belonging in tech culture
Re:I got asked LeetCode questions for a dev-ops systems engi... by mondoshawan on Friday June 14, 2019 @12:04PM (#20184077)
In the process you are pushing the candidate to the breaking point and eliminating any confidence they may have had in their abilities. They will end up demoralized and most likely fail the following interviews if they're the nervous sort. If they're smart, they'll bid you goodbye and you end up with a black eye reputation.
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @12:14PM (#20184160)
Any interview (of mine) is a conversation - they're not something you pass or fail - it's just a way for a potential employer and employee to get to know one another so they can make better decisions. Nobody won, lost, passed or failed. The interview is just there to provide more information to determine if the potential employer and employee would fit well together.

If I were in an interview that was presented as a zero sum game I would walk out too.

Re:I got asked LeetCode questions for a dev-ops systems engi... by Balgair on Friday June 14, 2019 @12:28PM (#20184269)
> Nobody won, lost, passed or failed

I mean, like, yeah they did. They either got the job or they did not.

Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @01:04PM (#20184559)
The interview is there to provide more information about a possible relationship. Winning an interview is like winning a date (assuming you want a relationship with the other person.).
Re:I got asked LeetCode questions for a dev-ops systems engi... by varjag on Friday June 14, 2019 @02:08PM (#20185208)
A special kind of dating where money are involved.
Re:I got asked LeetCode questions for a dev-ops systems engi... by jkdufair on Friday June 14, 2019 @01:44PM (#20184981)
If I were the interviewee and discovered it was a poor fit, I’d consider the lack of an offer or the opportunity to refuse one a win
Re:I got asked LeetCode questions for a dev-ops systems engi... by Balgair on Friday June 14, 2019 @02:20PM (#20185324)
Granted, this is tech, so finding a paying job isn't too terrible. But with a lot of other industries [0] it takes a long time and a lot of effort to get employment. I'd say for most US workers, even in today's market, not getting the job is a loss.

[0] which is not really super relevant to this discussion, I know.

Re:I got asked LeetCode questions for a dev-ops systems engi... by positivejam on Friday June 14, 2019 @01:25PM (#20184764)
> nervous people who are very self conscious in an interview setting may respond completely differently than they would if they were asked the same question on the job by the coffee machine.

This part is crucial. If an interviewee is pushed to the brink but doesn't say, "I don't know," that does not imply they will not say, "I don't know," once they've secured a position.

Re:I got asked LeetCode questions for a dev-ops systems engi... by notyourwork on Friday June 14, 2019 @11:58AM (#20184022)
It’s not a trick question. Saying I don’t know is a perfectly acceptable answer. The follow up should be questions to clarify or reduce complexity. I interview a lot and this is something I expect out of candidates.
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @11:53AM (#20183980)
Saying "I don't know" is an accurate answer.

The ability to ask meaningful questions is a big part of any programming job. And (in my opinion) harder to learn than any particular technology.

Re:I got asked LeetCode questions for a dev-ops systems engi... by UweSchmidt on Friday June 14, 2019 @12:23PM (#20184227)
Maybe you could give the critical replies to your comment some consideration. There seem to be many interviewers who abuse their temporary power over candidates by freestyling a psychological excercise, and brag about it in threads like this.

In a way forcing the other party to give up with an "I don't know" is humiliating, and graciously allowing this answer doesn't make things better. You'd put yourself above the other person.

Imagine you'd interview someone you truly respect, a luminary of Open Source walks in. How would you go about the interview then?

I think a great interviewer can make the interview an enlightening and wholesome experience for both parties - while easily identifying the exact qualifications and the fit of the candidate.

Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @01:19PM (#20184713)
I thought I had given consideration. I do not regard "I don't know" as giving up. Giving up would be not finding the answer eventually. I certainly don't find myself "under" some other person if they know the answer to a particular technical question.

As for interviewing a luminary of open source what would be the difference? I imagine they (much like everyone else) don't know lots of things and are probably comfortable saying so. Their answers to how they would go about finding an answer would probably be wonderful.

Re:I got asked LeetCode questions for a dev-ops systems engi... by UweSchmidt on Friday June 14, 2019 @04:09PM (#20186258)
Fair enough.

Of course it depends a lot on the overall tone of the interview, and as I read more I'm sure you're doing it very well.

Re:I got asked LeetCode questions for a dev-ops systems engi... by NoodleIncident on Friday June 14, 2019 @02:04PM (#20185160)
You can call it whatever you want, but I think if a candidate would be humiliated by saying "I don't know" in an interview, that's a strong negative signal. Saying "IDK" and reading the docs, googling it, or asking for help is at least half of the job.
Re:I got asked LeetCode questions for a dev-ops systems engi... by ThrowawayR2 on Friday June 14, 2019 @01:05PM (#20184579)
"I don't know" is something that developers encounter weekly, if not daily. There's nothing humiliating about acknowledging that there are things one doesn't know, whether in our daily jobs or in an interview.
Re:I got asked LeetCode questions for a dev-ops systems engi... by mondoshawan on Friday June 14, 2019 @11:57AM (#20184015)
Saying "I don't know" like this in an interview scenario is nearly impossible for most candidates and only serves to humiliate rather than prove their abilities.

If you want to see them ask questions, give a half explanation of the problem at hand instead and guide them to ask more detailed technical questions.

Be an ally, not an adversary, and you will find talent better than if you push.

Re:I got asked LeetCode questions for a dev-ops systems engi... by rifung on Friday June 14, 2019 @12:33PM (#20184307)
> Saying "I don't know" like this in an interview scenario is nearly impossible for most candidates and only serves to humiliate rather than prove their abilities.

I don't think this is true only in interviews though. I have worked with people who can't seem to admit they don't know something and they're difficult to work with.

It's completely fine if you can't do something. What's not fine is that you fail to communicate it to those around you and create false expectations.

That being the case, I think it's fair to score a candidate negatively if they aren't able to say they don't know something.

Re:I got asked LeetCode questions for a dev-ops systems engi... by notyourwork on Friday June 14, 2019 @12:01PM (#20184051)
It’s really not - as someone whose done 100s of interviews for a brand name tech company I don’t see this as a problem. The goal being for candidate to indicate their lack of knowledge but work through it. As an engineer you will encounter problems you don’t know how to solve. Pretending you know and bullshitting is a red flag.
Re:I got asked LeetCode questions for a dev-ops systems engi... by mondoshawan on Friday June 14, 2019 @12:06PM (#20184095)
There are hundreds of ways to do this without intentionally tilting the candidate into failure later. As an interviewer you have absolute authority in the room -- don't abuse it and destroy the candidate.
Re:I got asked LeetCode questions for a dev-ops systems engi... by notyourwork on Friday June 14, 2019 @01:11PM (#20184639)
I think you are misunderstanding my point by indicating that interviewer's shouldn't abuse their power.

To be specific, I do a lot of things up front in an interview to help the candidate. The most important is informing them that they should treat technical exercises as a team exercise where we are teammates working together. Furthermore, I declare that there is no penalty for my assistance during the interview. The idea is for us to work together to solve a problem, my interest is in how they think and work through the problem. Furthermore, I explicitly tell them for discussion on prior experience and technical facets of interview that they are welcome to indicate they do not have an answer to my question or are unsure what's next.

All of this combined creates a very pleasant experience which is an important part of my goal as an interviewer. I'm not trying to embarrass people, though I am trying to make a informed hiring decision which is a very expensive endeavor for my company. Therefore, beyond letting candidate enjoy themselves, my main focus is to ensure that I have sufficient confidence to hire or be willing to walk away due to lack of conclusive data.

Re:I got asked LeetCode questions for a dev-ops systems engi... by jvreagan on Friday June 14, 2019 @12:19PM (#20184197)
You are proving the OPs point: they are looking for people where "I don't know" is acceptable in collaborating with others, not for people where saying "I don't know" is considered a failure or humiliating. If someone is humiliated being asked a question they don't know the answer to, then they aren't a culture fit.

As Jeff Bezos says, the older he gets, the more he realizes he doesn't know.

Most people have no issue with saying "I don't know." I've worked with people that can't say "I don't know" - they are incredibly toxic.

Re:I got asked LeetCode questions for a dev-ops systems engi... by sigstoat on Friday June 14, 2019 @01:00PM (#20184525)
> Saying "I don't know" like this in an interview scenario is nearly impossible for most candidates and only serves to humiliate rather than prove their abilities.

with hacker news so utterly convinced that employers have literal powers of life and death over their employees, when do you expect the potential employee to regain the ability to tell their employer that they don't know? after they've quit their previous job and moved across the country? a week after that? six months? maybe after they've got some kids?

Re:I got asked LeetCode questions for a dev-ops systems engi... by ViViDboarder on Friday June 14, 2019 @12:30PM (#20184289)
It’s not a trick question. I am expecting them to answer the questions honestly. If they know the answer, go ahead and answer correctly. If not, don’t pretend.

I don’t want to hire someone who isn’t going to admit the limits of their abilities, for whatever reason. Could be smugness or lack of confidence, either way it’s a bad signal.

Re:I got asked LeetCode questions for a dev-ops systems engi... by autokad on Friday June 14, 2019 @01:45PM (#20184989)
its a trick question, period. The question is formulated with the expectation that it cant be answered, even if there is a small chance to answer it right.

its not a bad signal. to be honest its the smartest thing to do (like guessing on the GRE), especially since most people ask questions they expect the right answer too.

the only bad signal I see is in you. I would wager to say, in most situations in life, don't play tricks, just ask the question you really want answered.

Re:I got asked LeetCode questions for a dev-ops systems engi... by g-clef on Friday June 14, 2019 @01:44PM (#20184975)
As a lot of other commenters are pointing out: there's an adversarial and a non-adversarial way to do this.

When I'm interviewing someone I will often preface groups of questions with "have you worked with {x}?" or "are you comfortable answering questions about {x}?" before asking the actual questions covering that area. A simple intro question like that goes a long way towards keeping an interview friendly. The interviewee can say "no" to a small-sounding question without feeling like they're embarrassing themselves.

For example, they may be comfortable with Python but not super-comfortable with the GIL/multiprocessing/multithreading. If I ask "have you worked with Python's multiprocessing or multithreading before?" that comes across as much less adversarial than asking them to describe Python's GIL and forcing them to say "I don't know."

Doing an intro question also allows them to give a partway answer like "I've touched it before, but I wouldn't call myself an expert". If they say something like that I can re-focus my questions to another area, or just ask higher-level questions, rather than hitting them over the head with a deep question about something they've just told me they're not an expert in.

You do want people to be honest about their own limitations, but you don't want your interviewee to think that your organization is driven by macho posturing about being King Nerd.

Re:I got asked LeetCode questions for a dev-ops systems engi... by mondoshawan on Friday June 14, 2019 @11:54AM (#20183991)
This will easily pitch you into an adversarial position and give you and your company a black eye. Remember: interviews are bidirectional. If I was pushed to the breaking point like this in your interview, I'd walk out without saying a word.

You're only going to be selecting candidates who can handle pressure -- not skill or ability with this.

Re:I got asked LeetCode questions for a dev-ops systems engi... by chucksmash on Friday June 14, 2019 @12:23PM (#20184221)
You're already treating it as adversarial if you're thinking of it in terms of your "breaking points" and "walking out without saying a word."

Back in the day I had an interview for a business position where the interviewer's personal printer mysteriously started printing documents part way through. I'd just read "What Does Somebody Have To Do To Get A Job Around Here?" which listed that among other tactics a company might use to see how you handled distractions. I've suspected it was on purpose ever since. Even were it intentional though, it would be more of a gimmicky ploy than an adversarial thing to do.

An interviewer should be able to modulate the difficulty of a question without making you feel uncomfortable.

Also the job isn't done in a vacuum - being able to remain calm when you don't know the answer is an ability all its own. Interviewers shouldn't be creating artificially stressful situations but you've also got to be able to manage your own stress response!

Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @12:04PM (#20184074)
Interviews are certainly bidirectional - and should be conducted as conversations, not third degree interrogations. I would walk out on that too.

How is being asked something you don't know the answer to being pushed to the breaking point? Do we expect to learn nothing on our jobs?

Re:I got asked LeetCode questions for a dev-ops systems engi... by whymauri on Friday June 14, 2019 @05:50PM (#20186951)
My favorite interviews are the ones that have pushed me to the edge of my knowledge and had me derive things that were completely new to me. I love interviews that are genuinely enlightening, which is the opposite of regurgitating Leetcode.

Truly, the best interviews I've had have also been the hardest. Different strokes for different folks.

Re:I got asked LeetCode questions for a dev-ops systems engi... by malvosenior on Friday June 14, 2019 @11:45AM (#20183907)
Doing this during a job interview is not going to give you the results you expect. For every person like you who wants to hear "I don't know" there are 10 people who will pass on you for not knowing something. People's expectations are set by the worst interviewers they experience, not the best (and honestly, trying to trap people isn't the "best" anyway).
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @11:57AM (#20184012)
So far it's worked very well for me. Since I've started using it (admittedly my sample size is small) I've found some very effective programmers, and automatically filtered out a lot of egotistical types. Software is usually a collaborative effort and this technique helps in that regard.
Re:I got asked LeetCode questions for a dev-ops systems engi... by malvosenior on Friday June 14, 2019 @12:00PM (#20184034)
As another commenter mentioned, you're probably doing more damage than you realize. A lot of more experienced people are going to recognize this as toxic behavior and word will get out that your company isn't healthy. You may not even notice, but this kind of thing will keep the best people out of your pipeline if you continue to do it.

> Since I've started using it (admittedly my sample size is small) I've found some very effective programmers,

This is not the only way to find very effective programmers. You should level up your own ability to discovery this in someone in a non antagonistic and more straightforward manner.

Re:I got asked LeetCode questions for a dev-ops systems engi... by mondoshawan on Friday June 14, 2019 @12:01PM (#20184050)
I've done well over 200+ interviews myself, and been on hiring committees where I have had chances to review other interviews. This kind of behavior usually trashes the following ones and aets the candidate up for failure.
Re:I got asked LeetCode questions for a dev-ops systems engi... by collyw on Friday June 14, 2019 @12:10PM (#20184130)
To be fair I have "fessed up" to not knowing about a subject that was mentioned on my CV where I had used the tech a little bit 5+ years ago. Been offered the job both times. Though I could see if you hadn't had that experience it wouldn't be the answer that you would want to give.
Re:I got asked LeetCode questions for a dev-ops systems engi... by mywittyname on Friday June 14, 2019 @05:22PM (#20186770)
I don't know about others, but I expect people to have some fluff on their resumes. I don't blame them because recruiters and HR types love fluff, so fluff gets your foot in the door. Recruiters might skip over a person who has MongoDB on their resume instead of Elasticsearch because they don't know they are similar technologies. So it's reasonable that a candidate hold the recruiters hands.

If candidates come out and say such when I ask them questions about it, I'll just move on. I won't hold it against them unless it happens excessively.

Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @01:11PM (#20184641)
As a recruiter or an employer? I've only done "employer type" interviews.
Re:I got asked LeetCode questions for a dev-ops systems engi... by depr on Friday June 14, 2019 @11:58AM (#20184020)
How do you know whether the ones that were filtered out were egotistical?
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @12:06PM (#20184094)
Largely because they were making things up and changing the subject instead of answering honestly.
Re:I got asked LeetCode questions for a dev-ops systems engi... by rifung on Friday June 14, 2019 @12:35PM (#20184323)
I once told an interview I didn't know something and they told me that I should never say I don't know something and just try to make something up.

I don't really agree with him and just kept doing it though and things seems to be fine.. If anything I would say that interview was successful for both parties because we probably wouldn't get along and that is totally fine.

Re:I got asked LeetCode questions for a dev-ops systems engi... by superturkey650 on Monday June 17, 2019 @10:45AM (#20203481)
I was told something similar by my high school history teacher Mr. Kolhaise, but I think it was phrased in a more helpful manner and it's always stuck with me.

He said "Don't just tell me what you don't know, tell me what you do know" or in other words, don't just say "I don't know" but say something like "I don't know, but based on what I do know this is what I think the answer would be and this is how I would figure it out".

It really helps that everyone forgets what people say before the "but" and you can help get across the idea that while you may not know everything you know how to figure things out.

Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @02:24PM (#20185369)
That is the goal of an interview! You ended with more information that you had before.
Re:I got asked LeetCode questions for a dev-ops systems engi... by drugme on Friday June 14, 2019 @01:20PM (#20184718)
When interviewing people I usually push until I get the candidate to answer "I don't know" on SOMETHING,

"just because I can". To me this technique comes off as condescending and manipulative, and smells like a power play basically. Not to mention - the better candidates will pick up on it, and your company will eventually get a reputation it doesn't want to have.

And really there's no need for it. Time and time again, I find that just by having a normal technical conversation with someone, on virtually any topic that they claim to have expertise in -- they will show their strengths and weakness (and propensity for BS, if any) very, very quickly.

Re:I got asked LeetCode questions for a dev-ops systems engi... by charlieo88 on Friday June 14, 2019 @02:11PM (#20185228)
You seem like a person that has never had to deal with someone that is incapable of saying "I don't know." It is incredibly frustrating to project manage a team like that. It is tantamount to lying.
Re:I got asked LeetCode questions for a dev-ops systems engi... by drugme on Sunday June 16, 2019 @03:10PM (#20197297)
Sure I have - and like I said - it's easy to read this behavior from simply having a normal (but let's just say slightly inquisitive) conversation with someone. In fact even in recent memory I can think of multiple occasions where this behavior has emerged, simply when trying to get to the bottom of routine technical matter.
Re:I got asked LeetCode questions for a dev-ops systems engi... by Stronico on Friday June 14, 2019 @01:37PM (#20184892)
Not just because I can - interviews are always time limited, and technical conversations always (pleasantly) meander across many topics, usually the strengths of the people talking. It's easy to for someone to spend an hour talking about their strengths - interviews usually need some sort of direction to get useful information.

And it would be manipulative if there were some answer I was going for that wasn't true - I'm trying to elicit an honest response.

Re:I got asked LeetCode questions for a dev-ops systems engi... by mrunkel on Saturday June 15, 2019 @08:45AM (#20189752)
I do something similar, I ask the candidate what they do when three different people come to them with urgent needs that must be done immediately and there is no way that they can do them in the time given.

The answer I’m looking for is “I ask for help.” Or “I talk to my manager.” They don’t fail if they don’t answer it that way, but it’s a good starting point for a conversation about why they didn’t say that.

For me, interviewing is more about getting to know someone and how they think than checking off various skill boxes.

Re:I got asked LeetCode questions for a dev-ops systems engi... by diminoten on Friday June 14, 2019 @12:36PM (#20184331)
Haha, I usually say "I don't know" right away, I feel like I'd short circuit this test.