10 ms·
Becoming a dungeon master for an interview
- navane 3y ago> it feels like a very, very light version of the prep you do when designing a campaign as a DM With todays chatgpts, that reads like a pretty decent prep for a campaign as a DM.
- neilv 3y ago> Interviews should be as close as possible to the work that the candidate would do if they join. Interviews should give information to both parties about what it would be like if the person joined. Simulating a typical work task, as this article describes, might give you some of that. Though important to remember that's far from all that's relevant to either party. A recently fashionable Leetcode hazing, on the other hand, is mostly "anti-pattern". It tells the company whether or not the individual has studied for that ritual specifically, and was willing to submit to it for the approval of this company (or is using this company as practice for the gameable ritual). And it tells the individual nothing except that the company thinks this is a good way to do interviews.
- mooreds 3y ago> Interviews should give information to both parties about what it would be like if the person joined. I have participated in interview processes where, at the last interview, the employer tries to talk the candidate out of taking the job. Discuss the problems, the warts, the intractable issues, and other things that are downsides of this job. Every organization has these. I love this, because the employee is going to find all of the issues out anyway, and it's better for both parties if they part before employment begins if the issues are too much.
- neilv 3y agoInteresting, and I could see that working well for some places. I do something related to this in the interview. Part of the interview is more like things you'd tell a colleague who was considering that: pretty accurate characterization of what you know of the work, your idea of pros, things that might or might not be cons for the person, etc. Basically, they show up the first day, and their interactions with me are just the same (plus a little extra excitement on my part that they joined, and now able to share proprietary details but without unpleasant surprises). Six months later, and I'm still just the same (plus extra familiarity and increased mutual trust). And hopefully they also are what they seemed to be in the interview. Though you can't necessarily be 100% candid about everything in an interview, like if you were doing an internal assessment a technology, product, vendor, or competitor. For example, there are personnel issues, company image, proprietary tech, etc. Also, you don't want to say something that ends up misleadingly quoted out of context on a jobs forum or word-of-mouth by someone with a different sense of professionalism or confidentiality, and you don't want to give ammo to a spy from a competitor. In practice, the line of what to say seems pretty intuitive to hit, and I haven't knowingly had a problem with it. Though, when working at one company doing exotic-sounding, high-value-sounding stuff, I did have a couple candidates grill me on the tech and/or on resources. On those I try to respond something like, "Some of that is very proprietary, and unfortunately can't be talked about much right now until someone joins the team. But I can tell you some of the public information from news articles and such is A, B, and C. There's a few marketecture diagrams on our Web site, and links to some published research papers that detail those aspects better than I could."
- deleted 3y ago[deleted]
- abathur 3y ago> was willing to submit to it for the approval of this company I abstain, myself. I have too much real work that I'd like to push forward to be able justify spending weeks of free time on fake work.
- paulcole 3y agoGreat! Isn’t that the point? That some people who really don’t want the job won’t invest a bit of their time and people who do really want the job will?
- TheCleric 3y agoSure. If what the company doing the hiring is explicitly trying to get employees who are willing to do that. However if they just want knowledgeable, quality employees, some will self select out of that process.
- majormajor 3y agoDon't forget about the people who don't have to spend weeks or months focused just on interview prep to do well on the average leetcode question... That's who interviewers are looking for. Now, a case can be made that there aren't that many of those people and you might not need them anyway, but... if you can spend a few weeks to catch up that's not all bad compared to what high-end job offers in other professions demand of your resume. The more we keep the interview process something demonstrable vs status/prestige/name-check/references, the better.
- paulcole 3y agoThese jobs pay a lot of money. If you want one bad enough you’ll find the time to practice.
- dinobones 3y agoIf you want to receive top compensation, and work at the Meta/Roblox/AirBnBs etc, you will need to be able to solve 2 Leetcode medium questions in 45 minutes, correctly and optimally. I work for a big tech company where people smell their own farts and think they are geniuses even though they work on CRUD interfaces for admin portals for Cloud. The interview process is well known. I have seen wrong solutions made by these genius question writers in their own doc, or where they find out 4 weeks later that the time complexity of their own solution is not really what they thhink it is. Do you really think in a company with 50k+ software engineers, where many studied English (but like to conduct CS interviews like they’re CS researchers), that everyone will know and understand details like; how the expected linear time complexity of quickselect works? It’s a nightmare; it’s blind leading the blind. It’s been completely gamified at this point and the only way to win is to play the game, maybe 10 years ago you could’ve passed on your own merit of having a CS degree and knowing basic DS&A, but I promise you that is almost the case nowhere anymore.
- adamgordonbell 3y agoI feel like leetcode is a Goodhart's Law thing. When nobody was cramming for it, then at some places it was a good measure. Coding is more like weight lifting sometimes then running. There are some weights that some people just can't pick up. And so if the job involves lifting things that are usually light but occasionally heavy, then a squat becomes a good measure for candidate. But once everyone knows a big squat is the way in, they train squats, they show up in lift suits, they use amyl nitrates and the whole thing stops being a good measure. Because on the job you don't squat in a squat rack, but pick things up where they are found, in the conditions on the ground. Goodheart's law breaks things, because now you have a bunch of people optimized for a task that isn't exactly the job.
- mooreds 3y ago> Goodheart's law breaks things, because now you have a bunch of people optimized for a task that isn't exactly the job. Companies lose another way too. Folks who might be darn good at picking things up decide it isn't worth the focused training to get into companies that only seem to care about squatting, so they don't apply.
- adamgordonbell 3y agoYeah, I feel like any measure like this starts as a way to measure a proxy for IQ. But as it becomes a known thing, people train for it and it becomes a measure of conscientiousness (In the big five sense, aka diligent trainers rise to the top).
- reaperman 3y ago> they use amyl nitrates I think you meant ammonia. Poppers would cause an acute decrease in blood pressure which would be counterproductive during the lifting phase with a heavy weight.
- yieldcrv 3y agomaking a react component in a 45 minute interview (something I recently did) is better than leetcode, but still a poor signal. on the job I'll never do a time trial where I'm being watched and gaslit about "just wanting to see how I think" as opposed to "do it perfectly from memory in this collaborative coding session faster than this guy escaping a dystopia in Asia, and trying not to be deported back" find a way to simulate that I will do it some time over the next two weeks because the product manager reduced everyone's story points in half for this sprint in the grooming session, and the fact that I even did that gets me praised because nobody else on the team finished their tasks
- azangru 3y ago> 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.
- gdsimoes 3y agoAlso known as accent.
- Our_Benefactors 3y agoAnd grammar, vocabulary, tone, etiquette… a lot more goes into communication than accent alone.
- deleted 3y ago[deleted]
- AlotOfReading 3y agoOn average, I enjoy these kinds of interviews much more than leetcode. The quality of the prep work and the ad libbing makes a huge difference to the quality of the interview though. One particularly memorable interview involved verbally debugging intermittent crashes the interviewer had recently seen. Unfortunately, they had no information about the software stack, unique symptoms, or access to status registers so it ended up like: "Is this bit of information available?" "No" Repeated for 30 minutes.
- bee_rider 3y agoThat seems like an interview that you passed (the company learned that you know a lot more than them about the resources available for debugging).
- pavel_lishin 3y agoIt also sounds like an interview that the company failed.
- rzzzt 3y agoAlso a high level of frustration tolerance.
- Scarblac 3y agoMore likely the interviewer was some internal recruiter type who had been given some example questions to ask but didn't know about development themselves.
- AlotOfReading 3y agoThey were an engineer on the team I would have led, not a recruiter.
- X9 3y agoLove this approach! We used this method for awhile when conducting interviews, usually with a couple problems escalating in difficulty. Found it to be way more helpful to watch how someone troubleshoots than to test their aptitude with specific skills
- golol 3y agoI think one issue with this is that some candidates who might be great at the actual job could, for whatever reason, be bad at this verbal type of simulation. Perhaps they work by staring at the problem on their screen a lot, perhaps they struggle to think at the same time as roleplaying. Just saying that this roleplaying aspect is somewhat tested for and doesnt align with the job exactly.
- mock-possum 3y agoYes precisely. Make sure that you’re actually selecting for what you mean to be selecting for.
- paulcole 3y agoA lot of companies would much rather pass over a great fit than hire a bad fit. Not hiring great people isn’t that bad of a thing in most cases.
- abathur 3y agoThe interview the post describes actually sounds like a good format for me, but I do have some problems adjacent to the ones you mention. As someone who struggles with ~parallelizing some tasks (especially when anxious), it would be great to have an up-front check in about how comfortable I am with the format of any technical ~challenge. (And even better to discover there's some wiggle room to accommodate.) For example, I find it very difficult to code my way through a problem and narrate what I'm doing and take feedback while I know I'm being evaluated and the clock's ticking. If the interviewer says something important in the middle of this, I often have to put down any plates I've managed to get spinning (and maybe go offload some adrenaline) and then ask them to repeat before I can even parse the words they said, let alone figure out how they apply to the problem.
- Animats 3y agoThat's called an in-basket test.[1] For a really unusual interview process, see how Jane Street, the trading firm, does it. They expect people to do well at this.[2] Their actual interview process starts each candidate with a stack of poker chips. In each interview, candidates get to make bets on various things that look like financial trades. If they run out of chips, they're out. [1] https://en.wikipedia.org/wiki/In-basket_test https://en.wikipedia.org/wiki/In-basket_test [2] https://figgie.com/how-to-play https://figgie.com/how-to-play
- a_wild_dandan 3y agoThey should live stream interviewing the stock trading fish. Go pro, little dude!
- d-lisp 3y agoA software system differs from the chaos the trading world represents. You can try to evaluate traders, but the deep truth is that very good traders can become very bad traders seamlessly because nothing guarantees any success of any kind in that domain. When interviewing software engineers you shouldn't care that much about the abilities that someone shows during the time of a technical interview on a specific day; that's not an appropriate way to measure the skills you need for your business. Leet code is an appropriate way to measure how much such engineer is able to perform as a competitive coder. You will never need a competitive coder in your team; because what to be done in SE is not about coding less than 10 lines of code in less than X minutes to transform data A into data B. But back to candidate selection, due to the short amount of time you have to meet applicants, you finally decide to hire whatever person that succeeded to find the fastest solution to the almost scholastic problem you proposed because in the end, you fail to understand what could be the appropriate selection method : aren't all candidates more or less equivalent if you stop proposing leet code problems ? What can prove that X person with 5 years of exp is less good than that one that worked at google for 6 years ? Does it really matters than candidate Y doesn't know Go when all the languages we use aren't that truly different ? Is someone from nowhere, without any education of any sort, but that seems to be an hobbyist programmer since his childhood really a bad candidate ? You never know, but because whether you're HR or the person with technical authority in the team, you don't want to risk anything, and you believe that a good leet code solver can do the work. And finally, to me, that's the truth : more than 50% of the persons you decided to offer an interview would have done the work with success, and at least 20% seemed very nice, and you couldn't choose so leet code was the thing.
- andrewstuart 3y agoHere's how to recruit software developers. 1: define the requirements for the job 2: devise questions that attempt to give insight into how well the candidate might meet that requirement 3: note down the candidates suitability out of ten for each question 4: TALK to the candidate in a free flowing and open discussion about their work, what they have done, how they built it, why they built it that way, their role in the project, what went right, what went wrong, what they would do differently. 5: Whether or not the candidate asks questions is a meaningless measure. What is meaningful is to sense their level of curiosity - about this job that you are offering, about computing and technology in general. Software development is hard and being good at it requires a level of curiosity. It's probably a concern if someone shows no curiosity in this job or software, though you need to be cautious about how you measure this - did you do a good enough job to explore their level of curiosity? Curiosity does not necessarily reveal itself without careful probing. 6: Discuss the actual work of this job with the candidate. Quickly run through the actual todo list of things that need to be done right now - talk through the hardest of those tasks - how would they approach it? 7: take a leap and employ the person you feel is right - do NOT go into ever deeper analysis, ever more interviews, ever more tests and checks and hoops. No matter how much interviewing you do, you probably won't really know how someone goes in this job until they've been in it 3 or more months. 8: Don't be so risk averse that you don't hire anyone. Do it based on your best guess. it might sound harsh, but do your best and be willing to fire them before their 3 month trial is up if they are not the right person. 9: Take into account enthusiasm - how much does this person want this job? And no, do NOT measure this until the end of the interview process - looking for enthusiasm in a cover letter is like wanting a girlfriend/boyfriend commitment before first date. 10: Pay more than people expect, if you can. $1K less than someone says they want/need reduces first day enthusiasm for the job, $1K more increases first day enthusiasm. Wind the numbers up and down for greater impact. 11: After the interview process is done, talk to referees, analyses interview results apples versus apples. 12: Interview gimmicks, leetcode, abstract questions should be red flags for interviewees. If you're looking for a job and find yourself in a silly interview, be willing to politely call it off and save yourself the time and hassle of dealing with a company that does not know how to recruit software developers.
- deleted 3y ago[deleted]
- wiseowise 3y agoI was expecting different dungeon master: https://thefinalrumble.miraheze.org/wiki/Van_Darkholme https://thefinalrumble.miraheze.org/wiki/Van_Darkholme
- neonsunset 3y agoTook me a moment or two to realize this is about DnD. After all, interviews tend to be a stressful and intense process...
- Tade0 3y agoIn interviewing I try to avoid approaches that in any form or shape resemble riddles, so ostensibly open problems but with predetermined acceptable answers. I've found that it's both frustrating for the candidate and doesn't give me much insight. Such a back and forth to me is too close for comfort, even though I used to be into role-playing games back in the day. Currently I try to use the little time I have to determine whether the person in front of me is a charlatan, so only questions that are easy to answer for someone actually having the skills advertised in their CV.
- im_down_w_otp 3y agoCould you just have them sign an NDA and pair with people on some non-trade-secret real issue that needs addressing? If you start by giving a little bit of context and then jump into some reasonable end of the backlog, then you get to see how they think of priorities, they get to ask you lots of contextual questions, you get negotiate with each other a thing to do, you get to investigate and/or develop a solution, and at the end of it all parties involved got lots of signal about what it’s like and what’s required to do the job. Not to mention you stand the chance of some normally useful thing getting further along too. Work with the person like they’re “consultant for a day” and see where you get to. Why is our industry so resolute to come up with a bunch of bespoke, oblique representations of a job when the actual job is right there available to be used for assessment?
- pavel_lishin 3y agoMy favorite interview experience was a short take-home that required me to write a toy version of something the company actually did on a day-to-day basis, followed by an in-person pairing session to extend that toy to handle more functionality and cover certain edge cases. Of course, the downside is that it required me to spend four hours working on this at home, and then another several hours at the interview - but having to spend time interviewing is something that cannot be avoided, so I'd much rather the time be spent on something relevant that actually shows off my abilities, rather than playing Advent of Code with money at stake, or filling out astrological profiles.
- one_buggy_boi 3y ago> When interviewing as a software engineer, for example, you’ll run into places that lean heavily on algorithms interviews. And don’t get me wrong, those interviews can be fun (in the same way that Project Euler can be fun), but it’s not very relevant for most jobs I'm curious what changed around 2015-2016 that led to the current interview process. In the before times the interview was more of a technical conversation, sure they had some gotcha questions, but nothing too brutal. If you had real experience that you could talk about, maybe it was validated against references or a background check. People usually looked for a CS or adjacent degree, and that was enough. The quality of folks wasn't too different in my experience. I really feel for those with a lot of experience that are being dropped into the fire, especially those with families who may not have the time to memorize patterns for 3 months, but are still very capable. Non-tech, low paying jobs now ask you to create a soduko solver or trap rain water within 45 minutes. There's not many places to go for those that don't 'adapt'.
- dmoy 3y ago> I'm curious what changed around 2015-2016 that led to the current interview process. In the before times the interview was more of a technical conversation, sure they had some gotcha questions, but nothing too brutal. If you had real experience that you co... Places just copied big tech companies that were already doing that for many years prior to 2015. I had leetcode style interviews well before 2010 even.
- sailorganymede 3y agoPretty much this. Companies needed software engineers, looked at what Google was doing, and copied. And they call themselves innovative for doing it.
- baner2020 3y agoA company whose smart engineers threw their hands up claiming no moat while they were the pioneer of AI
- a_wild_dandan 3y ago
- tptacek 3y agoIt is possible to structure interviews so that: * Every candidate get an almost-identical interview * The interview is not heavily dependent on the investment or natural aptitude of the interviewer * Interviews generate data that can be scored by a rubric * Interviews aren't scored by the interviewer, thus eliminating the intrinsic bias of being in the hot seat with the candidate It looks different for every role. For instance, for a penetration testing role, I've run standardized interviews that involve generating and prioritizing attack surface lists and hypothetical bug lists. The output isn't "pass/fail", it's the list of places to test, the list of bugs expected, scheduling/testing budgets, and things like that. If I'm delivering the interview to the candidate, I'm presenting the panel of reviewers not my opinions on the candidate, but what they came up with. The same approach works for general software development (we don't use it here, we have an even fussier process). You can do design exercises, you can work out the dependencies that are going to be needed for a particular complicated project, you can do estimation exercises, you can catalog likely bugs. Review some PRs together. Look at the day-to-day work your team does, and then make the exercise a model of that work. It's not especially easy to do compared to just sitting down and asking a bunch of questions. Moreover, it's very hard to adopt it as a practice, because you have to trust the rubric (iterating on it over time, but using it enough for it to be meaningful) and not override it based on extrinsic considerations (referrals, misgivings about candidate background, &c). But the upside is pretty obvious? Once you have it worked out, you get a repeatable process, something that is naturally geared towards iteration and improvement. Standardize your interviews, generate data, have a panel make the decisions and not the interviewer. You can still play the interview like D&D if you want!
- deleted 3y ago[deleted]
- dangus 3y agoThis sounds like a regular situational interview?
- breadchris 3y agowow awesome analogy. I got rejected because my leet code solution wasn't fast enough for a security engineer position. The person who referred me was furious. Meanwhile, another interviewer did just this to me and it let me flex my knowledge. Would love to see this more. There is also the inevitable future where someone publishes a book on it and it gets cargo-culted. C'est la vie.
- kqr 3y agoThis is called simulation and it is a useful tool both when selecting for and training for cognitive skills. Importantly and usefully, simulations for cognitive work do not require any sort of physical fidelity, so it's really easy to set up basic scenarios like for hiring. (The main cost in using simulation for training lies in designing scenarios that train for expertise. That takes slightly more advanced elicitation methods which fall under the umbrella of cognitive task analysis.)
- randomgiy3142 3y agoA good interview should be a good fit for both parties. Just have a casual lunch with them. You should be able to tease out if they are a good fit. These “hacks” are so ridiculous. Way to overthink something.
- neuralzen 3y agoI went through something similar once when I was interviewing for an IT position in the Antarctic (I'd applied for positions at both McMurdo and Amundsen-Scott), and I was supposed to connect to their network simulator to troubleshoot and solve some network issue, but it wasn't working on their end so the interviewer walked me through the scenario, and responded as a DM would. - Quite frustratingly this was my 3rd interview for the position, and although I diagnosed and solved the DM'd scenario of a downed vlan issue in a Cisco environment in ~5 minutes of this off-the-cuff "simulation" using DM provided prompts, help menus, and outputs, I did not get the job. I think he penalized me for relying on the DM provided help menus and auto suggest tabbing...which is something anyone on a working simulator would have done. Which was a bummer because even though I was overqualified for the positions and would take a pay cut, I really wanted the experience of living for months in the Antarctic. So while I see the usefulness of this kind of interview, there are noteworthy issues of bias which a real simulator wouldn't begrudge you.
- bodelecta 3y agoI've just went through a round of interviews from various companies after being made redundant from work 4 months ago. Admittedly the job market was really quiet but it was eye opening the differences in interview techniques and processes. I had one interview from a FinTech company which I actually thought went quite well, the next day I got a rejection stating "I need to improve my STAR technique". I just rolled my eyes thinking FFS Another company the CTO wasn't on the call but had asked to record the last 15 minutes of the interview with questions he'd prepared, I was close to terminating the interview. If he couldn't be assed sitting in on the interview why should I answer questions the interviewer himself didn't understand. One of the questions was "What is triple D". I'm an experienced dev, fully aware there are too many acronyms in the industry but had never heard of triple D before, when I googled it after I was thinking FFS, that's just what any competent dev does by default. I guesses data driven development but admitted I wasn't sure. Another interview the principal engineer yawned 3 times when I was talking before I even got to the half way stage, not one apology. I know it's just human nature but to not even acknowledge he was making me uncomfortable reminded me afterwards that it's probably a toxic work culture, which I've been told since is the case from people who worked there. Thankfully at the start of the new year I was offered 3 roles, 2 of them I thought I'd screwed up the interview. The one I accepted, apart from taking on a task to review some code and raise issues with it, I was asked to describe an architecture of some system I'd worked on and enjoyed. I spoke too long, going past the interview time but didn't feel I explained the whole system. I understand interviewing candidates is difficult, I've had to do it a few times in the past but the competency of interviewers and the process to score candidates varies wildly from organisation to organisation. A realisation for me although I was already aware of it, is the personality of the people interviewing you varies wildly, more often than not it's a good indication of the organisation itself.
- dkarl 3y agoI think the "fake product" interview is a great format, but it can be done poorly if the setup is unrealistic. I've been on the receiving end of a couple of very bad attempts. In one, which I have described here before, an interviewer asked me to design a system for selling concert tickets. After half an hour of confused back and forth, it emerged that they wanted a network service that replied to requests with unpredictable random integers, which did not repeat, unless the service rebooted and then it was okay if there was an accidental repeat. Needless to say, I started with a lot of assumptions based on the idea of selling concert tickets, and I don't think it reflected poorly on me that it took so long to figure out that the real problem they were judging me by was so radically different from the one they asked me to solve. I had another interview recently which had a similar wrinkle. The interviewer asked for a system to solve a very particular problem, which because of the particulars of the problem would involve receiving very small amounts of data from systems in the field. The interviewer asked multiple times about the cost of data ingress and data storage, and each time I deflected them, saying that it wasn't significant compared to other costs in the system. I was so focused on solving the problem as stated that it didn't dawn on me until later that the interviewer likely had a different problem in mind in which the data was much bigger, and they were evaluating whether I could be sensitive to those costs and design an economical system. Interviews like these are very frustrating, and I don't think they will lead to great hires. You will end up hiring people who solve the problem you have in mind even though you told them to solve a different problem. These programmers will have the same biases and preoccupations as you, which might make them easy to incorporate into your team, but they will probably have the same blind spots as well, which means your team will be less prepared to solve new problems in the future.
- ascar 3y agoTo be fair, I would say if your task is to design a system it's your job to find out what the person actually wants and not run with assumptions you made based on a bad description. The reality is that you will usually start with a bad description. So I'm not sure if these misunderstandings actually reflect that badly on the interviewer/the question.
- 3y ago
- rohanjain91 3y agoThat's very similar to how good product management interviews are conducted.
- MagicMoonlight 3y agoThat actually seems like a good idea. Interesting, practical and you can see if they are socially inept. I’d actually try this.
- fanseepawnts 3y ago[dead]
- Donaldobob 3y ago[flagged]
- jayceedenton 3y agoThis 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. 2. As interviewers we are incredibly prone to seeing the things we know as obvious. When you devise an exercise, you can start to believe that everyone should easily see what you consider to be the 'right' way forward. In fact, seeing it may rely on your many years of experience in your company's culture, or your many years of experience with the interview exercise! So please, always remain skeptical of your assumptions about what is obvious, and avoid the trap of expecting candidates to see or follow the path that you think it's best. If any of your support scenarios are actually devious riddles that require one perfect question or leap, then whether candidates 'get it' or not will be random rather than indicative of better performance in-post.
- e12e 3y ago> 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?
- jayceedenton 3y agoA 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.
- e12e 3y agoThere's a bit of a difference between a fire drill in an office building from the perspective of a regular office employee - and a firefighter. In the latter case it would be expected to have people working as victims complete with mocha[1] injuries and feigned panic. 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".
- j7ake 3y agoCompanies should rather ask the candidate to describe a project they completed. 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.