13 ms·
John Carmack on Hiring
- boplicity 5y ago> Hiring is an obvious example, with "requirements" that filter out large chunks of applicants that don't have some kind of back channel In my experience, it is very tempting to filter for the most qualified candidates, and that should happen. However, there should also be a filter for the most dedicated candidates, as that can also lead to very good outcomes. Many of the best employees don't look that great on paper, but love their jobs, and are very motivated to excel. The same is not always true, at all, for "qualified" people.
- jimbob45 5y agoMy old company used to hire broke, desperate, and underachieving college students out of the local university for that exact reason - desperate people are often the most dedicated people. The scheme worked something like how the New England Patriots run things: keep a solid core of veterans well-paid and happy, then use them to train the hell out of new hires. Later, make sure those new hires get excellent jobs elsewhere in 4-6 years and repeat the cycle, ensuring that you never have to pay for premium talent since you can develop it at budget cost in-house. When I say "train the hell out of", I mean each new dev had a senior dev dedicated to just them who would criticize everything about their code and workmanship like a Mr. Miyagi. Every email that dev sent also got CC'd to that senior dev and the senior dev always knew what they were working on, how long such a thing should take them, and knew what questions/difficulties were likely to come up and when during the process of that item. Good mentorship cannot be substituted for during the training process. The system fell apart once management got flipped and forgot what made them successful in the first place.
- nickstinemates 5y agoSounds like the traditional trades system applied to tech.
- walshemj 5y agoMore like an advanced apprenticeships where like me you'd be doing 1 day a week and possibly an evening at community collage and that is in my case was a four year. The trouble is the cohort that would be ideal candidates now go to university as those roles are now degree entry.
- imbnwa 5y agoGods I wish I'd started my career at your company
- oblak 5y agoBefore or after the whole thing fell apart?
- imbnwa 5y agoBefore, mentoring was something that was only present when I started for less than a year but I could've used a more persistent program like this, I think, to help rectify a number of long-standing problems I'm only now starting to perceive and take action for much later.
- pkaye 5y ago> When I say "train the hell out of", I mean each new dev had a senior dev dedicated to just them who would criticize everything about their code and workmanship like a Mr. Miyagi. The management should also be aware that senior dev productivity will also go down in order to train the junior devs. Schedules should be adjusted to accommodate this.
- MattGaiser 5y agoThat is impressive actually.
- bennysomething 5y agoHow do you keep a senior Dev happy whos cc d in on every email a junior sends?
- sleepybrett 5y agoI've seen places where the juniors don't even really send email. They are essentially apprentices for their senior in like the medieval blacksmithing tradition. Working the bellows while the senior pounds out the sword. Eventually they graduate up but at first they aren't really trusted with anything but the most basic tasks.
- shultays 5y agoExpecting a new graduate/junior to stay at the same (probably his first) company for 4-6 years seems a bit optimistic. The companies often pay shit to such people and even if they excel at what they do, that additional +X% performance impact on their salary will barely matter if their starting salary was shit. Often job hopping is needed for any significant bump.
- disgruntledphd2 5y agoWell this approach doesn't work unless you actually promote people once they're no longer junior. In my time at a FAANG, I got a 33% pay rise nine months in along with a promotion. That kind of behaviour engenders a lot more loyalty than CPI adjusted raises when an employee is clearly killing it.
- emptysongglass 5y agoThat sounds awful for the morale of the juniors. Juniors should feel empowered to take their own initiative and find their own groove. Having trust put in me when I was a greenhorn made all the difference to my verve and drive at the company. The times where I was castigated and hounded over every little style choice made me loathe the company and the senior doing it.
- MattGaiser 5y agoWouldn't dedicated candidates generally hit up someone on LinkedIn to get put into the backchannel? Heck, people on HN have generously offered to put me into their company backchannel, so it doesn't seem to hard to get into it if you really want it.
- oblak 5y agoNever done this myself and I find the very notion off putting and dangerous. Sounds like diet nepotism to me.
- wayoutthere 5y agoEnjoy missing out on the good opportunities then; most don’t even hit the job sites before they’re filled.
- dghlsakjg 5y agoI think a lot of it is cultural or learned. It doesn’t occur to some people that you can do things like reach out on LinkedIn or do things beyond just checking the careers page. I read about people who fill out hundreds of applications and never get a response. I know it’s a numbers game, but that is absolutely wild the amount of effort people put into a strategy that clearly isn’t working.
- MattGaiser 5y agoRandom applications are working great for me too. I just do the inside track for really interesting roles.
- the_only_law 5y agoWhat’s the chance that me hitting up some rando on LinkedIn isn’t just gonna result in them ignoring the connection or telling me just to line up at the front door.
- MattGaiser 5y ago
- zz865 5y agoAdd to the list that the people who are best on paper and are good at interviewing will probably be looking for a new job in a year and/or when things get tough.
- atirip 5y agoWe always look for “rough diamonds”. It is a creative process, lots of tea leaves reading, but will yield excellent results if you have the ability to read these tea leaves. I am not sure we ever hired “the best on paper” candidate. But we have had great success with people who had no knowledge of out stack, down to the programming language.
- BackBlast 5y agoI've always thought that there is undue emphasis on the tech stack and the language. I've always felt that filtering for raw engineering ability, thinking prowess, and attitude would get you farther in the long run.
- nnevod 5y agoWhile I tend to agree, there's obviously jobs where familiarity with stack, tools and best practices is more important than engineering ability. They may not be interesting, but they do seem to comprise the majority of openly availible jobs. My current job has minimum emphasis on language (C#, targeting original Framework 2.0, no new features) and zero tech stack. On the one hand it is interesting - not enterprise stuff - and puts the brain to real use often, on the other, I think it doesn't provide anything market worthy to my CV. As most of my collegaues work for over 7 years there, it really seems to be so.
- BackBlast 5y agoIf you don't mind humoring me. What kind of slot is better for a plodding dev who checks all the tech boxes?
- sneak 5y agoWhat do you mean specifically by reading tea leaves? What things do you seek out and what things are disqualifiers? How do you know that your style of tea leaf reading is effective? ngl, the way you describe it makes it sound super cargo-culty, but if there is something more to it I'd love to hear it.
- WhompingWindows 5y agoHow do you determine who is a dedicated job applicant? First, everyone shoots their resume and maybe cover letter into your black hole. Are the dedicated ones the ones who actually included a cover letter? Or is it how enthused/personalized the cover letter seems? A qualified individual should do that, perhaps even better since they have experience and talent, if they're indeed qualified. Next, they have to go through interviews. Are they expected to fully research the company and its methods before the initial round? Or how about coding questions: Would you take someone who spent 3X the time on leetcode but only got 50% as many coding answers as the qualified person? Do you purposefully choose those who you deemed "worked harder" or "wanted it more"? Are things like follow-up emails, thank you's, further reflections, are these things how you determine dedication? Or do you purposefully over-look those you think are well qualified, ruling them out in favor of those "trying harder"?
- boplicity 5y agoNo, we don't do any of that. We have a variety of low-commitment projects that we pay people to do. These projects add value to the company, of course, but they also allow us to get to know a variety of people who can become more involved with us. In other words, we've found ways to take risks on people, and get to know them, without hiring them outright. We hope to hire them, but they still do need to go through our filtering system first. It may not work in other fields, but it works well in the field we're in. Of course, we also have a more traditional path, including resumes, interviews, etc. It's good to have multiple methods for finding employees, IMO.
- HWR_14 5y agoDo your low commitment projects actually pay a reasonable amount?
- fb03 5y agoThey usually pay the standard rate that would be applied for the expected amount of hours of completion of that task, with a small plus. this way, even if you don't land the job you still don't get out of it feeling like you lost invaluable time of your life. But in my own experience I have once worked for free on those tasks, hoping to get hired, and when it didn't pan out it made me a bit sour. Won't do that again.
- k__ 5y agoIn my experience "dedicated" means "put up with our BS"
- boplicity 5y agoI think it's a matter of how a company is run. Some like to exploit their employees, while others value them, and want them to be happy for the long term. In the long run, my hope is that the people we work with will believe they're getting the better end of the deal, and that (if they're employees), they are given stability and support for the long term. It's a matter of respect, responsibility, and commitment.
- JohnWhigham 5y agoDedicated here sounds like coded language for "will work the longest hours"
- paxys 5y agoAgree with this, but the thread doesn't really add anything to the discussion other than "hiring is a hard problem for both sides". People should upvote based on content, not the profile of the author.
- ericsoderstrom 5y agoI think the interesting addition is his point that adding some amount of literal randomness to stages of the process would be a good thing, if the culture around interviewing could change to accept it
- hhmc 5y agoI think he's specifically alluding to doing something like Bayesian exploration/exploitation -- which would be very interesting. Unfortunately, you'd need to hire at huge scale to assess the outcome of the experiment, and - as he mentions - it would be hard to get hiring departments to accept.
- sharken 5y agoI much prefer the approach also mentioned in that thread. Here a hiring process was adjusted so that good current employees could actually pass the hiring process. Of course that doesn't solve the issue on how to get the first few hires.
- deleted 5y ago[deleted]
- aynyc 5y agoWhen I was interviewing for a job, I complain about potential employers with their craziness. When I was interviewing to fill a job, I complain about potential employees with their craziness. Edit: I don't have a solution. I have all but given on the traditional method of applying for jobs via websites. Fortunately, I have enough network to help with my referrals and recruiters have been calling.
- briffle 5y agoI've been on both, but I also realize companies putting out a list of almost silly requirements that just about no person ever could meet has made many people 'stretch' their qualifcations too.. I have programmed against and Oracle DB becomes Oracle DBA experience, etc. Because when you do want an actual DBA that has a bit of programming background, you get so many applications for the first type. Additionally, things like a Linux Systems Administrator can come in many different strenghts, and your going to attract a different level of skill by posting your salary range as 60-80k, than if you post 120-140k. But many employers don't want to post it at all, and then it seems you only get the low end guys applying.
- artful-hacker 5y agoOne of the few actually useful functions recruiting companies can do is get the job salary range in agreement with the candidates desires before wasting anybody's time.
- wayoutthere 5y agoI too have found applying for jobs via web sites to be a complete waste of time. Every job I’ve gotten in the past 20 years was either through a personal contact or a recruiter who reached out and contacted me based on my LinkedIn.
- sharken 5y agoMy experience exactly, it was only after actually calling a company about a job that everything clicked. Sending an application using a recruitment website is like buying a lottery ticket with the same poor chance of winning. And the easiest way to get a job offer is to know someone within the company that can recommend you.
- colonwqbang 5y agoThis is pretty vague, doesn't really say much about anything.
- jstx1 5y agoThis is a long and polite way to acknowledge the UnderdogDevs group and not say much else. Companies have a very strong incentive to miminise the false positive rate and the tradeoffs that they make there mean that they increase the false negatives because the cost of a bad hire is so much higher than the cost on missing out on someone good. In other words they're optimising for precision. I don't know how you start helping these disadvantaged groups without taking on a lot more risk and higher cost.
- boplicity 5y agoThe risk of hiring mediocre people who don't really care is invisible. Eventually, it becomes part of the fabric of the company, and the result, of course, is obvious. I suppose most large organizations can handle this particular risk because they've lucked onto a large cash-cow, such Google's ad-dominance.
- JamesBarney 5y ago> because the cost of a bad hire is so much higher than the cost on missing out on someone good Is this true? Organizations I've been a part of the best hires were game changing for the company, and the worst hires just got fired after 6 months.
- the_gipsy 5y agoI see only really, really bad hires getting fired, after a year or so. Simply mediocre people are not fired, and don’t leave by themselves.
- Dudeman112 5y agoUnless you are paying a premium (and need exceptional employees), getting mediocre people qualifies them for being a good hire. So those people not leaving is a good thing.
- PragmaticPulp 5y agoYes, it’s true. Even if you remove the bad hires after six months, that’s six months of wasted mentoring effort and six months of of not being able to fill that position with someone who can do better. That’s also six months that the bad hire’s coworkers have to put up with a bad employee on their team. They’re going to wonder if bad hires are the new norm and take it as a sign that it’s time for them to move on. Bad hires have a lot of ripple effects. Most employees aren’t isolated islands within a company. Their coworkers suffer the most.
- swman 5y agoIf you want to actually empower people, just do it. These companies have billions in cash reserves. If you don’t want to wire me that money, then at lease use it to set up A shadowing program for ex cons to spend a month with one your engineering teams. See how software gets built, and also be a part of it asking questions and hanging out with the team. Create programs that train adults to perform various jobs that are open. For example, many people would be willing to do any job at a tech company - it’s a booming industry. Why not have a pipeline for people to enroll to learn how to be a BDR, customer service, test engineer, etc. that results in them being placed at a job? Or seriously give me the money and I’ll help set it up for you. All these people and companies talking about this stuff is annoying. Y’all are smart and resourceful so just do it and show us.
- AceJohnny2 5y agoCompanies that have these kind of resources are hamstrung by process and budgets and review meetings to prevent fraud and abuses. Companies that have these kind of resources and aren't hamstrung are ripe with fraud and abuses.
- swman 5y agoEither way, excuses.
- aliswe 5y agowhat's this rambling ... you go and call them up instead and tell them all about it. and BTW, it's not about them having billions in reserves (idk why but I hate this phrase - maybe because I grew up hearing it), it's a legitimate requirement for them to hire more people if they want to expand.
- kator 5y agoI have always focused on hiring for attitude and aptitude. If you have the attitude to learn, and the aptitude to grown your skills, then you'll do great at anything you're passionate about. I literally hired a guy who was a part-time computer hobbyist but, a full time pool man. I told him "hey how would you like to spend 40 hours a week learning more about computers." Today he's working as a leader in his company's security group. He often thanks me for the job, and I always remind him "you did the work, all I did was give you the opportunity". Sadly as stated in the thread linked, its hard when you have 10k applicants, to treat each as a potentially amazing member of the your team. I still try hard to look for that attitude and aptitude, and if a candidate demonstrates this in our dialog, I will do my best to find a path for them to connect with other opportunities if they're not a strong match for roles I'm filling on my teams. What I know is we're born to this world knowing how to eat, breathe, cry, and a couple other things. The rest, all of it, we've learned on our way to this day. Just because the person in front of me didn't have the same path as me, doesn't mean they won't learn to have an incredible impact going forward. Searching for this potential and type of partnership at scale is hard. My heart wants to say it can be solved, but my calendar is an evil overlord that only allows me only so many hours a day to invest in growing my teams...
- jstx1 5y agoYou have a bright career as a LinkedIn influencer ahead of you.
- nickff 5y ago>" You have a bright career as a LinkedIn influencer ahead of you. " I am not sure exactly what you meant to say, but this came off as a bit snide (to me).
- pc86 5y agoLinkedIn is full of completely farcical stories about recruiters who had the prescience to hire someone even though they were 30 seconds late for an interview or didn't wear a tie or hadn't graduated from an Ivy League school or some other such nonsense. And because of this HR drone's largesse, this person later did their job satisfactorily. I honestly can't tell if the GP meant it in a snide way (like my example above) or as an honest compliment. It could be either, really.
- alberth 5y agoI wonder how folks will compare Carmack's views to hiring, with how Google hire's (only top school with top grades).
- deleted 5y ago[deleted]
- autotune 5y agoThat’s how Google hired before introducing LeetCode to the process, from my understanding.
- hwers 5y agoI feel like this is going to blow up into a thread with a ton of comments about peoples own personal opinions on hiring - while the actual content of this tweet thread barely flesh much out about the topic.
- EricRiese 5y agoWSJ just posted a story about this yesterday: https://www.wsj.com/articles/companies-need-more-workers-why-do-they-reject-millions-of-resumes-11630728008 https://www.wsj.com/articles/companies-need-more-workers-why... I think a company could do well by teaching HR about game theory: take into account what your competitors are doing for hiring and the best candidates they're skipping over when coming up with your own strategy.
- HPsquared 5y agoI wouldn't mind rolling a D20, it's transparent and honest.
- Zababa 5y agoAs long as we consider 1 the best result and 20 the worse, since my luck often work this way, I'm fine with it.
- walshemj 5y agoLol with my luck this would be like tonight's Rise of the rune lords pathfinder game where my l14 wizard got doppelganged twice. The first doppelganger first critted a disintegrate spell and killed the rogue 200hp dammage The second doppelganger one shoted my character. 50% party kills in one round.
- gfodor 5y agoIf enough state about a person is public and verifiable, then hiring can become algorithmic. As a bonus, if this is publicly disclosed, then the applicant can walk the path to close the gap to be hired at places they wish to work. The catch is capturing and verifying the relevant info. It may not be tractable, to put it mildly. But it’s a useful thought exercise to think about what it would take for such an approach to be sane.
- throwaway9191aa 5y agoHow does one get in touch with this UnderdogDevs group without a twitter account, or otherwise public account? I haven't seen an email address anywhere but am probably just missing it.
- bennysomething 5y agoGenuine question: I don't understand the post, what is he saying? It's something to do with hiring ex prisoners?
- smusamashah 5y agoWhen hiring for senior positions, its probably more easier to rig the system. At the level no one even thinks of checking if someone can code. I worked for someone like that to do their job for them. This person was hired on a 7+ year xp position for a job and only thing they knew is how to answer questions in an interview. I use to get the shared screen from their work computer and use to work for them. My only guess on how they got the job was that the resume was saying so much that no one bothered to ask them to write the code. How do you get a high paying dev job when you can't write method, don't even know what return is? but you have degrees and all that fluff written in your resume. I don't understand.
- Dyac 5y agoHow did the arrangement work between you? Were you full-time helping them? Are you in a poorer country?
- smusamashah 5y agoIt was occasional, I don't have stamina for part time regular job along with day job. Sometimes few days in a row for 1-2 hours a day. And yes, the person I was doing it for was in some corp in US.
- yupper32 5y agoJust a reminder that most requirements on job postings can be ignored. You can still apply and get through pretty often if you don't fit the requirements perfectly. There's almost no downside to applying.
- mywittyname 5y agoIt can be discouraging to apply for jobs and not get even a callback.
- chongli 5y agoThat goes down with volume. If you apply to a large number of jobs then you won't worry about those who didn't call you back because you'll be too busy scheduling and attending interviews. Of course, if you apply to a large number of jobs and don't get any callbacks then that's a strong signal that you either need to update your resume, update your credentials, or seek employment in another field.
- deleted 5y ago[deleted]
- jstx1 5y agoIn turn this gives companies a reason to apply strong filters just so they can reduce their shortlist to a manageable size.
- yupper32 5y agoYup. But at the same time, in the current environment, the person who applies to 100 places will more often be better off than the person who applies to 10 places. If you need a job, you gotta play the game. Mass applying is the current meta game.
- dvogel 5y agoWhile I don't advocate for mass applying, I have always believed that most top candidates for a position will only hit approximately 5/8 desired experience/skills points. As Carmack says in the thread, the labor force simply has a perpetually non-optimal distribution of skills. After seeing it from the hiring side for the past 7 years, I can also say that there's usually a few extra unlisted criteria that would more than substitute for the skills you don't match on. The content of job listings is largely true to the desires of the hiring manager but also incorporates some organizational inertia. It takes a while to get new technologies incorporated into the practices of recruiting offices. Many managers are usually informally hiring for skills that have not yet achieved enough of a foothold to be a screening criteria.
- darth_avocado 5y ago> interviewing prospects is a very non-trivial cost to an organization Yet, a lot of companies would rather not give you that trivial raise to retain you, but spend that non-trivial cost to hire someone else at a higher rate.
- paulryanrogers 5y agoIt's a strange yet common anecdote. I wonder if employers are thinking the grass is always greener on the other side.
- obviouslynotme 5y agoIn my decades experience hiring, there are only three archetypes you want to avoid: - Someone who has no clue. This is rare but it does happen. I have seen some fly through interviews and then literally do nothing until they leave for another company as we are set to fire them. - Assholes. Everyone is nice in the interviews. Not everyone is nice during code review. There is a sub-archetype of asshole called The Complainer. They can live in pairs, but if there is no Assholes, a true Complainer will find a way to turn someone into one. They are two sides of the same coin. - My way or the highway types. Your team uses Design Patterns and Unit Testing. Bob says that is overengineering and refuses to be a team player. Interviews focus on the first one, which is honestly simple for a relatively experienced interviewer to weed out. I don't believe in 10X rockstar ninja programmers. Either someone has the ability or they don't. The real keys to great hiring are good managers and cheap firing. Good managers are hard to come by, but they can be built fairly easily. Cheap firing is usually easy, if that is your goal. Some locales restrict this legally, but there is always a loophole.
- snovv_crash 5y agoFiring is dangerous, it can demoralize the team extremely quickly. My rough rule of thumb is that for anybody who was even marginally liked who gets fired, expect one of your best people to leave. On the other hand, if there is someone who people don't like, who visibly avoids work, and the rest of the team resents them, then firing is actually a really positive thing.
- GiorgioG 5y ago> Firing is dangerous, it can demoralize the team extremely quickly. Conversely, keeping clueless people around is demoralizing and insulting to the people actually doing the work. I don't mean junior folks who get it but are building experience. A company I worked for hired a junior against the advice of the team (red flag anyone?). We spent 6-8 months with this individual spinning their wheels. They just did not get it. It created more work for the rest of the team to help them, redo the work correctly, etc. Did they fire him? Nope...they transferred him to another group within the company. And of course he's not doing well in that group either. Why should people work their butts off if it seemingly makes no difference? I've since left that company - this wasn't the primary driver, there were lots of other supporting reasons, but ultimately it came down to my loss of faith in management's ability to steer us in the right direction.
- ghiculescu 5y agohttps://twitter.com/UnderdogDevs https://twitter.com/UnderdogDevs just links to a youtube channel. Assuming this is basically a pitch for UnderDog Devs... if you want to actually hire UnderDog Devs how do you learn more about that?
- hmahncke 5y ago"just tossing out all the ex-cons is an easy call" - it might be an easy call, but it doesn't mean it's the right thing to do.
- deleted 5y ago[deleted]
- bitwize 5y agoGiven some of the shenanigans Carmack himself got up to back in the day (including B&E), I'm not sure he's saying it's the right thing to do, only an easy, commonly used and widely considered unobjectionable first-level filter.
- breckenedge 5y agoYea that’s what he says in the thread, it’s a negative example. “Thinking about this while considering the challenges that @UnderdogDevs face in trying to help the previously incarcerated into software jobs.” Here’s a link to the Underdog Devs organization: https://www.underdogdevs.org/ https://www.underdogdevs.org/
- hmahncke 5y agoThanks for pointing that out - great to see someone is working on this.
- throwaway9191aa 5y agoIt isn't that easy to do. Anyone advertising their ex-con status is sabotaging themselves. So what signal do they use for every inbound resume? So the company can't just trash the resume. After the interview, if things are moving forward, the candidate can inform the hiring manager of the situation. But if the company doesn't do background checks, they don't ask so you don't tell.
- kennywinker 5y agoBG checks are pretty common in tech, in my limited experience.
- madrox 5y agoThe most influential essay I've ever read on hiring was titled I Don't Hire Unlucky People[1]. At the time, I was struggling to build a mobile dev team, and I could always find reasons to not hire anyone in the pipeline. However, there came a point where I had to apply the secretary problem [2] to my situation and realize it was costing me more to not have these positions filled. To that end, my only hard requirement became whether I left the interview with them feeling like this was someone I could manage and grow. The irony is that once I embraced this, I ended up with a pretty diverse team almost as a side effect. It made me realize that most "unspoken disqualifications" are usually anti-diversity in practice, though I don't think that's done consciously. 1: http://braythwayt.com/posterous/2014/10/04/i-dont-hire-unlucky-people.html http://braythwayt.com/posterous/2014/10/04/i-dont-hire-unluc... 2: https://en.wikipedia.org/wiki/Secretary_problem https://en.wikipedia.org/wiki/Secretary_problem
- wisty 5y agoThe alternative is that you nitpick, and toss out all the ones that don't tick the right boxes. This means you either get people who have good attention to detail, or people who have had plenty of failed iterations to polish their approach.
- madrox 5y agoThat's essentially the point of that essay. That, and most of those boxes you want ticked are artificial means of whittling down candidates and not hard criteria for whether someone can do a job.
- dleslie 5y agoI prefer working with, and hiring, the sort of people that FAANGs would never look at: diverse and weird education or experience be backgrounds, grossly unrelated hobbies, and pressing personal responsibilities like a band, family, or sport. Some of the best programmers I've worked with were ex high school teachers, military, set designers, nurses and such. I _want to believe_ that folks like this trend towards flexibility and teamwork. That they're at work for the purpose of earning, and work with the goal of delivering. They'll collaborate when possible, and cut features when necessary.
- deleted 5y ago[deleted]
- jonny_eh 5y agoSo… willing to be underpaid and work long hours?
- dleslie 5y agoI prefer teams that never/rarely work overtime or weekends, and have fair market compensation.
- ChrisMarshallNY 5y agoThat’s what worked for me (as an employee). I’m a high school dropout, with a GED, and some tech school training (from a now-defunct certificate mill). Not exactly a Stanford Ph.D. When that’s your pedigree, no one gives you a break, so you have to make your own, and prove yourself at every step. Sort of “A Boy Named Sue” thing. It either makes you, or breaks you. Kept me humble, hungry, and a team player. Yeah, I got taken advantage of, but I also found that people would give me incredible opportunity, as I was a lot cheaper than an architect. My very first engineering project was complete hardware and firmware design of a microwave switching device[0]. Almost no one gets that kind of opportunity. Most folks have to wait years before being trusted with much lower levels of responsibility (I had almost no supervision or guidance, during the project). Did I mention that this was my very first engineering project, ever? The only reason I got it, was because I was given the rather humble task of assembling an ATE system, and I was getting tired of constantly stopping the test to rewire the units. My boss got sick of me bitching, and said “Why don’t you do something about it?” So I did. Since he told me to do it, he couldn’t very well prevent me from following through. That’s been the story of my life. People toss me difficult problems, to shut me up, and I solve them. This has not always won me friends. I’ve learned that, quite often, people don’t actually want their problems solved, and get quite upset, when you solve them; even when they asked you to. In the aggregate, it has worked out well. I’ve retired, ten years early (not by choice -thanks, ageism!). [0] https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf https://littlegreenviper.com/TF30194/TF30194-Manual-1987.pdf (downloads a PDF)
- minsc__and__boo 5y agoPeople here are saying that Carmack isn't really saying much (quantity-wise he's not) or giving their own personal anecdotes, but he's touching on information theory for imperfect markets. Basically the employer and candidate screw up the signals to each other about buying/selling of labor today, and it creates costly overhead for both parties. In a perfect market, employers and candidates know everything about each other and quickly fill- or land-in the best possible positions (respectively). Not sure if the startup he's promoting, or throwing in random population sampling, solves this problem though. Seems like the random sampling is only a temporary fix to uncovering missed positive signals in candidates.
- americafails 5y agoAt least you all admit that college is a scam considering you don't hire people based on skill and education. I have never had a job in tech because I have no idea how to communicate skill and passion outside of being good at cramming and faking my knowledge. Since I won't do that, I will most likely never get a job. What a waste of time
- elbasti 5y agoThe best book I've read on hiring is "Who: The A Method for Hiring." It's so good in fact that I feel kind of bad sharing it, almost as if I were giving away a competitive advantage. It makes a very simple point that runs counter to most silicon valley talk about "hire for slope not Y intercept" or "hire hustle" or whatever: Hire people that have the skills necessary for the job that needs to be done. That's it! It sounds simple to the point of ridiculousness, but the truth is that most job descriptions/roles in an organization are written in a lazy way, in which the org has not actually done the work to figure out what specific skills are required by the organization to complete it's mission. So instead, they hire for generalists, or for "people they like" or for people that fit a pattern--all because they haven't actually done the work to figure out what skills are actually needed. Examples. A small startup puts up a job description for "senior ruby engineer." If the org is bottlenecked because they are working on very tricky code they should be interviewing for a very different engineer than if they are bottlenecked because they actually need someone who can ship simple CRUD features fast. "oh, but see we only hire senior engineers because {reasons}." Balderdash! Think about the problems you actually have, the skills and experience required to guarantee (or as close to it) that a candidate can Do The Job, and go.
- UnpossibleJim 5y agoWait, are you saying the STE job I saw at Amazon might not need a master's degree in CS? Preposterous! =P
- BlueDingo 5y agoIn that scenario, is everyone hired on a contract basis? Do good workers get dumped after successful projects simply because the requirement they were desired for is complete? I think companies hire for general skills not just because they aren't clear about goals, but because they're dealing with people. I get why you like the idea but you can't just malloc and delete people, they need some stability. And since the company probably won't be dropping their tech stack with each new project, hiring for knowledge in an area rather than knowledge of a narrower task seems reasonable?
- anon9001 5y agoCorollary: Have your interviewers be experts in the specific are you're trying to hire. If you need a ruby engineer, don't submit them to a generic hiring panel. Have them spend an hour or two talking shop and doing some pair programming with one of your most expert rubyists. Master craftsmen can pick each other out in a second, but a whole hiring panel can fail to spot both bullshit and greatness.
- devwastaken 5y agoRequire government ID, create an org for standardized certification, call it something dumb like "bootstrap certificate", which weeds out all the non programmers. Then you can focus on the remaining that are legitimate candidates. There's more identity requirements and anti spam to a Facebook account than there is in hiring, and in a world of remote work that just doesn't work.
- autarch 5y agohttps://threadreaderapp.com/thread/1435307747470454787.html https://threadreaderapp.com/thread/1435307747470454787.html
- throwaway20371 5y agoWhy doesn't Twitter just make their posts unlimited? People would still write short, terrible, infurating tweets, but they could finally stop these run-on multiple-tweet abominations. Or make an actual blog feature. I know that wouldn't be as "engaging" though.
- dd444fgdfg 5y agounpopular opinion most certainly but we are all part of the problem. if I apply for google right now I'm another one of their 10k applicants today. Google are never going to hire me. The solutions begins with applicants self filtering instead of blasting every company with their resume, then complaining that said companies are unable to scale their recruitment process. Be more honest with yourself before you apply. Are you really qualified. Are you either already at or above the level of everyone they currently employ?
- stereoradonc 5y agoThis is a brilliant thread. I recently got rejected (for a non-tech job) but at the time, I realised what potential employers were seeking. They were keen to have a round peg for their round holes without appreciating the holistic ideas I would have brought on the table. I don't blame them. They are besotted by credentials - like everyone else. Though, from this point of failure, I have learned more about leadership than what an online course could teach me. Even though I exceed their credentials (I am qualified for the job), I didn't let a committee decide my sense of self-worth. I wished them good luck with the search process.
- alexpotato 5y agoThis is a particularly great story from a now defunct blog (hence the pastebin) that talks about how for free training on a technology platform you use extensively can be both good for you and for the people taking the training: https://pastebin.com/raw/QtePMR26 https://pastebin.com/raw/QtePMR26
- P_I_Staker 5y agoHoly shit, I was just thinking the same thing. We were talking about the various things that recruiters use to filter applicants, and they're largely untested, possibly containing unknown bias. You know what's not biased? Random chance. Just try to get down to the bare minimum reqs, then randomly place in a queue. Then you have two options. Either truly random interviews, or the manager gets to pick out of some kind of priority queue. There's still biases here, but we're not introducing any black magic. There are biases in whatever minimum specs you set. If you have the manager select, then you have their biases. Also, it would be hard to manage whatever the specs are, because you're probably not going to hire literally anyone, while maintaining this random strategy (without creating a new "system").