3 ms·
Is there a reason there's no naming and shaming going on here? One company asked me to do an implementation of the Bay Area MUNI network which fetched live upd
by JansjoFromIkea 7y ago
Is there a reason there's no naming and shaming going on here?
One company asked me to do an implementation of the Bay Area MUNI network which fetched live updates of the locations of all buses every 10 seconds; there was more to it but I can't remember it now. This was to be done in React with D3 and no additional libraries were to be used to help with integrating D3 maps in React.
The role was junior level, the job listing did not specify D3 as a requirement (which pretty much guarantees a lot of people would start into it without realising maps are one of the more complicated things to do in D3 as a newbie or how poorly D3 played with React), the role was in Europe.
If someone can confirm I'm not breaking any rules I'll happily share their name.
The best interview experiences I've had are with groups who just went through my (not very impressive) Github. A small coding challenge can be good as a thing to talk through during the final interview but anything longer than that and I'll tend to pitch sending them something I wanted to make in my own time regardless.
- zymhan 7y ago> Is there a reason there's no naming and shaming going on here? No, there is no rule, unless you signed a contract stating you will never disclose any interview information, and even then, they'd have to find your post, find out who you are, and then take you to court over an extremely shaky premise. Just name the damn company people! You're giving companies far more credit than they deserve in these situations. I'd argue you owe it to other people who may follow in your steps to know when a company is exploitative, deceptive, or just plain corrosive. edit: now with less snark
- JansjoFromIkea 7y ago> "Is there a rule I don't know about" > Goes on to not violate the rule that seems to exist Anyways, it was ThousandEyes
- zymhan 7y agoI appreciate you having the courage to call them out :)
- JansjoFromIkea 7y agoNo courage in that! The true courage is in admitting I was stupid enough to take a stab at their challenge. The interview itself was a whole other tale of awfulness but I'll limit my overview of it here to saying that they didn't bring up the coding challenge once despite being repeatedly asked for feedback before, during and after the interview. Maybe they felt awkward about saying how crap they thought it was? Be pretty weird to bring me in for an interview in that case though...