161–170 of 181 posts
Earlier quoted context omitted.
> faster than this guy escaping a dystopia in Asia, and trying not to be deported back While that guy may have an advantage over you in motivation, you might have an advantage over him in communication.
Also known as accent.
Earlier quoted context omitted.
To be fair, even remembering the names is really difficult, especially working in a large org, many people I see only once or twice or have just heard about. With pronouns most of the time I can luckily just resort to "them" if I am unsure. I frequently in a meeting am unsure if I have or when I have met the person before, although I do find their face familiar. That is the first level of awkwardness to solve for me.…
Yeah this ends up being exactly what I do, in addition to avoiding high-conflict individuals altogether. I can't handle the actual headache of keeping up with everyone's arbitrary titles. I'm not your Tumblr mutual or a goddamn MUSH engine. I'll humor transpeople since they offer some visual cue in either direction but enbies are deliberately obtuse and go ballistic when you get it wrong. I have more issue playing ba…
This sounds like a good exercise, and kudos for thinking differently and at least trying to create a fairer and more useful process. Two comments I'd make, that I hope you are already thinking about: 1. Role playing is a cringe-inducing experience for many (most?) adults. Please credit the interviewee with intelligence and don't try to actually role-play this. These are hypothetical scenarios, so discuss them as such…
> Role playing is a cringe-inducing experience for many (most?) adults. Depends a bit on the how: I don't think most find fire exercises, military exercises cringy - although they are a form of roleplay?
A fire drill where the Health & Safety guy insists that we pretend it's real - yes, most people find this cringe-inducing. For more on this, see Dwight Schrute.
Let the interviewer then dive into any technical challenges such a project may propose, in order to vet technical skills.
This allows a chance for candidate to show they can connect high level big picture thinking with low level technical skills.
Earlier quoted context omitted.
Pretty much this. Companies needed software engineers, looked at what Google was doing, and copied. And they call themselves innovative for doing it.
Ah, so to reach their hiring destination, their preferred mode of transportation is the bandwagon.
Earlier quoted context omitted.
> Role playing is a cringe-inducing experience for many (most?) adults. Depends a bit on the how: I don't think most find fire exercises, military exercises cringy - although they are a form of roleplay?
A fire drill where we don't pretend it's real but do take the drill seriously, is fine. A fire drill where the Health & Safety guy insists that we pretend it's real - yes, most people find this cringe-inducing. For more on this, see Dwight Schrute.
I don't see why simulating working a bug report need be cringe inducing... If everyone is just playing themselves.
[1] unintentional humor. I suppose there are some unfortunate people that have had to simulate helping someone with a mocha burn or similar injury. I meant "mock injury".
Earlier quoted context omitted.
Does 99.995% [1] of hackernews sound reasonable enough to you? The reality is a lot of systems (especially simple ones) run perfectly fine on a single server with next to no downtime and all the additional redundancies we introduce also add additional points of failures and without the scale that makes these necessary you might actually end up reducing your availability. [1] https://hn.hund.io/
> Does 99.995% [1] of hackernews sound reasonable enough to you? How did you come up with that number? I looked at the link and just one of the outages listed on January 10 was 59 minutes. That alone makes the uptime worse than 99.99% for the entire year before it was halfway through January. (99.995% means at most 26.3 minutes of downtime per year. See https://en.wikipedia.org/wiki/High_availability#Percentage_c...…
if you click the history it says 98.452% over 365 days.
Earlier quoted context omitted.
absolubtely! One of the best jobs I ever worked at asked me what CPU I had in my computer at home, I talked about how i'd built my own pc and the parts that went into it and why, and they (much) later when I was settled at the role said they could see I was a good candidate from that point onward. I think its useful to show a curiosity about your tools, about the boundaries of your world, which is useful when things…
Do you really think it made you a better candidate, or did this person just feel a connection due to a similarity in interests or in your approach to computing? Was it even relevant for the job?
It's hard to say for sure - both of these things are also part of being a good candidate and working well in a team.
But I do think that this experience is both because of and forms part of who I am, a certain troubleshooting & optimizing mindset and curiosity with machines. Is it strictly necessary, or will all people with this shared hobby/past be this way? I don't know. I do think its a useful or good fuzzy signal, to be best used alongside other signals.
Was it relevant for the job? Not for the job description. There were times when I used related experience to solve problems or smooth things over though, such as figuring out why a QA engineer's setup was bluescreening (faulty ram), or in having familiarity with tools built into windows for performance profiling and debugging memory & storage problems with programs
Earlier quoted context omitted.
I recently started interviewing again and haven't encountered many leetcode style questions this time around. I'm noticing lots of contrived questions that relate to some feature the company had to build.
This is my favorite, “we want you to work for free”