On Interviewing as a Junior Dev
lizmrush.com
On Interviewing as a Junior Dev
1–10 of 95 posts
Re: On Interviewing as a Junior Dev
#2> I did a code challenge that involved ranking soccer teams, and while going over the code a developer at the company asked me if I needed the rules of the game explained to me. While it's a good thing to make sure the candidate understands what the problem is, companies need to be aware that these things carry extra cultural baggage and asking a female candidate if they understand a basic sports rule (or any other male dominated theme) comes across as belittling and sexist.
As a male, I don't even know the rules of soccer, so I would have gladly wanted to hear the rules of the game so I could implement the solution correctly.
Re: On Interviewing as a Junior Dev
#3On rescheduling, the candidate should also be considerate of the interviewer. Too many times, candidates have scheduled a interview for early morning (because they don't want to take time off from their current job) then while I'm driving to work early, call 20 minutes before to say they are "sick" and cancel. If you feel you are getting sick, try to cancel much earlier so as not to inconvenience others.
Re: On Interviewing as a Junior Dev
#4> I did a code challenge that involved ranking soccer teams, and while going over the code a developer at the company asked me if I needed the rules of the game explained to me. While it's a good thing to make sure the candidate understands what the problem is, companies need to be aware that these things carry extra cultural baggage and asking a female candidate if they understand a basic sports rule (or any other m…
I think too that there's nothing sexist about being explained the rules of soccer. Also I get the feeling that the OP is a little too over her head. At some point I thought it was Ken Thompson writing the blog post.
Anyway, I'm glad that turned out good for her, also some stats are interesting (2 responses out of 10 online approaches is a good number IMHO).
I'm considering pursuing a remote dev career but I'm writing only ruby code right now, have some personal projects which I need to polish and started learning JavaScript. I would be interested to read more stories on the same topic but with much less verbosity.
Re: On Interviewing as a Junior Dev
#5> I did a code challenge that involved ranking soccer teams, and while going over the code a developer at the company asked me if I needed the rules of the game explained to me. While it's a good thing to make sure the candidate understands what the problem is, companies need to be aware that these things carry extra cultural baggage and asking a female candidate if they understand a basic sports rule (or any other m…
Yeah, I know I would want the rules explained to me. Personally, I think that it is a positive that an interviewer doesn't assume any extraneous knowledge on the candidate's part, since it prevents the candidate being in a position where they may feel anxious or embarrassed about asking for help or clarification, and lets them focus on demonstrating the coding abilities. It also presents a way to clear up any ambiguities right at the start.
Replace soccer with something like curling, or analyzing corn yields, or whatever obscure topic an interviewer wants to use to frame a question, and the interviewer's question comes across as perfectly valid thing to ask.
Re: On Interviewing as a Junior Dev
#6> I did a code challenge that involved ranking soccer teams, and while going over the code a developer at the company asked me if I needed the rules of the game explained to me. While it's a good thing to make sure the candidate understands what the problem is, companies need to be aware that these things carry extra cultural baggage and asking a female candidate if they understand a basic sports rule (or any other m…
Unfortunately, our culture generally views sport as a male domain. While you and I are probably aware that there's nothing intrinsically "male" about sport, it can feel a little weird for someone to treat you as if your understanding is aligned with the gendered assumption. Anyone, if they don't understand the rules of the game, could still ask what they are. Would you feel weird if someone assumed you knew the rules because you were a man? How could you tell if they assumed that because you were a man, or because of some other reason?
I think the point the developer is trying to make is that all this could be avoided by using another context in the challenge. Not using a different challenge is at least somewhat displaying that they didn't think how this situation might make someone feel.
Re: On Interviewing as a Junior Dev
#7> I did a code challenge that involved ranking soccer teams, and while going over the code a developer at the company asked me if I needed the rules of the game explained to me. While it's a good thing to make sure the candidate understands what the problem is, companies need to be aware that these things carry extra cultural baggage and asking a female candidate if they understand a basic sports rule (or any other m…
So.. the company asks a candidate if they understand the game, and just because the author of this post is female, she wildly speculates that they must only be asking her because she is female. This is ludicrous. Sounds like a feminist.
Re: On Interviewing as a Junior Dev
#8$95,000 for someone with 6 months school + 6 month internship is fucking insane. Holy shit!
Re: On Interviewing as a Junior Dev
#9That's a pretty impressive starting salary range for a junior.
a) You must have interviewed exceptionally well, and be in practice "not really" a junior (which would imply Ada are doing an incredible job, and is freakin' awesome), or be bringing to bear some other skills
and/or
b) Salary range where you are is broken
You said the range you got offered was $75-$95, which in Great British Pounds is £47-£60,000, and I've absolutely no reason to doubt you. BUT: you can get a reasonable senior developer in the most expensive city in the world (London) for £60,000.
Re: On Interviewing as a Junior Dev
#10That's a pretty impressive starting salary range for a junior. a) You must have interviewed exceptionally well, and be in practice "not really" a junior (which would imply Ada are doing an incredible job, and is freakin' awesome), or be bringing to bear some other skills and/or b) Salary range where you are is broken You said the range you got offered was $75-$95, which in Great British Pounds is £47-£60,000, and I'v…
The pickyness about jobs doesn't exactly scream junior dev either. Most I know would be glad to just get a job, and then after they've got some experience on their CV, they can be picky.