janephilipps

6 ms·

1.
by janephilipps 9y ago
I agree with your point. I'll add that for new developers and those without the traditional CS background (both of whom are my target audience for this guide) spending the extra time is a learning experience for them that can make them
2.
by janephilipps 9y ago
These are good data points. I think the amount of time you should spend often depends on where you are in your career. I know many companies don't explicitly require tests, but for them if a candidate submits a take-home challenge with
3.
by janephilipps 9y ago
Good point about consistency, which is hard to achieve with the open-ended take-home challenges. I still feel like there is a catch 22 for new developers though - if you're competing with more experienced candidates, your best solution
4.
by janephilipps 9y ago
Love the idea of investing in the local community. Training and mentorship is so important, and so many companies sacrifice it for other things.
5.
by janephilipps 9y ago
Wow, so sorry to hear this! This seems to test nothing other than what your interpretation of "clever" is. I've definitely learned that it never hurts to ask questions in these situations.
6.
by janephilipps 9y ago
This is really cool, thanks for sharing! I don't necessarily disagree with your point, though I do think an unrealistic time limit is even worse than no time limit. I also emphasize the importance of not taking on a challenge that is o
7.
by janephilipps 9y ago
This seems like a good happy medium type of take-home challenge. Out of curiosity, how many applicants have you had?
8.
by janephilipps 9y ago
Part of what I like about take-home challenges is that you can do them on your own time without anyone watching over your shoulder. Because in-person technical interviews tend to last for such a long time, they can be incredibly draining. T
9.
by janephilipps 9y ago
For a well established developer, this may be true, but for newer developers, they often have to jump through a lot of hoops to prove their skills first, especially if they come from a non-traditional background and do not have a CS degree.
10.
by janephilipps 9y ago
As an experienced programmer, what does your ideal interview process look like? Do you think your opinion holds true for junior developers as well?
11.
by janephilipps 9y ago
This is a really cool idea - because working with code written by other people is usually a large part of any job, this type of assignment could also test for that. For newer devs, I've seen anything from simple Tic Tac Toe to being gi
12.
by janephilipps 9y ago
Sure - as someone who transitioned into development from another industry, I could only rely on my past experience for transferrable skills, and not my actual technical skills. While Github is great, my Github is not always an accurate refl
13.
by janephilipps 9y ago
I agree that time suggestions are usually way off, which can be a positive and a negative. On one hand, you can spend a ton of time to go above and beyond, while on the other hand, you may have other priorities. I think if you're reall
14.
by janephilipps 9y ago
Examples like this are why I think take-home challenges are a better way to assess a candidate's coding skills vs. their problem solving skills/how they think.
15.
by janephilipps 9y ago
This is tough - I've had similar experiences. I think the main issue here is that the company didn't give you any feedback, so it's hard to know what happened. I've submitted a take-home challenge, but had hiring needs c
16.
by janephilipps 9y ago
Thanks! I definitely understand that many people are opposed to take-home challenges because they can be very time consuming. For me, I use them as a learning opportunity, so even though they are not necessarily going to be used or maintain
17.
Guide to Take-home Coding Challenges(fullstackinterviewing.com)
99 points by janephilipps 9y ago|147 comments