Joe Petrich 🟪 pfp
Joe Petrich 🟪
@jpetrich
gm fellow casters. For the engineers out there, if given the choice between a take-home exercise and a live coding interview, which would you choose?
21 replies
0 recast
0 reaction
fant pfp
fant
@fant
Is neither an option? Showing existing project is lower barrier for candidates, but I've found it very hit and miss when hiring since people come with all kinds of random projects. Difficult to compare candidates objectively
1 reply
0 recast
1 reaction
what pfp
what
@what
not an engineer, (tech recruiter) but candidates respond really really well to take-home exercises. they feel it's the most fair assessment, as well as the most enjoyable. it gives candidates the sense that you're interviewing w/ confidence and know what you're looking for.
1 reply
0 recast
0 reaction
mulf pfp
mulf
@mulf
Third option, review a fully baked product / project your interviewee has shipped in the past?
1 reply
0 recast
0 reaction
Breck Yunits pfp
Breck Yunits
@breck
wouldnt apply. we don't do interviews. everyone is hired. just email me your rate, i'll agree, then you can start working on issues https://github.com/breck7/pldb/issues
1 reply
0 recast
0 reaction
Nar pfp
Nar
@nar
Live for sure. Get the process done with quickly and on a more level field (eg take home favors someone with more time)
1 reply
0 recast
0 reaction
Ashley Chang pfp
Ashley Chang
@ashley
Take home 100%. It depends on your personal strengths but I think the take home is much more reflective of what work will be like + you get time to think through things thoroughly. Live takes less time but its more of a performance and favors a completely diff skillset imo
1 reply
0 recast
0 reaction
steph 🧾 pfp
steph 🧾
@steph
Take home for sure. ✨ IRL prob takes less of the applicant's time, but damn can they be stressful - + I have yet to experience a whiteboarding interview reflective of the work (almost all involved recursively implementing some algorithm in front of ppl - diff skillset imo).
1 reply
0 recast
0 reaction
borodutch @ lunchbreak.com pfp
borodutch @ lunchbreak.com
@farcasteradmin.eth
live coding any time of the day, both as interviewer and interviewee
1 reply
0 recast
0 reaction
Alex Poon pfp
Alex Poon
@alexpoon.eth
When was the last time you have to code under pressure? With time constraints and someone judging you the whole time?
1 reply
0 recast
0 reaction
Brent Fitzgerald pfp
Brent Fitzgerald
@bf
Live pairing. Lets me evaluate the interviewers, plus probably takes less time.
0 reply
0 recast
0 reaction
Carlos Matallín pfp
Carlos Matallín
@matallo.eth
Take home hands down
0 reply
0 recast
0 reaction
Varun Srinivasan pfp
Varun Srinivasan
@v
Take home for sure
0 reply
0 recast
0 reaction
rene pfp
rene
@reen
take home exercise + live coding interview on that take home task where you describe your logic and solution
0 reply
0 recast
0 reaction
svj pfp
svj
@svj
this may be iOS eng specific - but an amalgamation of the best interviews i’ve experienced: - take home (3 hr task max, must complete) - meeting w/ screen share to discuss your code - 1/2 features done live (not known beforehand, but working together as if on team)
0 reply
0 recast
0 reaction
Maybe Im Wasabi〽️ pfp
Maybe Im Wasabi〽️
@maybeimwasabi
Take home. Consider the introvert, sensitive type. There is also ample proof in psych research that humans across the board perform worse when “watched” in various scenarios. Certain personalities will perform significantly worse.
0 reply
0 recast
0 reaction
Kevin pfp
Kevin
@typedarray.eth
prefer live coding as long as it's not a google/leetcode-style problem
0 reply
0 recast
0 reaction
Will Papper pfp
Will Papper
@will
We did a paid take-home at Syndicate for a while with a live walkthrough. Worked well for entry level, but was hard to create challenges appropriate for senior people. Switched to live coding for senior candidates with an emphasis on architecture.
0 reply
0 recast
0 reaction
si pfp
si
@si
Take home
0 reply
0 recast
1 reaction
gumdalf pfp
gumdalf
@0xarun
Not a developer or an engineer in a pure sense.. but the interview process should be as close to the real work scenario as possible.
0 reply
0 recast
0 reaction