[bartislartfast]

Recently had to hire a new dev, and one of the submissions used chatGPT to generate a solution for our take-home test.

The really clever thing was, they did a line by line breakdown of the solution chatGPT came up with, keeping certain parts and throwing out others, giving reasons why each part deserved to stay or be tossed.

Then they wrote a second solution incorporating parts of the first and their own original code, which was genius. They put it all in a readme file with the solution. It instantly put them at the top of our candidate pile.

Unfortunately, the in person interview didn't go so well so we didn't hire them.

Smart approach though. If they'd just used ChatGPT to come up with some bog standard interview questions and solutions they'd probably have walked right into a job with us.

[yieldcrv]

so at what point does your in person interview become the problem?

what is the line for you when the day to day doesn't involve unassisted time trials, but instead requires code reviews of assisted work and code reviews of colleagues work

[bartislartfast]

code reviews are not the be-all and end-all of a coding job.

in-person interview can give you some insight into what it might be like to work with a person day to day, it has more value than a take-home test in a lot of ways.

[yieldcrv]

does your in-person interview do that?