News for hackers. Stuff that matters.
Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @12:17AM (#23983477)
We use a 3 step process, sans whiteboard: 1. First interview, the candidate interviews us. What market we serve, what our development processes are, what our technology stack is. If they express interest by being prepared and asking good questions, we send them home with

2. a programming task. Choose 1 of 5 tasks. The tasks are not abstract problems or puzzles, but come out of the designs we've implemented. We ask for 100 lines of code and not more than 2 hours. They take as much calendar time in days as they need, most have full time jobs, and let us know when you're done. The candidate then comes back, typically in 2 to 7 days and hosts a code review in front of our team. I give strict instructions before hand: The purpose of the review is to learn how they thought through the problem and how they solved it, not to criticize their style and approach.

3. If we decide we like them to this point, the third interview is with managers from other functions. How well does the candidate communicate, come across to non-developers, express interest in the company and role, etc. It's a check point to look for concerning weaknesses, as well as get buy in from the broader organization.

We like this approach because it allows the candidate to code in a much more natural environment. They can take the time they need and comfortably solve. No one spends their professional career coding on a white board. This approach so far has yielded excellent results. We ask developers how much time they took in the programming task and why they chose the one they solved. The programming task is telling, not in the quality of their code and how long they took, but how much did they get into it? We have had the range from candidates who did not complete it at all and opted out, to candidates who stumped 40 year veterans with elegant code. In every case, we learn how well they can express their thoughts, and importantly, their level of love for the discipline. This is as important to me as any other attribute.

Re:Hiring Without Whiteboards by fiblye on Wednesday July 29, 2020 @01:04AM (#23983653)
A lot of people in other comments below are criticizing take-home tasks, but honestly, this sounds nice and balanced. I'd much rather have a couple days to think about a problem and a few hours to implement it over having to take time off work, pay to go all the way to your company at a time that works for both of us, and deal with a white board interview. It's a way bigger investment. So long as it's a small, confined, practical problem and not a full app, this sounds good.

Plus, if your company gives someone what they might think are ridiculous questions or they realize it's just not what they're good at, they can easily reject proceeding any farther with the interview. If someone walks into a crappy whiteboard interview, they feel kind of stuck. Seems to be better for both sides. Less pressure.

Re:Hiring Without Whiteboards by GordonS on Wednesday July 29, 2020 @12:40PM (#23988718)
Despite having a family not much spare time, I also like the take-home approach.

But any time take-home tasks come up on HN, there are always people here complaining about it and even demanding to be paid for their time.

I get that it doesn't suit everyone, but nothing does. Coming up with an approach that works for the company and candidates is really hard - as evidenced by the many, many threads on this subject here on HN.

Perhaps the best compromise would perhaps be to permit the candidate to perform the task there and then or take it home, but this may require more of a commitment from the interviewer, if they then need to additionally devise tasks to be completed in a shorter time.

Re:Hiring Without Whiteboards by wildrhythms on Wednesday July 29, 2020 @08:36AM (#23985939)
I oppose take-home tasks as an interviewer. I don't think employees or prospective employees should be taking work home with them, ever. Instead, collaborating on a problem with the interviewee, discussing the problem and potential solutions, observing how the interviewee recognizes when they go off-track, how they respond to hints and suggestions... these are all better signals than the culmination of some homework task, and easily captured in a 30-45 minute interview.
Re:Hiring Without Whiteboards by tchaffee on Wednesday July 29, 2020 @11:14AM (#23987533)
> collaborating on a problem with the interviewee

That's not how developers spend the vast majority of their time. It's a poor signal in my experience. What it selects for is candidates who are immediately comfortable collaborating in real time with someone they have never met. That doesn't mean you aren't getting good candidates. What is means is that I spend far less than you finding good candidates because I also hire people who are great developers and who would fail at your interview.

Re:Hiring Without Whiteboards by pc86 on Thursday July 30, 2020 @07:46AM (#23997003)
If you're working on hard problems, 30-45 minutes isn't even enough time to fully context shift and get into flow, let alone in an interview where you are a) stressed, b) trying to impress, c) unfamiliar with the specifics of the organization, d) potentially unfamiliar with the industry entirely. This simply isn't enough time to get a sense for how someone thinks or approaches things that are going to be impactful to a large organization except at the most superficial levels. However, if they have a couple hours at their leisure to approach a problem, it's very easy for them to go over how they approached it and where they got stuck in just a few minutes.

The compromise here is to talk about the employee's past projects. The downside is now the interviewer needs to get up to speed quickly, and won't have all the necessary context of the organization and (potentially) industry. Not to mention the fact that candidates lie a lot about how much of a role they actually had in projects.

Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @09:06AM (#23986180)
We have both elements. The code they wrote is subsequently reviewed live with 3 or more of our engineers and all of these aspects are explored.

I think what gives our approach balance is that we are also committing to making a time investment. Reviews typically last an hour, which means that the 2 hours we ask from the candidate is matched with 3-5 hours of our engineers' time to review and discuss with them.

Re:Hiring Without Whiteboards by bryanrasmussen on Wednesday July 29, 2020 @06:42AM (#23985260)
>1. First interview, the candidate interviews us. What market we serve, what our development processes are, what our technology stack is.

I somehow feel this rewards opinionated developers.

Also right now I'm looking at a couple places because their recruiters called me up and said they were willing to meet my requirements which are basically pay - I don't care about most of these things, if they want me to do stuff and are willing to pay my rate and if they, after looking over my cv believe I can handle their stack, that's it. I don't really have any questions for them.

So I guess you don't have people looking for people for you - you only have people coming in that think your company is special enough that they really really want to be there and are invested about finding out everything just to confirm that commitment on their part is good?

on edit: this of course supposes that 90% of the companies out there are very similar and do not have any problems that are so interesting that I should feel prompted to ask. If I ever applied to the Internet Archive I'm sure I would have things I would like to ask.

Re:Hiring Without Whiteboards by awhitby on Wednesday July 29, 2020 @08:49AM (#23986047)
Aren't opinions something an employer should want in developers? And not just opinions on tech stack but all the way up to requirements etc.

If I hire a developer "to build X," I would rather work with the developer who explains that X is the wrong thing and we should actually build Y, than the one who shrugs, asks no more questions, and builds a really excellent X - that later turns out to be the wrong thing to have built.

Re:Hiring Without Whiteboards by jjk166 on Wednesday July 29, 2020 @10:24AM (#23986991)
At the interview stage, the candidate has been looking at your use case for at most a couple of hours with very little context. Assuming you've done any work on X and that you are competent, X is probably a good choice or at least there's good reason to believe it is a good choice. It might be nice if the candidate asks why you chose X over Y, but they shouldn't seriously propose that you should switch over to Y. Best case scenario they're assuming their little glimpse gives them a deeper understanding of the problem than you, which suggests they're cocky, worst case they may be deliberately selling you on a potentially worse solution that they just happen to be more comfortable with, ie they're inflexible. A good developer should wait until they know what they are talking about before they form an opinion on what would be the right tool for the job.
Re:Hiring Without Whiteboards by swsieber on Wednesday July 29, 2020 @08:58AM (#23986120)
There's a difference between opinionated and having an opinion. I think Rust is much more pleasant to work with (an opinion), but I'm not going to let it stop me from using other things (not opinionated)
Re:Hiring Without Whiteboards by gjm11 on Wednesday July 29, 2020 @07:36AM (#23985553)
Something seems badly off to me with the phrase "candidates who stumped 40 year veterans with elegant code".

I don't want code that stumps anyone. I want code that delights 40-year veterans, for sure. But the signal of genuine elegance is "oh, that's a lovely way to do it" much more often than it's "how the hell does this work?".

Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @08:33AM (#23985918)
It was more of 'I didn't know the C language could do that'. The elegance was that what it did was obvious.
Re:Hiring Without Whiteboards by nilkn on Wednesday July 29, 2020 @01:49AM (#23983822)
How do you avoid awarding candidates who violate your request of no more than two hours and spend considerable time coming up with something amazing? They may still produce 100 lines of code — but those 100 lines may end up being unusually elegant, beautiful code that stumps 40 year veterans. How do you avoid punishing someone who took your requested time constraint seriously (or otherwise didn’t have enough free time to violate it anyway)?

That’s not to say I don’t think this process has promise, but I’d need to be convinced that the above two issues can be fairly dealt with first.

Re:Hiring Without Whiteboards by IggleSniggle on Wednesday July 29, 2020 @02:07AM (#23983889)
I'm of the opinion that this is fair enough as long as the pay isn't crazy high. The truth is, no interview is ever truly fair, and all interviews can be gamed. "Grinding leetcode" is much the same problem you are describing wrt spending 40 hours on a 2 hour project. People game non-technical interviews too. And resumes.

It sucks, but you only need to be better perceived than the next best competitor. Most folks don't have 40 hours to spend on a 2 hour max coding challenge. Hopefully the ones that do are already employed and not currently competing with you, or are so inexperienced that 40 hours produces horrific over-engineered abominations instead of clean efficient readable code.

Re:Hiring Without Whiteboards by wvenable on Wednesday July 29, 2020 @02:15AM (#23983917)
I reject entire the premise of this question. Anyone spending huge amounts of time is either going to produce way too much or they just took too long. There is nothing magical about programming where taking 8 hours to solve a 2 hour problem is going to stump 40 year veterans or be unusually beautiful. That's just unrealistic.
Re:Hiring Without Whiteboards by ht_th on Wednesday July 29, 2020 @04:07AM (#23984405)
You are taking it to the other extreme. Sure, in 8 hours I will not write something "unusually beautiful". But if I spend two hours solving a problem and hacking together a solution, I come to better understand both problem and solution. Hereafter, I then can rewrite my solution in another couple of hours and improve it significantly with respect to maintainability, readability, naming, messy choices, &c.

If I want this job, I would spend this extra time to submit this better solution because obviously that will improve my chances of getting the job. But that means that these take home assignments might not be such a good indicator of efficient proficiency. You might be overvaluing people spending more time on these tasks and undervaluing people spending the allotted time on these tasks. For example, a better developer who did write a solid solution in under 2 hours might get passed over because her solution seems not as good as mine where I did spend another hour to rewrite my initial messy solution.

Re:Hiring Without Whiteboards by dmos62 on Wednesday July 29, 2020 @03:47AM (#23984316)
That's not my experience at all. To a limited extent, you can get something more beautiful by just putting more work in it.
Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @09:00AM (#23986140)
Actually, if they spend more than two hours, the question is why. We are happy to see them get interested in the task and dive deeper, but we just don't want to ask for more, that would be unreasonable in our view. It's fine if the code is broken, or has a couple of bugs. (It's best if it compiles though!)

The goal is as much to learn how they think, solve problems and communicate as it is whether they know how to write software.

I'll give one example: One task is to figure out how long it takes to grab the current time from the operating system. We use a rather obscure OS. A candidate chose this and solved it simply (though it's got a couple of points to mind), but then he got curious and wanted to know whether a virtual machine had a different timing and then what the performance on a different operating system was. He told us that he spent about 8 hours altogether. I felt a bit bad on one hand, but on the other, it's exactly what we like to see: Solid programmers who love programming technology for its own sake.

Re:Hiring Without Whiteboards by twic on Wednesday July 29, 2020 @01:15PM (#23989150)
Something i've seen a couple of times is giving a take-home exercise, then working on it further in the on-site interview. The first stage filters out people who can't get things done even given as much time and help as they want, the second stage filters out people who can't get things done at a reasonable pace without a helping hand.

I think it's common for an on-site interview to include a reasonable chunk of programming, and using a continuation of the take-home to do that is good because it means the candidate isn't starting from scratch. Coming in warmed up should minimise noise from nerves, unfamiliarity with tools or context, etc.

Re:Hiring Without Whiteboards by tziki on Wednesday July 29, 2020 @02:02AM (#23983859)
This. I just can't see this not penalizing conscientious candidates.
Re:Hiring Without Whiteboards by frequentnapper on Wednesday July 29, 2020 @01:50AM (#23983825)
Damn, can I do one just for fun and then let's code review together? :p

I recently had a humiliating experience. Just was approached on LinkedIn and at first they sent me a take home. I learned the front-end tech which was required for it, and then coded it. They just wanted me to fill out a doc but I put it all up on stackblitz. Another portion was back-end which I also put up on another online env so they could see not only the code but how everything was laid out.

Get to the over the screen share interview - just nervous and both the interviewers were impatient, and just the atmosphere was so nerve-wracking - they did nothing to make it more relaxed. Just seemed like the senior guy was stressed out and I was wasting his time. My brain kind of shut off and the seemingly simple problem at that time just seemed insurmountable because I felt myself second guessing my every thought.

Been developing for a number of years for a few companies, and I guess I haven't prepped for the tech interview - I thought my existing skills are what they need and should be enough to evaluate but boy was I wrong.

Needless to say they didn't go with me. It's not like I needed the job, or probably wouldn't have taken it anyway since what their maximum range was lower than what I make, but the startup seemed quite interesting. Just such a bad experience.

Re:Hiring Without Whiteboards by JauntyHatAngle on Wednesday July 29, 2020 @02:55AM (#23984086)
That's annoying, but sounds like you avoided a bad team environment anyway?

If they're not placating you at all than I doubt that'd be a great environment to work in. Or they'd already selected someone.

Re:Hiring Without Whiteboards by genericlogic on Wednesday July 29, 2020 @06:15AM (#23985131)
A key point in your process is that you have a conversation before the homework phase. The last time I was job hunting I would be given homework without ever having a chance to talk to someone. I did that once, sent my work into an automated system and never heard anything back besides an automated thank you.

I think if I was interviewing using your process I would submit code because I would guaranteed a chance to talk about it with other developers.

Re:Hiring Without Whiteboards by ProZsolt on Wednesday July 29, 2020 @08:34AM (#23985922)
Yes, if you aren't planing to invest in me. I won't do your homework. In this way you will only get desperate candidates.
Re:Hiring Without Whiteboards by tziki on Wednesday July 29, 2020 @04:15AM (#23984446)
Why not time the programming task? Since it's supposed to take about two hours you could ask them to choose a two hour slot, email them the task at that time and have them return it two hours later. This wouldn't penalize people who choose to abide by the time guideline vs more dishonest candidates.
Re:Hiring Without Whiteboards by ProZsolt on Wednesday July 29, 2020 @08:32AM (#23985905)
When I have limited amount of time even if it's more than enough I get stressed. When I'm on a job I have time to think about the problem, come up a rough solution in my head then start coding. If I have a hard limit I don't think that much because what if I don't have enough time to write it down? In the sort thinking phase I came up with a subpar architecture, but even if I have an extra half hour in the endI can't really change it or worst You cant finish it because I didn't think of an edge case.
Re:Hiring Without Whiteboards by twic on Wednesday July 29, 2020 @01:17PM (#23989177)
If your slot starts, and then something comes up - your elderly grandmother phones, your internet goes down, your roof springs a leak - that would be pretty annoying.
Re:Hiring Without Whiteboards by cutemonster on Thursday July 30, 2020 @05:50PM (#24003231)
What about visiting a coworking space and blocking your grandmother's number?

Temporarily only

Re:Hiring Without Whiteboards by friendzis on Wednesday July 29, 2020 @04:04AM (#23984393)
> The tasks <...> come out of the designs we've implemented.

I guess the tasks are something like "take this scaffolding and implement thing x". What would you think if the candidate responded saying the scaffolding does not allow to implement X properly without sacrificing things y and z, and instead of turning in code for review would show up for a discussion about the compromises and deficiencies in the scaffolding?

Re:Hiring Without Whiteboards by cutemonster on Thursday July 30, 2020 @05:58PM (#24003311)
> if the candidate responded saying

Responded how, when? (At what point in the process)

Re:Hiring Without Whiteboards by friendzis on Monday August 03, 2020 @02:35AM (#24034762)
> At what point in the process

> > instead of turning in code for review

I.e. something like instead of turning in code example they turn in a motivated analysis of why the scaffolding provided cannot support "proper" (and then analysis of so called proper) implementation of the thing asked, provide analysis for changes required in the scaffolding.

Basically, the candidate would turn "provide and review code" process into "let's talk about architecture, implementation and tradeoffs". Would you discard such a candidate for not following the process because you expect seniority or would higher level thinking be a plus?

Re:Hiring Without Whiteboards by ShamelessC on Wednesday July 29, 2020 @02:04AM (#23983870)
How do you feel about paying candidates for the time they spend on the assignment?
Re:Hiring Without Whiteboards by Polylactic_acid on Wednesday July 29, 2020 @02:37AM (#23984009)
I once applied at a company that started with a programming test before any human communication. I think I did a pretty good job on the test. After that I was rejected when I assume they saw my resume. They gave me $50 store credit on their website (custom sticker printing). I assume it cost them a lot less than $50 but it was still pretty cool.
Re:Hiring Without Whiteboards by justinlloyd on Wednesday July 29, 2020 @03:48AM (#23984317)
This past week one of the companies on "who's hiring" sent me three challenges that "would only take 2 hours" before I ever got to talk to a human being or even got a human being responding with an email. This was a fully automated system apparently. "Take this programming test, we'll let you know if you're good enough to talk with a human."

Whilst the challenges were not particularly complex, you also had to ensure that the person who was going to run your code could stand up your environment, so part of the second challenge was "thoroughly document how to run your code, the environment needed, etc, etc."

Life is too short to deal with this kind of stonewalling.

Re:Hiring Without Whiteboards by collyw on Wednesday July 29, 2020 @04:25AM (#23984498)
We (the whole developer community) really need to stop responding to such companies.

I did one recently after the initial HR person chat. I spent a morning on it as they suggested 2 or 3 hours. But then I was rejected for the most pedantic reasons (2 white space PEP violations), not setting up mocks for testing (that would have doubled the scope of the project). Providing an HTML response rather than JSON when the spec asked for a "page, don't bother about styling". And various other trivialities.

I tried passing on my complaints, but the HR girls didn't like that. Pretty disrespectful after giving up a morning of my free time.

Sennder is the company, as I feel that we should be naming and shaming.

Re:Hiring Without Whiteboards by VonGallifrey on Wednesday July 29, 2020 @06:05AM (#23985067)
I just completed this exact challenge (Yes, for Sennder) and I think their challenge is fine. It is not really difficult or takes much time at all. They didn't seem too strict in their review and I was able to discuss some of the "mistakes" and choices I made in the tech interview. Including some PEP8 violations. Despite these mistakes I passed the tech interview just fine and I just have the CTO interview left.

I don't see how mocks would have doubled the scope of the project. I think I have mocks set up in a few lines of code or so. If your project is so difficult to test or if it is difficult to set up mocks for it maybe there is a serious flaw in your project structure?

> Providing an HTML response rather than JSON when the spec asked for a "page, don't bother about styling".

I don't understand what you mean with this. Did you provide a HTML response or did you provide JSON? I did a super simple HTML response with no styling and that was fine. If you did JSON I could see how they would mark it as a mistake when they clearly asked for a HTML page.

Re:Hiring Without Whiteboards by collyw on Wednesday July 29, 2020 @09:18AM (#23986301)
They did say that they were planning on changing it so maybe you got a different one. I gave them HTML, and they claimed that "JSON would have been better" despite the specification asking for a "page" with "no need for styling".
Re:Hiring Without Whiteboards by caymanjim on Wednesday July 29, 2020 @08:13AM (#23985753)
It sounds like your submission was unrefined, maybe amateur. That's what tests like this are for. Referring to "the HR girls" isn't winning you any points either, and makes me wonder what kind of attitude you displayed to the people involved.
Re:Hiring Without Whiteboards by collyw on Sunday August 02, 2020 @09:35AM (#24028613)
Not as amateur as the spec.
Re:Hiring Without Whiteboards by wildrhythms on Wednesday July 29, 2020 @08:43AM (#23985999)
I turned down an offer from a direct competitor company because they tried to funnel me through an automated programming "test". I told them I have years of experience at their competing company whose hiring bar is notoriously high, and they still demanded I take their weird test.

The company was Goldman Sachs. Name and shame.

Re:Hiring Without Whiteboards by GordonS on Wednesday July 29, 2020 @02:55PM (#23990332)
You need to try to see it from the hirer's perspective too.

I don't interview much these days, but I spent several years of my career sifting through CVs and interviewing candidates.

The number of candidates with seemingly impressive CVs and apparent several years of experience, yet whom basically couldn't code, was shockingly high. And when I say "couldn't code", I'm talking "couldn't even fizz-buzz" levels of incompetence.

The fact is that there are many devs out there who coast through jobs, while all the time it's their colleagues who are doing all the work.

I wasted, many, many hours of my life before realising that it was pointless interviewing candidates that couldn't code - asking them to perform a sort of gatekeeper test improved things immensely.

So it might seem insulting to have to perform these entry tests, but unless you already have code publicly available (e.g. on GitHub), you shouldn't take it personally.

Re:Hiring Without Whiteboards by pandaman on Wednesday July 29, 2020 @11:04AM (#23987434)
I had similar experience with Facebook, not directly competing as they are just expanding into my area of expertise, but they had been looking to poach. The recruiter told me that the first step will be a test to determine if I can program so I told them I am not interested without even trying to negotiate out of it.
Re:Hiring Without Whiteboards by cutemonster on Thursday July 30, 2020 @05:45PM (#24003202)
> a test to determine if I can program so I told them I am not interested

It seems you don't enjoy coding?

Re:Hiring Without Whiteboards by pandaman on Thursday July 30, 2020 @06:38PM (#24003607)
No, not writing code per se.
Re:Hiring Without Whiteboards by lukey_q on Wednesday July 29, 2020 @02:33AM (#23984001)
I created a similar task at my company as the parent commenter, building a small frontend to an existing API that can be completed in a couple of hours. There's no time limit for turning it in (we suggest two weeks but don't enforce it) and we specifically tell people that a good, concise solution to the problem at hand is perfectly fine, and even might be better than a sloppier solution that tries to add bells and whistles.

When I set it up the goal was to avoid a lot of the issues I've personally had or heard about with coding challenges: they take way too long, they're too abstract, or you feel like the company might just be using you to get a couple of days of free work on their actual codebase. For this reason I feel fine about not paying people, as it's just a small part of the application process and not free work for us.

I think it's worked pretty well so far. It happens after the initial phone screen and before the first technical interview. We send people the challenge, they return it whenever they want, and if we like it we set up a technical interview. Since the challenge uses our tech stack and is similar to the work we actually do, a large part of the first technical interview is discussing their solution. Why they chose certain patterns, why they added a certain library, how they'd consider testing it, why a certain function might be slow with 10k entities, and so on.

Re:Hiring Without Whiteboards by azangru on Wednesday July 29, 2020 @08:34AM (#23985925)
I would feel bad about it.

You don't normally pay candidates for the time they spend doing the whiteboard interview, do you? You can view the take-home task as a replacement of the whiteboarding session, equally with no pecuniary obligations for the candidate.

Re:Hiring Without Whiteboards by cutemonster on Thursday July 30, 2020 @06:00PM (#24003326)
Another thing, what if it seems some people just want the money, and didn't try seriously

Then what? Would it feel good to pay

Re:Hiring Without Whiteboards by GordonS on Wednesday July 29, 2020 @12:45PM (#23988789)
Do you have a few examples of tasks you assigned? I struggle to come up with tasks that I think have the right level of complexity, but which can also be completed in a reasonable amount of time.
Re:Hiring Without Whiteboards by naavis on Wednesday July 29, 2020 @12:44AM (#23983581)
Do you have some kind of a screening process before the first interview?
Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @01:21AM (#23983724)
Typically an introductory phone call: ‘is this the kind of job you’d be interested in.’ Maybe that’s step 0.
Re:Hiring Without Whiteboards by quantified on Wednesday July 29, 2020 @10:16AM (#23986892)
Much better thought out than any I have performed in on either side. Thank you for sharing, this would be a good template for others who need one to follow (which many do). You also hiring?
Re:Hiring Without Whiteboards by victor9000 on Wednesday July 29, 2020 @12:33AM (#23983542)
This sounds like a pretty reasonable process, are you guys hiring?
Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @12:36AM (#23983551)
Digital Dynamics, a small company in Scotts Valley, Ca. We make specialty industrial control computers.
Re:Hiring Without Whiteboards by pythonbase on Wednesday July 29, 2020 @01:20AM (#23983721)
Great approach. How do you shortlist candidates for the first step?
Re:Hiring Without Whiteboards by 11thEarlOfMar on Wednesday July 29, 2020 @01:22AM (#23983732)
Resumes & phone calls if they look interesting.