News for hackers. Stuff that matters.
Re: by codr7 on Monday June 26, 2023 @04:31PM (#36485416)
I don't know, I've walked into these interviews with zero preparation and succeeded.

And I've failed FAANG-ish interviews where no amount of leetcode grinding would have helped me.

In my opinion, it's getting rather silly. They're scaring off and filtering out excellent candidates with these excessive processes. None of them even cared about my Github repository that's full of code I write for fun.

Software developer hiring is definitely ripe for revolution/innovation.

Re: by kerblang on Monday June 26, 2023 @04:40PM (#36485532)
I tend to put it this way: If you are entrepreneurially/leadership- minded and can develop a talent for identifying talent, you can be 10x, even 100x more valuable than any engineer because you become a force multiplier who recognizes real talent and empowers it - and the best part is that everyone else is dragging their knuckles on the ground and obsessed with pretentious gate-keeping. The opportunity level is wide-open.
Re: by majormajor on Monday June 26, 2023 @04:48PM (#36485625)
If you want to make money off of being better at hiring than Google et al you need two things:

1) the product idea for something to build that you can sell profitably

2) the hiring skill

Neither of those are trivial to develop.

I do tend the think the second isn't that hard to develop for specific situations (FAANG interviews are really aimed at hiring people who they could swap around to large different sorts of teams or roles and get along with, and be productive with, a huge swath of the company, though IME in practice that doesn't happen terribly often these days). But if you're doing it for someone else's company, your upside is capped by the upside of the company you're working for. And your reward is too - you're not going to command 10x the pay from a CEO you report to who doesn't themselves understand the difficulty of the hiring you're doing compared to "just copy Google" (or why they wouldn't have good results with the latter).

Re: by borroka on Monday June 26, 2023 @05:02PM (#36485798)
A talent for identifying talent needs to be supported with numbers and effect sizes.

The relative absence of numbers from the conversation is what allows many directors of football/soccer (those who recommend the purchase or sell of players) to boast about their stature as talent scouts.

Indeed, it is not surprising that directors of soccer focus on successes and tend to gloss over the many blunders made. Which makes it difficult, as in many other fields, to distinguish the role of luck and ability in successes and failures. Almost always, in my experience, those with the most money and at least an average "eye" succeed in doing the best that can be done: everything else is a game of chance.

A more sophisticated and technically oriented person would say that the most that can be done is to increase the odds of success, but then we are all left to the whims of fate: the young soccer player who many thought would be a sure bet will turn out to be one among many, and the average player at age 16 will have the growth spurt in the next two years that will make his body more conducive to stellar success (but was the growth spurt predictable?).

What I can say is that there have been several attempts to create a special agency for the identification and management of talent in the technology industry, but none has turned out to be more than a higher-level contracting firm.

Re: by onlyrealcuzzo on Monday June 26, 2023 @04:40PM (#36485536)
> In my opinion, it's getting rather silly.

It's luck of the draw. That's really how it's always been.

If you get bad interviewers, you're in for a bad time.

If you get asked questions you know, you're in for a good time.

It's possible your odds of getting bad interviewers has increased. But I doubt the increase is that substantial.

It's interesting to me how much stock these companies put into hiring, and then let countless terrible interviewers continue to interview.

You'd think they'd recognize high quality interviewers and get them doing more than 1 interview per week, and not let people interview until passing a pretty high bar in the quality of their interview.

Instead, they pretty much let anyone interview (as long as they've been at the company for N months and gone to some training).

Re: by Tyr42 on Monday June 26, 2023 @05:01PM (#36485793)
They also don't give any feedback on your interviews other than an eventual "they were hired" or not. So if you are a mediocre interviewer you will never know.
Re: by michaelt on Monday June 26, 2023 @05:33PM (#36486187)
> You'd think they'd recognize high quality interviewers and get them doing more than 1 interview per week, and not let people interview until passing a pretty high bar in the quality of their interview.

I think you substantially over-estimate the eagerness of software developers to take on unrewarding admin work.

Re: by onlyrealcuzzo on Monday June 26, 2023 @06:19PM (#36486641)
> I think you substantially over-estimate the eagerness of software developers to take on unrewarding admin work.

Why do you assume it can only be un-rewarding?

If hiring is so important, maybe it's worth paying the best people extra to get it done correctly.

If it's not that important, it'd be nice if they'd stop pretending like it is.

Re: by michaelt on Monday June 26, 2023 @07:03PM (#36487019)
> Why do you assume it can only be un-rewarding?

It’s an important day for them, so you owe them your full attention. Can’t be browsing the web or replying to emails.

After a decade of interviewing, there is no excitement in watching the thousandth interviewee make the thousandth attempt to count the set bits in an integer.

Hiring is important, it's just very very very boring.

Re: by lionkor on Monday June 26, 2023 @04:40PM (#36485530)
All jobs I applied for that I interviewed for looked at my GitHub specifically, and my past projects, and that was their main topic of discussion in the interview, apart from usual coding questions and such.

Im not victim blaming by saying you may just be applying to the wrong places, am I

Re: by majormajor on Monday June 26, 2023 @04:43PM (#36485573)
I would love to talk about my github projects with an interviewer - hell, I'd also love to talk more about my past systems than their hypothetical ones - but like the parent post, I've found it pretty rare. Past projects maybe 15% of the time at medium-to-large companies (500+ person), and so far am batting 0.000 for "asked about personal projects", including at FAANG interviews.
Re: by liuliu on Monday June 26, 2023 @04:52PM (#36485687)
The logic is twisted and strange, the justification sums up to this: talking past projects like talking to a PhD student about his research paper, it is all they does and doesn't put them in enough "foreign situation" to see their novel problem-solving abilities.

OTOH, when you are hiring for leaders (directors and above), past experiences and behavior questions are all you talking about.

Re: by majormajor on Monday June 26, 2023 @05:33PM (#36486181)
That makes a certain about of sense but I think you can usually get a feel for project-by-project dissimilarities in someone's background and figure out if they've been doing the "1 year of experience for 10 years" or the "continually tackling new challenges and learning from them" path.
Re: by PheonixPharts on Monday June 26, 2023 @04:50PM (#36485651)
Unfortunately this also means you have to be open to a potential 50% cut in TC as well.

Personally, I find enjoying the 8+ hours I spend at work each day more important than raw TC, so have made the tradeoff (and still have a reasonably high TC) which works for me.

That said, I would love a more laid back research programming job in academia, but that requires an additional 50% cut from where I am now.

It's still understandably frustrating that knowing how to write software seems largely irrelevant to getting a job at a FAANG.

Re: by mihaitodor on Monday June 26, 2023 @04:41PM (#36485552)
I have a public disclaimer in my LinkedIn profile intro saying that I refuse to do any algorithmic live coding. They’re top employers and whatnot, but one doesn’t need to torture themselves with Leetcode to get a good job in this industry
Re: by dpe82 on Monday June 26, 2023 @04:43PM (#36485566)
Interesting; how has that worked for you?
Re: by mihaitodor on Monday June 26, 2023 @04:54PM (#36485711)
It felt quite empowering, actually. I ended up having to point it out to some recruiters who kept pestering me even though I already knew what their employer’s interview process is like. It also helped me avoid wasting time to hop on the first intro call with HR to get details about the next steps. Also, I got a few people reaching out specifically because they resonated with it, which was great!
Re: by dekhn on Monday June 26, 2023 @04:52PM (#36485683)
Interesting. So if I asked you to open up coderpad.io and write a python function to reverse a string, you'd just absolutely refuse? What would you do otherwise to show me that you're a programmer?
Re: by mihaitodor on Monday June 26, 2023 @05:01PM (#36485791)
I’d refuse, but If the conversation goes in that direction, then I’d probably end the conversation right there, since it’s pretty clear that’s not the kind of role I want to interview for. I managed to accumulate a bit of online presence over the years and I expect my future employer to a) look me up prior to the interview and b) have a direct interest in my Open Source work.
Re: by dekhn on Monday June 26, 2023 @05:05PM (#36485841)
Sure, I'd look you up and scan your github pages. I've dealt with people who set up fake githubs (copying from various places on the web to make it look like they did real work). Can't help you if you only want to interview people who are interested in your open source work... that sounds very limiting.
Re: by blitzar on Monday June 26, 2023 @05:11PM (#36485920)
I've dealt with people whos whole CV was fake. One of the points of the interview is to sniff this out.

Diving into a github and then asking questions about it, in the same way as you would ask about stuff on a CV seems like a massive win for the skilled interviewer.

Re: by allarm on Monday June 26, 2023 @05:34PM (#36486195)
Normally when I’m interviewing people I don’t go much further than asking about the topics they covered in their resume. If they lied in the resume, it’s an instant no-go. And if their resume is on your desk already, that means that their skill set covers most of the requirements for this position already. Simple enough.
Re: by dekhn on Monday June 26, 2023 @05:50PM (#36486353)
Well, hold on. I see a resume that says "Worked on a complex ML problem, training a model that did blah-and-blah". Sounds great, right? Then when you poke further you find out the person just took an online class that involved git cloning a repo and running scikit-learn on some toy examples without even understanding any of it.

Resume inflation is a big thing.

Re: by allarm on Tuesday June 27, 2023 @03:03AM (#36489754)
I think you misunderstood, I didn’t mean that the resume alone is enough to pass the interview.
Re: by blitzar on Tuesday June 27, 2023 @03:21AM (#36489863)
Normally when I’m interviewing people I do go much further than asking about the topics they covered in their resume.
Re: by allarm on Wednesday June 28, 2023 @07:46AM (#36505071)
So?
Re: by blitzar on Tuesday June 27, 2023 @05:12AM (#36490617)
This might be too cynical ... but those that engage in resume inflation and all the other games get the interviews and get the jobs and become the interviewer. Thus git cloning a repo and running scikit-learn on some toy examples without even understanding any of it == Worked on a complex ML problem.

As for the CV that says took an online class that involved git cloning a repo and running scikit-learn on some toy examples is a CV you should discard as they probably just went for a cup of coffee and looked at the clouds for an hour.

Re: by allarm on Monday June 26, 2023 @05:29PM (#36486118)
In my experience it’s super easy to see that the resume or github or a home project is fake. If not immediately then in like first 10 minutes of the interview. I don’t think that “people lie” is a valid reason to generalize. If anything, that’s the interviewers who are limiting themselves, not the other way around.
Re: by mihaitodor on Monday June 26, 2023 @05:50PM (#36486356)
This guilty-until-proven-innocent attitude will drive people like myself away instantly and that's fine. So far, I had plenty of options to pick from and, for me at least, culture match is highly important.
Re: by dekhn on Monday June 26, 2023 @06:53PM (#36486942)
Oh, I understand. However, the problem is that many companies are inundated with low-quality, puffed up resumes, and it's truly hard to find people that are actually qualified, especially if they're not doing any work to make themselves available.

I would add that I don't think you should think of it as "guilty-until-proven-innocent"; it's just the reality that you are competing with large numbers of amoral people who will lie to get a job. This is much less about culture match than you think.

Re: by michaelt on Monday June 26, 2023 @05:44PM (#36486284)
> What would you do otherwise to show me that you're a programmer?

Pretty much every other job in every other industry seems to do OK with education, experience and references.

If I want to hire a guy to tile my bathroom I don't need him to slap some tiles onto a whiteboard to get the job - some photos of the last few jobs he's done would be just fine.

Is the programming profession really so full of inept frauds? Is our industry so unable to regulate university education that qualifications are so worthless?

Re: by dekhn on Monday June 26, 2023 @05:49PM (#36486334)
Is the bathroom tiling really a fair comparison?

The main reason I hire the way I do is I learned that there are people who have resumes that look like mine (with 30+ years of coding) but they don't actually know how to do any coding, even just "please write out a simple class in python that does nothing". I go out of my way to give every candidate a fair shake and I'm not looking for some fast, set-in-stone rules. Nor am I looking for you to solve any really hard problems. Still it's been depressing just how many coders I interview who can't even explain how a hash table works.

Re: by codr7 on Monday June 26, 2023 @11:07PM (#36488429)
Try again?
Re: by stcroixx on Monday June 26, 2023 @08:53PM (#36487782)
I would definitely leave. Maybe for an intern that would be acceptable, otherwise red flag.
Re: by dekhn on Monday June 26, 2023 @09:09PM (#36487859)
How can you expect to interview for a job without doing a basic coding interview?
Re: by dpe82 on Tuesday June 27, 2023 @01:17PM (#36495919)
Maybe by presenting your education and past experiences by discussing the design and interpersonal challenges you worked through?

IMO quizzing someone on whether they can solve an artificially tricky algorithm problem on the spot does not correlate very strongly the actual day-to-day work we do as software engineers. At best it's a measure of... whether someone can solve a tricky algorithm problem on the spot. It looks like engineering but it's not really what we do.

Re: by dekhn on Tuesday June 27, 2023 @01:26PM (#36496039)
If you read my comments you'll see I'm not advocating tricky algorithm problems.

We're talking fizzbuzz-level verification, I'd say about 50% of applicants that I interview can't do fizzbuzz.

Do you want me to make it easier? how about reverse a string?

Re: by dpe82 on Tuesday June 27, 2023 @04:21PM (#36498133)
Ah yeah, agreed, a bare minimum "yeah ok you can code" is perfectly reasonable.
Re: by xyzelement on Monday June 26, 2023 @04:53PM (#36485697)
There was a great story on HN a few days about the concept of "It wasn't for me"[1] - the distinction between something being "bad" vs "just not for me." Your comment made me think of that.

If you really perceive algorithmic live coding as torture, then it makes all the sense in the world to avoid it. "It's not for you."

But it's important to recognize two things: first that this is subjective. A different person may enjoy something you hate (I don't mind live coding for example) or at least won't consider is bad enough to be called "torture." So just because it's not "for you" doesn't mean it's bad.

The second thing is to recognize that there's a cost to being however we are. In this case, the cost of avoiding opportunities that require such interviews is that you may have fewer opportunities and they may be less lucrative on average. It's possible that (a) you are still able to find good-enough opportunities and (b) the downside is worth avoiding the torture. But you can also decide that this cost isn't worth it, and you have some room to shape what is and isn't for you, over time. For example, if the thing that makes this "torture" for you something like anxiety when being watched? If so, probably something like that shows up in other places in your life and maybe valuable to tackle anyway.

By no means am I suggesting that you need to do something different than what you're doing, just pointing out that these reactions are subjective, can have downsides, and are under our control to some extent.

[1] https://news.ycombinator.com/item?id=36452067

Re: by mihaitodor on Monday June 26, 2023 @06:26PM (#36486709)
> the distinction between something being "bad" vs "just not for me." Your comment made me think of that.

> If you really perceive algorithmic live coding as torture, then it makes all the sense in the world to avoid it. "It's not for you."

I wasn't aware of this concept, but I can assure you that I don't have such a mindset. I tend to enjoy finding difficult challenges and complex topics to dig into which are way outside of my comfort zone. Leetcode practice is different, though, and yes, it does feel like torture to me and some other developers who tend to be rather quiet in general. While it's really tempting, I don't think I'm the right person to act as a community voice on this topic, although I do chime in sometimes.

When you're just starting this career path, it feels like homework. Heck, it's even exciting to solve problems which are a bit more complicated than whatever you're exposed to in school. However, try to spend several years in a row (8 in my case) trying and failing to pass such interviews (several in-person ones each year) and it will feel like torture. "If you'll spend a little bit more time on Leetcode, surely you'll pass next time..." No thanks! I'm done. The issue is not the lack of training, but the way in which these interviews are conducted by certain people which causes me distress and severe anxiety. I moaned about this before in various HN threads related to interviews and I might bother to blog about it some day.

> In this case, the cost of avoiding opportunities that require such interviews is that you may have fewer opportunities and they may be less lucrative on average.

Hasn't been my experience, but I'm not looking to maximise my income. I looked for advice on negotiation strategies and whatnot and felt happy with the offers I got. Others might have a different experience in this regard, but I think asking for less money in exchange for a psychologically-safe interview process is nonsense. At the end of the day, you get what you pay for and there are review sites anyway.

> For example, if the thing that makes this "torture" for you something like anxiety when being watched? If so, probably something like that shows up in other places in your life and maybe valuable to tackle anyway.

I think you're making certain assumptions here. I don't need to "tackle" my perception of what's safe and comfortable. We're all different and that's a good thing.

Re: by liuliu on Monday June 26, 2023 @04:39PM (#36485525)
When you are hiring in volume, you are hiring for additive value, not for transformative value (nor multiplicative value). For additive value, conformance is essential.

Most of the semi-successful companies don't need to be "the innovation machine".

Re: by snakewatching on Monday June 26, 2023 @04:44PM (#36485579)
I will agree with this. Leetcode style interviews identify the "rule-followers", "not-going to rock the boat" type of engineers. That's what FAANGs need, not innovators and leaders.
Re: by CamperBob2 on Monday June 26, 2023 @04:40PM (#36485531)
What kills me is that the developers they are hiring based on their encyclopedic knowledge of language minutiae and mad leetcode skillz are exactly the ones who will be first in line for replacement with ML-based solutions.

The fitness function used by these companies is so broken it's not even funny. The ability to get things done and ship product doesn't even seem to be on their radar. They are optimizing for dead weight, which is how they end up with these periodic 1000+-person layoffs.

Re: by kulikalov on Monday June 26, 2023 @04:46PM (#36485600)
Not a recruiter, but I imagine there are at least 3 reasons for your repo to be ignored or deprioritized in favor of typical interview: - not everyone contributes to OSS - it’s easy to fake - it’s hard to assess within a short period of time

This it seems to be hard to standardize and streamline candidates validation based on their oss repos.

Also, afaik the goal of interview is to assess candidates thinking patterns, it’s hard to do quickly based on an arbitrary piece of code.

Re: by codr7 on Monday June 26, 2023 @04:48PM (#36485628)
Sure, it would take some more effort to dig into than checking boxes.

But it would also provide more valuable feedback.

Re: by tdudzik on Monday June 26, 2023 @04:51PM (#36485667)
How would you compare candidates that have some code in GitHub and those that don't ?
Re: by cinntaile on Monday June 26, 2023 @04:54PM (#36485720)
You can assess the ones that don't have code on GitHub in a different way, but there is no reason to ignore a possibly valuable datapoint.
Re: by tdudzik on Monday June 26, 2023 @05:44PM (#36486285)
But faang companies try to objectively compare all candidates. Also they have so many resumes that it doesn't seem feasible to review code on GitHub.
Re: by codr7 on Monday June 26, 2023 @06:27PM (#36486720)
5 hours x 1/2 people checking boxes is energy that could be put to better use.
Re: by TheBigSalad on Monday June 26, 2023 @04:48PM (#36485618)
"They're scaring off and filtering out excellent candidates with these excessive processes." I don't see myself ever applying to any of these whacky interview companies. I like money and all, but idk. It's such a turn off. Maybe if I truly felt they were actually measuring company value.
Re: by ar_lan on Monday June 26, 2023 @04:56PM (#36485741)
Where do you find other valuable companies to interview at? Genuine question, I've been entrenched in the Silicon Valley bubble for well over a decade that I don't even know how/where to find meaningful (remote) companies.
Re: by TheBigSalad on Tuesday June 27, 2023 @05:24PM (#36498869)
Mostly friends or targeting well known companies. I've used recruiters, all sorts of things. I can't speak to the current climate as I haven't looked in years.
Re: by ulfw on Monday June 26, 2023 @04:48PM (#36485634)
The Product Manager interviews are even worse. Google was the shittiest experience I had, all the way to the silly hiring Committee. Three months of my life I'll never get back.
Re: by passwordoops on Monday June 26, 2023 @04:54PM (#36485713)
Ooh do provide more detail! In general I've found PM interviews at hardware companies much more useful (?) than software.
Re: by em500 on Monday June 26, 2023 @04:50PM (#36485659)
FAANGs can get literally over a million job applications per year. Any procedure that filters that down to roughly the number of people that they plan to hire (a few 10k) is also going to filter out some excellent candidates, no way around it.
Re: by codr7 on Monday June 26, 2023 @04:56PM (#36485748)
But it's still a very time consuming and expensive process. Typically 5h of interviews with 1/2 people from my experience. Spending that energy more wisely would result in more valuable feedback and better hires. But it takes actual effort to try and understand rather than simply checking boxes.
Re: by RandallBrown on Monday June 26, 2023 @04:59PM (#36485780)
And yet, they still cold email me every 6 months or so.
Re: by ar_lan on Monday June 26, 2023 @04:54PM (#36485714)
GitHub is not the best metric, though.

1. Many (most) engineers are not in positions to be able to meaningfully contribute to OSS (e.g. all the code I write for work is proprietary).

2. It can easily be faked.

3. Personal projects can sometimes be interesting, but often don't showcase usefulness (unless front-end).

4. Many high quality engineers don't like to spend their free time doing more of their job.

Some repos, of course, are more impactful though. And I would probably say that if you are someone who loves to write code 16 hours a day, more power to you, you deserve to be hired! But many quality engineers would get missed if that is the desired bar (which is fine - other companies will just scoop them up).

(edit: OSS engineers extra upset by what I'm saying, but there is a lot more to this world than just what shows up in your GitHub feed)

Re: by codr7 on Monday June 26, 2023 @05:04PM (#36485831)
The fact that a candidate loves problem solving / coding so much that they'd do it for fun is a pretty strong signal.

Like I said, it would take more effort from the interviewers to dig into.

But it would also provide more valuable feedback and result in better hires.

Re: by superfrank on Monday June 26, 2023 @04:55PM (#36485729)
I agree that there's a lot that the current hiring process get wrong. I'm not really defending it, but want to clarify a few things.

> They're scaring off and filtering out excellent candidates with these excessive processes.

In my experience this is by design. The cost of a false positive (hiring someone they shouldn't) is far more expensive than a false negative (passing on a good candidate). Since FAANGs usually have a healthy pipeline of candidates and many who fail will eventually reapply they're okay with passing on possibly qualified candidates.

> None of them even cared about my Github repository that's full of code I write for fun.

As an EM at a mid to large tech company who has hired plenty of engineers I think ignoring people's Github is the right call and I don't even bother looking at candidate's Github unless it's for something like an intern role. Ignoring the fact that I don't know where the code on Github came from (did someone else write it? Is this just following a tutorial?), the code you write and the skills you use when you're writing code at home alone on a passion project is VERY different than the skills you need to be successful in a large, slow moving, bureaucratic corporation.

Re: by blitzar on Monday June 26, 2023 @05:00PM (#36485789)
> The cost of a false positive (hiring someone they shouldn't) is far more expensive than a false negative (passing on a good candidate)

The cost of a false positive is 0 - they always hire the non optimum candidate there is a massive margin of error.

We all like to pretend that without our unique special skills the entire company would dissapear overnight, but it is a fantasy.

Re: by nomel on Monday June 26, 2023 @05:10PM (#36485903)
> None of them even cared about my Github repository that's full of code I write for fun.

Context: I've interviewed around 200 people for our current org, and have "settled" on an interview that's used for a certain position. I don't think I'm necessarily good at interviews, and I'm not sure I'm "doing it right". I give the number to show that my sample size is reasonable. We're solving practical problems, with code. Our interview sessions are 45 minutes for each person (which is the fundamental limitation).

I don't look at GitHub projects, or really ask about previous work.

I used to, but I very quickly found that the vast majority of people lie on their resumes. Generally, the more senior, the more lies. Most people put bullet points of "achieved x" which end up really being "kinda helped those people who were achieving x". For GitHub, in most cases, it was obvious the person was not the author of the Github repo they gave me. They could answer questions about the code, but couldn't go into any depth about it.

I found that going over previous work, or Github repos, ended up taking a huge chunk of the 45 minutes, that put each person on a different standard, somewhat of their own crafting, leaving no time to find out if they were actually able to write a for loop or not, which I've had Phd candidates, with "15 years of experience", fail to do. For feedback of the candidate, I need a tangible justification, and clear demonstration of why I say yes/maybe/no. There are no "gut feelings" allowed from the panel; you need reasons.

So, I give the candidate a simple, practical, work relevant, problem to solve during the interview. No compilation, no running code, no worries about perfect syntax, and no esoteric knowledge/libraries required. They're free to use whatever language they want. It's an interview where they have to demonstrate their thought process, how they question/navigate the requirements, and ability to see consequences (which I think is 90% of programming).

Maybe a few percent have finished within 10 minutes. For these people, we had fun talking about their other work, and they showed great knowledge, as expected. But, as desired, that wasn't required to do first. The interview itself proved that they would already.

I would love feedback about this approach, even though it seems to be working well for our orgs needs. Ideally, I would take the Jim Keller approach, and have a nerd out session, but, I have a feeling people are more properly filtered before they would get to him.

Re: by OkayPhysicist on Monday June 26, 2023 @05:29PM (#36486114)
Personally I wouldn't terribly mind such an interview, but I do know plenty of people who absolutely fall to pieces when having to code while being watched, and it's definitely not particularly pleasant to me, either. I think the best interview I've experienced was one where the "2 hour interview" consisted of me receiving an email with a short, job-related task and then after an hour was up we spoke and discussed my solution. Respected my time, as it wasn't some open-ended take-home test that somebody with too much time on their hands could spend dozens of hours polishing to perfection, while still not being quite so "whiteboard-y".

With regards to Github projects and the like, I do ask about them in interviews, because I think there's a place for them as an early screening. Every engineer worth their salt has some war stories, and that's a good angle to approach their GitHub profile: if they have an interesting sounding project, asking them to talk about any interesting problems they ran into during its creation tends to make it immediately clear whether they're full of shit or not. It's not a great positive signal, but if they're not chomping at the bit to talk about engineering challenges, it's a strong negative signal.

Re: by nomel on Monday June 26, 2023 @06:20PM (#36486654)
> absolutely fall to pieces when having to code while being watched

Yeah, this is the biggest problem I have with it. I try to be conscious of this, and try to keep things pretty lighthearted. If I notice someone getting nervous, a "you're doing great for time" usually calms them. If not, I do follow up interview, if they did well seeking an understanding the problem, and could explain it verbally. I've had a few people pass with flying colors after a second round.

> and that's a good angle to approach their GitHub profile

I disagree here, with the (probably wrong) assumption that not having a GitHub profile adds a negative bias. Some people put their coding hours into work, with different lives outside of coding. All of the colleagues I've known with impressive GitHub profiles burnt out/left. Battle stories can be within corporate repos.

Re: by codr7 on Monday June 26, 2023 @05:18PM (#36485996)
Wouldn't that be an excellent filter?

If the candidate is lying, just move on to the next.

Re: by nomel on Monday June 26, 2023 @06:34PM (#36486783)
Maybe my org is different, but I need to have confidence and justify/document my yes/maybe/no. It's very hard to prove that someone is lying, especially since you can't expect them to remember everything from some years ago. You could claim they should have tried to remember the details of their projects, but that's tricky since most people can't take code or notes with them. If I show that they have a Phd, with experience building whatever, but can't write a for loop, then I have my proof.

Terms like "good thought process", etc aren't allowed in our feedback, unless specific examples are given. Terms like "team fit" will get your feedback outright rejected. No mushiness allowed.

Re: by codr7 on Monday June 26, 2023 @09:18PM (#36487904)
Sounds interesting, feel free to get in touch.
Re: by bhasi on Monday June 26, 2023 @08:15PM (#36487548)
> no compilation, no running code

I recently had an interview where, for the first time, the coding round was Coderpad based, which allowed me to run my code and build my solution bit by bit with instantaneous feedback.

I know for sure that I wouldn't have been able to solve that recursion problem without that live terminal. I now am going to insist on this live terminal in all of my future interviews and refuse to do any that don't employ one.

I think it helps my anxiety immensely.

Re: by nomel on Tuesday June 27, 2023 @01:29PM (#36496072)
I think this is fair. But, with how simple the problem is that I give, it's a real issue if they can't read/understand the code they've written. It's simple enough that anyone should be able to mentally run the program.

Regardless, I'm going to offer that as an option and see how things go. Maybe everyone will be in a better mindset, allowing me to add a bit more complexity/depth to the problem.

Re: by nomel on Tuesday June 27, 2023 @12:45PM (#36495390)
I realized I've left out some detail. I'm on a panel, and I'm not one of the hiring managers. Others might be looking at resumes and repos, ideally before they make it to us. The above was to show why I, personally, don't consider them.
Re: by dennis_jeeves1 on Monday June 26, 2023 @08:11PM (#36487522)
>Software developer hiring is definitely ripe for revolution/innovation.

That's like saying that janitor jobs ripe are for revolution/innovation. You would think I'm joking, but most companies really do not care, despite what they say.