News for hackers. Stuff that matters.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by gabereiser on Saturday July 01, 2023 @07:42AM (#36549064)
What kills me is the fact that the interviews (especially the technical ones) go in depth into topics that aren’t ever pertinent to the job. It’s simply so the interviewer can rank you vs themselves. You need to be good but not too good you’re a threat.

The best interviews I’ve ever taken and in turn, host, are the ones where we break down a problem with low code, no gotchas, little examples of specifics just to make sure they know how to write it in language of their choice. That they understand the problem, can satisfactorily break it down into actionable tasks, and come up with a solution to the problem.

Everything else: tech stack, jira, agile, culture - is company specific and should be taught to your employees and not be made the bar. If you need someone who can hit the ground running you can focus on a tech stack but ultimately it’s up to you, the company, to ensure they fit. Not the new hire.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by rewmie on Saturday July 01, 2023 @08:24AM (#36549346)
> What kills me is the fact that the interviews (especially the technical ones) go in depth into topics that aren’t ever pertinent to the job. It’s simply so the interviewer can rank you vs themselves. You need to be good but not too good you’re a threat.

Story time.

A few years back I was in hiring loops as an interviewer. Half a dozen engineers in my company interviewed a candidate during a morning. Everyone had their notes and we were discussing if we should hire the guy or not. Everyone gave thumbs up except one engineer. It turned out he tested the candidate on data structures and algorithms, and the candidate hadn't memorized the computational complexity of some bullshit algorithm that only shows up in lame trivia games no one cares about. Based in that, that particular interviewer gave thumbs down. We discussed everything, went through all notes, and ultimately based on all feedback the hiring leader gave a thumbs up. The data structures engineer threw a tantrum. In his opinion, we would be lowering the hiring bar if we hired a candidate that failed to meet his bar on what he felt were basic competences. The hiring leader asked how many times he used that algorithm in his everyday work. The data structures engineer answered that alas he never used it at all, but still he felt that everyone working in his org should know that.

I feel some companies don't have good hiring managers and give free reign to bad engineers who have no idea what it takes to deliver production code.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by roland35 on Saturday July 01, 2023 @08:28AM (#36549375)
That is a major problem in interviewing. Everyone has their own set of internal guidelines!

I have worked on teams trying to improve our interviewing process, and one key goal was aligning everyone in exactly what technical and personal attributes we were trying to hire for.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by rewmie on Saturday July 01, 2023 @08:04PM (#36556678)
In my anecdote, we already had very explicit and rigorous guidelines. We had goals, evaluation requirements, question banks, and more importantly post-interview meetings where all interviewers matched notes and we're tasked with gathering data on topics that overlapped the responsibilities of other interviewers.

Even so, the data structure engineer cracked open Trivial Pursuit on the candidates and wanted to reject him based on one answer alone.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by roland35 on Sunday July 02, 2023 @08:42AM (#36560947)
Yup, some people just seem to have a hard time with evaluating candidates fairly rather than by some arbitrary guidelines inside their head.

Of course if you're looking for a software jeopardy contestant maybe memory recall is important, but for the rest of us it is much better to have a good understanding of fundamentals and know where to look when it comes to specifics!

Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Saturday July 01, 2023 @09:54AM (#36550136)
That’s why you need experienced hiring managers. The questions should be discussed and approved before the interview. You just don’t let an engineer ask whatever they want. An interview plan needs to be shared to avoid overlapping questions or topics between interviews. In this particular example the hiring leader did the right thing, only after doing the wrong thing: not review or having an interview plan discussed beforehand and training the interviewers. The interviewing principles need to be clear to all your interviewers.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by rewmie on Saturday July 01, 2023 @08:01PM (#36556646)
> You just don’t let an engineer ask whatever they want.

In my anecdote, the data structure engineer was indeed tasked with evaluating the candidate on his data structures knowledge. Except that the candidate had guidelines that went in the line of assessing basic understanding and proficiency in following an algorithm, but instead opted to make it a game of Trivial Pursuit.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by goostavos on Saturday July 01, 2023 @02:31PM (#36553433)
This personality defect is painfully common. They view themselves as "the bar."

It's always trumped up nonsense blown out of proportion. In one debrief, they made a stink because they botched an implementation of a red-black tree. it was the most pretty, trivial nonsense. The only time people are implementing red-black trees by hand are... when they're studying for our bullshit software interviews.

We also had a guy with a Ph.D in.. something. He wanted everyone to know he was very smart. Especially the interviewees. The problem he asked was so bizarre and complex that it took those of us already at the company several hours to figure it out upon giving it a try. it's just, like, dude, what is the point of what you're trying to do here? How small is your ego that you need to bully strangers on irrelevant nonsense?

Re:Leveling Up in Job Interviews for Software Engineers (2022) by roenxi on Saturday July 01, 2023 @08:50AM (#36549553)
> You need to be good but not too good you’re a threat.

For what it is worth; based on what I've seen in interviews. Programmers can only rank people who are close to their own level. If someone like Terry Davis of TempleOS fame shows up for an interview, should the interview declare them as a madman? a genius? both? If we need to build an OS, are his design choice eccentricities sly moves of genius or evidence of a diseased mind?

It isn't as much that strong programmers are a threat (that might be a factor) but more that big gaps in though lead to both productivity and inscrutability. And people avoid things they don't understand.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Saturday July 01, 2023 @09:59AM (#36550192)
That’s why assembling an interview panel requires some finesse. How senior the candidate is expected to be needs to be calibrated and interviewers selected accordingly to seniority and domain expertise. Not always possible, so it’s always imperfect. Assessing performance is really hard, even more so with limited interview time that requires determining not only hire or no hire, but also level and compensation.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by golergka on Saturday July 01, 2023 @11:06AM (#36550905)
I would hire him in a heartbeat if, and only if, the team I would be hiring him for would be a team of one.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by Roark66 on Saturday July 01, 2023 @09:08AM (#36549686)
Personally I really dislike very specific questions you can Google an answer to in 3s and consequently no one remembers it while doing an actual job. IMO when it comes to verification of actual technical ability the candidate should be told an example of an actual task she/he would be expected to complete routinely and they should either do it during the interview or explain how would they go about doing it.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Saturday July 01, 2023 @09:48AM (#36550082)
I get what you mean I think. However if you’ve been doing C dev for several years and you “don’t remember” what a static variable is and when to use it (or not) is not a great sign. Cumulative signals is what determines hire or no hire, not a single “wrong answer”. Even when a candidate doesn’t know an answer you can get useful signals. If you give them the answer or hints and see how they react or a follow up question after giving them the answer.

You can google many things easily. Understanding the answer and knowing how to apply it to different problems matters a lot more. I still expect some concepts and definitions to be remembered if you’re claiming expertise in a topic.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by badtension on Saturday July 01, 2023 @11:45AM (#36551324)
Static variable sure but there are many other examples, like returning a C fixed-size array from a function. I had this question asked and they specifically insisted on being compliant with the standards and not using an out-argument. This is a ridiculous question.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by _a_a_a_ on Saturday July 01, 2023 @12:17PM (#36551721)
> they specifically insisted on being compliant with the standards

that's wrong?

Re:Leveling Up in Job Interviews for Software Engineers (2022) by badtension on Saturday July 01, 2023 @12:57PM (#36552111)
No, but this is a very niche thing to know and if I remember correctly gcc has a widely used specific extension for that which would not be accepted in that case.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Sunday July 02, 2023 @12:36PM (#36563064)
Being pedantic about standards and expecting people to recite them perfectly as a way to assess skill or seniority is what is wrong. Even when you are implementing a 'standard' there's room for robustness principles (liberal in what you accept, strict with what you send) that should be weighted instead of blindly following a 'standard'.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by publicmail on Saturday July 01, 2023 @02:23PM (#36553330)
Agreed. I’ve been doing C development for the last 10 years and I’ve never seen that. I would have put it inside a struct and returned that.

I hate those types of trick questions.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Sunday July 02, 2023 @12:32PM (#36563024)
I guess my point is that what you really dislike are niche pedantic gotcha questions, not 'very specific questions you can Google an answer to in 3s'. I fully agree with that btw.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by pphysch on Saturday July 01, 2023 @01:44PM (#36552762)
One question I asked recently was "what is the `with` statement in Python for?" If they ask for clarification I'll mention related terms like "context management" and "RAII", which we could discuss without Python syntax.

Yes, they can Google the answer in 3s.

Yes, I could also ask a long-form question about how they would approach wrapping an IO interface in Python.

But if they don't understand `with` or resource/context management, the chances that they would produce a reasonable answer to the long-form question are tiny. They will produce an answer anyways, and it will likely be a waste of time. So we cut to the chase and target the core concepts directly.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by mhss on Saturday July 01, 2023 @09:34AM (#36549934)
I’m not going to justify going in depth in topics not relevant for the job. However going deep in tech topics is necessary to evaluate experience and seniority. The “best interviews” process you described is adequate for the first eng levels but if you want to interview for senior, staff, principal; etc it gets harder and going into depth and breadth is necessary.

Heck. Sometimes going into topics “not relevant” for the job is revealing. If their cv says they spent 5yrs writing Linux dev drivers but the position is to write golang web services I may still ask about device drivers if I can get a domain expert. Good people tend to understand very well the things they’ve worked on.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by jagged-chisel on Saturday July 01, 2023 @10:05AM (#36550251)
‘going into topics “not relevant” for the job is revealing‘

I would suggest anything on the applicant’s cv is fair game. What makes no sense is asking about removing duplicates from a linked list when that’s nowhere near what the job will entail.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by jonathankoren on Saturday July 01, 2023 @11:41AM (#36551274)
It’s literally an intro test question that you can figure out if you know what a linked list is. It’s not that big of a deal.

Now trying to remember a specific algorithm like red-black tree rotation or Djikstra’s is something completely different

Re:Leveling Up in Job Interviews for Software Engineers (2022) by softfalcon on Saturday July 01, 2023 @09:44AM (#36550037)
Yeah, I try and background check my interviewer thoroughly because of the “threat” issue. I always ask who will be interviewing me and look them up.

I specifically try and answer their questions and “hold back” a bit when answering if I can. I also sometimes will drop a nugget of knowing more and study their reaction. Some interviewers react quite poorly if you hint you know considerably more about a subject than they might want you to know.

I have friends with a lot more education than myself (PhD, masters, very senior) and they say they have to do this A LOT.

The goal is to see how the interviewer handles not being the smartest in the room about everything. This is a big deal because it can suss out whether the other person is “on good behaviour for the interview” but otherwise has an enormous ego during regular work hours.

No one wants to work for an ego maniac vetting out all the A+ candidates out of fear of competition.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by angarg12 on Saturday July 01, 2023 @11:49AM (#36551374)
I never heard about having to do this during an interview, but it sounds concerning.

My advice would be to not play mind games and just interview as yourself. Interviews go both ways, so if your interviewer is a psychopath you'd want to know sooner. Then just give the job a pass.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by dallasg3 on Saturday July 01, 2023 @01:49PM (#36552840)
Psychopaths can be the best chameleons though.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by lowdest on Saturday July 01, 2023 @01:52PM (#36552885)
True in aggregate, but special conditions exist. E.g. when interviewing for a rarely available position with extraordinary compensation.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by redditor98654 on Sunday July 02, 2023 @06:39AM (#36560176)
I have done 300+ interviews in a 13 year career in FAANG companies and anytime I get a sense a candidate knows more than me, I get all excited and will work extra hard in the debriefs to get the person hired. If the spot is for my own team, even better ans will nudge my manager to hire the candidate. The prospects of learning from the person on the job is too enticing.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by GeorgeTirebiter on Sunday July 02, 2023 @04:03PM (#36565107)
Good for you! Andrew Carnegie said something like "I don't know how to make steel, but I do know how to HIRE the men who do!" He wasn't threatened by competence.

However, my experience with FAANg companies is: the interviewers cannot handle an interviewee who knows more, has more experience, and who comes up with better solutions to their stock 'whiteboard' problems.

Such a person should not squander his/her talents in a FAANG. That's why there are start-ups.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by sokoloff on Saturday July 01, 2023 @09:44AM (#36550039)
> You need to be good but not too good you’re a threat.

I will happily hire someone who’s a threat to take my job. If I don’t, I can’t ever move up either.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by softfalcon on Saturday July 01, 2023 @09:50AM (#36550100)
This is the right way to take it, but unfortunately many don’t see it this way.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by scarface_74 on Saturday July 01, 2023 @10:00AM (#36550200)
With most employees not staying at a job for more than two years, why wouldn’t you hire someone who can hit the ground running? If they spend six months doing negative work ramping up and leave in two years, your investment in them didn’t go far.

Yes, I know the answer is to keep them at market wages and don’t fall into the salary compression trap.

But often that isn’t under your control as a hiring manager. HR won’t give you a budget for raises. But will give you the budget to hire at market rates.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by solarmist on Saturday July 01, 2023 @11:16AM (#36551019)
Because, as mentioned, it’s a fantasy that someone can step in and understand the peculiarities of a new company without ramp up time.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by scarface_74 on Saturday July 01, 2023 @11:28AM (#36551143)
There are two things to ramp up on - the technology and the business.

If they know the technology that’s one less thing to worry about.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by solarmist on Saturday July 01, 2023 @11:44AM (#36551302)
And you can know 100% of the technologies they use; open the repo and still say,

“what the hell were they thinking using X like Y!”

“Why didn’t they use Y here”

“Oh man, this looks like monkey patched code from 2 full versions ago, the right way to handle this now would be 1/3 the code, but oh they can’t update it because they’re mutating the data structure in order to Z… Fuck…”

Re:Leveling Up in Job Interviews for Software Engineers (2022) by scarface_74 on Saturday July 01, 2023 @12:37PM (#36551927)
Everyone thinks what came before then was done stupidly.

With maturity, you realize whatever they did worked well enough to get the company to a position where they were able to hire you.

As Corey Quinn (a well known “cloud economist”) says, “legacy software is software that generates revenue”.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by solarmist on Saturday July 01, 2023 @12:56PM (#36552102)
That wasn't the point. You missed the context or something. Those were just examples of initial thoughts that come up when starting to understand a new codebase.

My point was exactly the opposite and parallel to what you said. But even with experience it takes time to decode those decisions.

The point is that it takes time to understand the whys of code that is counterintuitive at first.

Even if you are a 100% match for the technology.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by eulers_secret on Saturday July 01, 2023 @01:36PM (#36552640)
It depends on domain, and we have mostly webdevs in this thread.

When I joined a kernel gfx driver team, the expected ramp time was ~6 months. My friend working on Mesa had a >1 year ramp time!

If I open the source for a Django or React app, I can get to fixing bugs in a few days or less. It just depends.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by solarmist on Saturday July 01, 2023 @01:59PM (#36552999)
Sure, it's most dependent on the age of the company/software. The older, or lower level the code, the more hacks and workaround that appear in a codebase.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by epicureanideal on Saturday July 01, 2023 @11:21AM (#36551074)
Sounds like HR shouldn’t be in charge of deciding engineering salaries and raises. Seems like HR creates more problems than it solves. Time to reduce the scope of their roles.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by isbvhodnvemrwvn on Saturday July 01, 2023 @11:44AM (#36551298)
It's not HR that decides that, it's management. HR just enforces it.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by redditor98654 on Sunday July 02, 2023 @06:45AM (#36560207)
Yeah, upper management and the finance department.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by ahoka on Saturday July 01, 2023 @01:15PM (#36552341)
Do you think HR decides salaries? Do yo also think cashiers set the price of bread?
Re:Leveling Up in Job Interviews for Software Engineers (2022) by goostavos on Saturday July 01, 2023 @02:18PM (#36553248)
Reading comprehension: the person you're replying to is replying to the statement: "HR won’t give you a budget for raises"
Re:Leveling Up in Job Interviews for Software Engineers (2022) by isbvhodnvemrwvn on Saturday July 01, 2023 @04:14PM (#36554627)
Thinking comprehension - who determines budget?
Re:Leveling Up in Job Interviews for Software Engineers (2022) by ren_engineer on Saturday July 01, 2023 @01:44PM (#36552761)
if "most" engineers are staying for less than 2 years you either have a culture problem or aren't matching market rates for compensation
Re:Leveling Up in Job Interviews for Software Engineers (2022) by esafak on Saturday July 01, 2023 @03:47PM (#36554291)
That's twice as long as Google's average tenure.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by ren_engineer on Saturday July 01, 2023 @05:05PM (#36555219)
that number comes from their hiring spree when around 20% chunk of their workforce had 0 years of tenure, the data was pulled from LinkedIn and includes all employees or people claiming they are employees
Re:Leveling Up in Job Interviews for Software Engineers (2022) by jagged-chisel on Saturday July 01, 2023 @10:01AM (#36550215)
Allow me to add.

“If you need someone who can hit the ground running…” then you need to have documented the crazy decisions that led to the awkward implementation that is your product. I have yet to meet a company who is using standard, recommended, tried-n-tested, well-known solutions to typical problems. Unless you write docs or stick to standards, no outsider has the context to “hit the ground running.”

Re:Leveling Up in Job Interviews for Software Engineers (2022) by SonOfLilit on Saturday July 01, 2023 @11:54AM (#36551441)
Some people can still hit the ground running when there is a complex codebase with zero docs. They are just very expensive.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by QuercusMax on Saturday July 01, 2023 @12:53PM (#36552085)
Last three times I've joined a new team (2004, 2015, 2017) I spent my first week trying to fix tiny bugs and generally just reading my way through the codebase till I understood what was going on. I highly recommend it.

I learned to do this when I was working on my master's, and my advisor suggested a project to me, and when I asked him for help figuring out where to start, and he told me to read through the code until I understood it, and come to him if I spent more than an hour or two stuck on things. Thanks, Mikhail - your advice was fantastic.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by not_alexb on Saturday July 01, 2023 @01:31PM (#36552569)
That only works if the code was written in a semi-digestible format; I've met my fair share of monstrosities that were propped up by race conditions -- you're not going to briskly digest them in a week (especially if you're in the unlucky circumstance of only having a single breakpoint per run and the engineers who had any understanding of it haven't worked there in 20 years).
Re:Leveling Up in Job Interviews for Software Engineers (2022) by SnorkelTan on Saturday July 01, 2023 @03:22PM (#36554017)
Test cases can be a good place to start because they are usually clustered around business critical functionality. Or problematic legacy code that needs to work :)
Re:Leveling Up in Job Interviews for Software Engineers (2022) by not_alexb on Saturday July 01, 2023 @03:41PM (#36554243)
I wish that was an option for at least half the codebases I've worked on. Tangent: you'd be surprised how many life threatening codebases have little to no tests at all.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by snovv_crash on Saturday July 01, 2023 @04:57PM (#36555128)
I've twice had to introduce test infrastructure so that test cases can even be written in the first place.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by wiml on Saturday July 01, 2023 @05:18PM (#36555342)
Test cases? I still feel lucky to discover that a new (to me) project is even using source code control, let alone has some kind of test suite, let alone one that it currently passes.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by SonOfLilit on Tuesday July 04, 2023 @02:13PM (#36590524)
Reading through a codebase without a specific purpose is a very slow way to get up to speed.

The best advice I've heard is "start from the data structures, they are at the heart of everything".

I like inventing purposes while reading through code if I don't have a real one. I call it "scavenger hunting" and often use it as a programming exercise when teaching. For example here is a scavenger hunt for CPython and Postgre - which lines of code would you need to touch to achieve these purposes?

https://github.com/python/cpython In json module: add parameter to load() and loads() that when True only allows spaces as whitespace characters in the json (and not tabs or newlines)

In re module, python regex has syntax for a digit (\d) and for an alphanumeric or underscore character (\w). Add \l that means "any letter".

In re module, python regex has syntax for hex escapes (e.g. \x0a), octal escapes (e.g. 0o012), unicode escapes (e.g. \u000a). Add binary escapes (e.g. \q00001010)

In python C implementation: Replace the hash function used when inserting a string key to a dictionary

In python C implementation: Add an average() builtin function (like e.g. max(), sum())

https://github.com/postgres/postgres Better string hashing algorithm for query plans that involve hashing a column

"Better column combination hashing algorithm for query plans that involve hashing a column

Some queries will want a hash on (a, b) which involves calculating hash(a), hash(b), and then combining them into combination_hash(hash(a), hash(b))"

"Add a new kind of step to execution plans

e.g. a step that logs to a cloud logging service. No need to compile it into queries, just to add the data structure for it and code that runs it when relevant so it could be compiled"

"Add gzip compression as a way to avoid page splits

Today when a page is about to be split, bottom up deletion and deduplication are attempted to keep the page from splitting. We want to add GZIP compression as a third way to try and avoid expensive page splits."

"Add a complex number column type

The column should hold a float for the real part and a float for the imaginary part"

Add Configuration Flag to Never Use Covered Index Optimization

"Add new type of index

e.g. index that runs Principal Component Analysis to index high dimensional data, but don't care about the details, just the integration points"

Re:Leveling Up in Job Interviews for Software Engineers (2022) by not_alexb on Saturday July 01, 2023 @01:10PM (#36552275)
Expensive because, under deadlines, it's a bit of a nightmare to have to twist your mind into all these shapes (and shatter a few times because your first couple passes of understanding are going to go so right until they go so wrong) until whatever you're reverse engineering finally clicks. It's even better when you feel you're just at the cusp of delivering a new feature on top of what you reverse engineered, and you realize you're missing a skill and have to level up your knowledge to inside of a couple days (oh, and dont forget the times when you think you've learned just enough of that skill to deliver and realize you need to explore an entire subfield of that skill to truly deliver).

I've delivered every single time, but I can't do this shit more than a few times a year; I don't say this lightly: it's fucking unhealthy..

Re:Leveling Up in Job Interviews for Software Engineers (2022) by SonOfLilit on Tuesday July 04, 2023 @02:08PM (#36590456)
Yes.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by ch4s3 on Saturday July 01, 2023 @11:44AM (#36551304)
This definitely rings true to me. We give an interview that’s basically a simple parser, and ask candidates to do it recursively(in Elixir) using function head instead of Enumerable. We link to the relevant docs and it’s a paired exercise with tests built in. It’s generally been a good predictor of candidates ability to work in our code base and collaborate. The whole thing can be done in 50loc and is not meant to be terribly hard.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by angarg12 on Saturday July 01, 2023 @11:54AM (#36551436)
I've conducted hundreds of interviews and I agree about the tech stack, but disagree about culture.

Tech is usually easy to pick up, and highly company specific. Any good engineer should be able to learn new tech, and things will change over time.

Culture is much harder to "teach". For me testing for culture fit has become much more important than tech acumen, particularly at more senior levels. You need to have a sense of at least whether the candidate aligns with the company culture, and is willing to fit.

Not doing this risks several scenarios:

a) The candidate takes a while, but finally fits with the culture. This is suboptimal but ultimately a good outcome.

b) Candidate refuses to fit with the culture. This will likely cause performance issues, and the employee will ultimately leave or get fired. Not a good outcome.

c) Candidate actively subverts the company culture. This is the most destructive outcome and can be quite damaging, particularly at higher levels.

Checking that someone will be a good fit for the company is better for both the company and the candidate.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by spacemadness on Saturday July 01, 2023 @12:36PM (#36551918)
I recently interviewed a candidate that seemed solid technically but kept calling me bro. I’m pretty laid back but that was a fail. Note to everyone here: don’t do that.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by the_gipsy on Saturday July 01, 2023 @01:17PM (#36552368)
Chillax, bro.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by goostavos on Saturday July 01, 2023 @02:21PM (#36553291)
Bruh.

Counter note: I've done 100s of interviews. A bro, bruh, or brah wouldn't even register as something notable to me. This is just how my younger coworkers talk.

Their use of "bet" has taken some getting used to.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by ecshafer on Saturday July 01, 2023 @03:29PM (#36554087)
I haven't had that happen, but it would be refreshing. I would be really weirded out by a "sir" though. casual environments where people can just work and not worry about wearing a persona are nice.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by spacemadness on Saturday July 01, 2023 @03:58PM (#36554410)
I would also be weirded out by sir. I say dude a lot but I wouldn’t throw that out like a nervous tic in an interview—it’s a little too familiar and doesn’t exactly reflect situational awareness.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by stephendause on Tuesday July 04, 2023 @02:22PM (#36590661)
I think the use of "sir" depends on the person's background culture. If you're from the US, it's probably too formal unless you're in the military or something, but other cultures place a higher value on respect for authority. I've had people not originally from the US call me "sir", and while I make sure they know they don't have to, I also don't worry about it.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by auggierose on Saturday July 01, 2023 @03:39PM (#36554210)
You are probably not as laid back as you think you are, bro.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by spacemadness on Saturday July 01, 2023 @03:46PM (#36554284)
Maybe you’re right, bro. I guess I can live with that, bro.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by throwaway202351 on Saturday July 01, 2023 @04:25PM (#36554759)
I recently interviewed at a place where the interviewers kept calling me bro or dude, so maybe they'll match with each other at some point.

Without wanting to get into a discussion of the gender-neutrality of those words, I'm not a man and everyone that I talked with there was, and it just felt odd.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by Silhouette on Saturday July 01, 2023 @07:49PM (#36556565)
The same sort of problem exists across generations. I've had a few meetings with potential clients for our business who were quite young (sometimes literally but certainly culturally) and it felt like they were speaking a different language. When that language sounds like sound bites they probably heard on TikTok last night and yet somehow conveys no useful information whatsoever it's usually a good sign not to pursue that deal any further! You don't have to be all stuffy and formal but professional presentation and effective communication are valuable skills. I can only imagine what they must sound like when they're interviewing potential employees for their own business.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by gabereiser on Sunday July 02, 2023 @08:00AM (#36560638)
I call everyone dude regardless of gender. #genderequality
Re:Leveling Up in Job Interviews for Software Engineers (2022) by coredog64 on Saturday July 01, 2023 @06:14PM (#36555870)
No cap, fr fr.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by brightlancer on Saturday July 01, 2023 @09:25PM (#36557244)
> Note to everyone here: don’t do that.

Note to everyone here: Not everyone is as uptight as this guy and you shouldn't be either.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by _a_a_a_ on Saturday July 01, 2023 @12:16PM (#36551707)
It depends what company culture actually is. I have worked at companies where documentation has been frowned upon – I'm not exaggerating either. That is something I most definitely will try and subvert.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by Silhouette on Saturday July 01, 2023 @07:41PM (#36556507)
On the other hand if you never hire anyone with different ideas then you'll inevitably create a monoculture that had difficulty seeing its own weaknesses and making improvements.

Sometimes two philosophies aren't necessarily wrong but simply aren't compatible. Choices like emphasising frequent collaboration and constant communication or async-first deep work. Mismatches there are genuine culture misfits and it benefits everyone to realise that early and move on with no hard feelings.

But a lot of ideas in how a team works are not so black and white. It's valuable to hire people who have different ideas and aren't afraid to advocate for them when the time is right as long as they are still team players who will accept a result that isn't their personal preference if that's the team's consensus or management's direction. Not hiring people like that because their personal preferences don't align with the team's current way of doing things is also a culture misfit but in this case it's a dodged bullet for the good candidate.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by brightlancer on Saturday July 01, 2023 @09:52PM (#36557397)
> > Culture is much harder to "teach". For me testing for culture fit has become much more important than tech acumen, particularly at more senior levels. You need to have a sense of at least whether the candidate aligns with the company culture, and is willing to fit.

> On the other hand if you never hire anyone with different ideas then you'll inevitably create a monoculture that had difficulty seeing its own weaknesses and making improvements.

This is a balancing act for which there isn't a hard and fast rule, because organizations need a culture, but not all cultural values are good.

A group might want to bend on someone who is weaker on their Documentation And Testing value, but not bend on someone who is weaker on their Honesty value; but maybe they won't bend on Documentation And Testing because they view it as essential and don't want to risk that the FNG won't internalize it.

"But that isn't the cultures I object to," I've heard critics say. Of course not. But sometimes those are the cultural values that folks are trying to conserve. That's why there's no hard and fast rule.

Sometimes the cultural values are dishonesty or bigotry or cronyism, or simply an aversion to being called "bro". But often they're honesty and open-mindedness and fairness. We should not toss out the baby with the bathwater.

Re:Leveling Up in Job Interviews for Software Engineers (2022) by hardlianotion on Saturday July 01, 2023 @02:37PM (#36553512)
Yeah - my last interview was a bit like that. Uninteresting, lazy factorial question, some syntax bits on Python, can you list some canonical definition of object orientation, no probing at all on any topic of interest, and then a brief trivial squabble on what a list comprehension is.
Re:Leveling Up in Job Interviews for Software Engineers (2022) by twelve40 on Saturday July 01, 2023 @07:12PM (#36556308)
> so the interviewer can rank you vs themselves. You need to be good but not too good you’re a threat

Maybe only about 10% of people who are sadists or calculating assholes actually follow that motivation? Unless you had a very special sample pool. Most interviewers i've met - both good and bad - were just trying to do what they think is right, with varying degrees of competence.