Tomorrow will be the first time I'll be interviewing candidates for hiring. Any advice?
P.S.: This will be first time an interviewer will be more nervous than the candidates. 🤔🤔

Ask them theoretical questions. If they can answer, they are nerds who shouldnt be hired.

@BindView what do you think is the best way to check a candidates pragmatic thinking?

Let them tell you what they did in the field. For example which tech they use? Why they chose it, and what problem they were trying to solve.

If they answer all three they are thinkers and not monkey see monkey do IMO

Ask them questions about the biggest difficulties they had in the past, and how they managed them.
If the candidate is prepared for this question, you're just gonna get bullshit. If not, then it's probably the most valuable information you can get.

Don't throw many exams and theoretical questions or problems, as most of the people come in shitting their pants anyway. Leave the technical exam for after the interview.

If the job is really demanding of good cognitive abilities, you can ask a question or two, like to quickly determine whether 899 is a prime number, or to determine if 2 words from a list are linked by doing N operations of changing 1 character to get to another word in that list, or some of the first problems on projecteuler.net. But those are advanced, which you can be sure that 99% of developers won't be able to answer at an interview. Use them only if you want a freakin' genius and nothing else.

Start by peeing on them to assert dominance.

Should help with your confidence...

@Froot and my soul died there... 😅😅

The interview in my company was with a developer and a HR. I had to explain technical concepts to the HR person, which I found was a good way to test my knowledge and my communication skills.

Depending on the position, ask them to write pseudo code. That'll focus on their structure and thought process, rather than syntax n stuff, which we all Google anyway 🤠

@donutsocks if they ask for code during an interview, i usually get up and leave

@BindView I've never actually experienced it (thank god), but from what I hear from my dev friends, it's quite common?

@donutsocks 1/8 so far, but maybe i was lucky

Asking for code is common in my company but that is not the main decider for a candidate.

Talk. Conversations are the best way to interview. And conversations aren't scary when the other person is doing everything they can to make a good impression 😊

Determine if they will fit in with the rest of the devs (personality, talkativeness, temperament, humor, hygiene, etc.). See how techy and competent and friendly they sound.

Some people are best at faking the above, so obviously look at code, too. Code reviews aren't scary, either: it's just code.

Interviews are fun!

@dazen yeah exactly, thats a good question because i have no fucking idea, now hire me

Interviews are over. I ended up going through their CV point by point. Finished with some basic algo questions. All in all it was a good experience. 😎😎