7 ms·
Slightly Less Awful Hiring for Engineering Talent
- afarrell 11y ago> Don’t require a particular language But do indicate language in the nice-to-haves at least. Some programmers find that they work much better with certain tools than others and it is useful to know if you are able to use those tools.
- elwell 11y agoAlso, depending on the language, it should sometimes be a requirement. If you're hiring for a Haskell developer, and you're a startup, you don't have time for a top python engineer to spend 2 months getting up to speed in Haskell.
- wwweston 11y ago> If you're hiring for a Haskell developer, and you're a startup, you don't have time for a top python engineer to spend 2 months getting up to speed in Haskell. I'm curious. Are there projects/organizations anyone can think of that were in this position went on to success? I have a suspicion that by the time an organization gets itself in a position where it needs a dev with niche skills and the need is so urgent that it can't spare even two months to get a top generalist developer up to speed... it's already made some bad decisions that might mean that it's not going to survive. Highly specialized knowledge directly in the product domain is one thing. That's understandable. If what we're talking here is language/stack preference, that's something else.
- wpietri 11y agoYeah. Especially at a startup I think you should be optimizing for engineering growth. A company that a) has very specialized language needs, and b) isn't set up to mentor doesn't sound well set up to grow quickly.
- crdb 11y agoMy experience hiring and working with Haskell developers - and those trying to get up to speed - is that one cannot just "learn Haskell in 2 months" as you might say, pick up Ruby after you already have significant Python, Java and C++ experience. It is however relatively unique to Haskell and similar languages whose paradigm is very different to what most of the market is used to. Everything is an optimization over a number of variables. The upside of Haskell is that (if you make an effort) you get very good people and they don't cost as much because there is comparatively less demand for the language, so even on a greenfield project it makes sense to give it a shot. This is aside from numerous language-specific benefits which have been discussed to death in the never ending language wars. The downside is that only a portion of the self-defined Haskell community can truly be more productive in Haskell than say, Python; and these people have many options and are themselves making trade-offs and optimizing across a variety of variables when picking a job (e.g. interesting machine learning work in Python vs boring CRUD work in Haskell, given the same salary, might rank about the same). If you find these people, if they want to work for you, you get good results. But you're bidding against Google and hedge funds, so you need to find an edge that they cannot take advantage of. For example, I saw almost no CVs with prestigious universities on them, because that's a common filter in prestigious organisations, who tend to miss out on the self-taught talent and the less well ranked alumni; those with "prestigious" CVs wait for organisations to get in touch rather than having to sell themselves. So it's probably a good idea to avoid using university as a filter. One reason there are many Haskell job openings in comparably fragile settings (low budget, bad politics, low stakes etc.) is because in cases where resources are ample (thus allowing for time for senior people to learn a new language or junior people to learn professional software development skills), the risk-taking appetite is less and managers will hedge by going for the popular instead of taking a "Python paradox"/blub bet. A cynical reason for this might also be that you do not want to be dependent on a small number of talented people - having a large team of replaceable junior talent hedges against the developers acquiring strong negotiating power by virtue of adding too much value, or even just the risk that a car crash wipes out half your codebase. In some ways the survivability of the organisation in the low-resource setting is then dependent on the Haskeller - if you help your employer increase its conversion rate or customer lifetime value 10-fold, or reduce dev ops and infrastucture cost by a factor of 10, you might well change the very dynamics of the business and justify your team and salary; so it might make sense to take a less attractive posting if you know this is a possibility. At the same time, there are numerous companies arguing this to try and get you to accept a pay cut.
- wpietri 11y agoDefinitely. My goal was for people to feel informed, but definitely not for them to feel scared off.
- krazydad 11y agoAs someone who is currently job hunting, and freshly familiar with excessively long & arbitrary "requrements" sections and tedious application forms, THANK YOU.
- wpietri 11y agoI'm the author, and I'm glad to discuss!
- jobSeeker2016 11y agoDoes Code for America offer internships?
- wpietri 11y agoI think mostly not, although we did have a few interns from Code2040 this year. We do, however, have the fellowship program: https://www.codeforamerica.org/about/fellowship/ https://www.codeforamerica.org/about/fellowship/ That's a great opportunity for people with a few years experience to stretch themselves, being part of a small team that has a year to research, evolve, and deliver a whole system.
- xigency 11y agoI liked most of the decisions you made and how you addressed the problem of hiring coders. One question, do you think, maybe not in your case but in some situations, that a process like this might be too drawn out or too selective? Recently I spent some time interviewing and jumping between jobs, and compared to the amount of time I spent working at one company, I was spending a lot of time interviewing, preparing for interviews, and applying to companies. Basically, my impression from being a high school programmer was walking in the door, being qualified, and being hired essentially in the same afternoon. After getting through college, it seems to be way more of a contest to win a job. Similarly, I earned an internship at a high-profile company in New York City, which I didn't actually complete due to extenuating circumstances, but the impression I had from the interview and from a few days on the job was that the role was trivially easy and they were somehow scouting the absolutely most qualified and talented programmers in the country, anyway. This might happen to work out but something seems broken in this situation, too.
- wpietri 11y agoAs to being drawn out, I think that I would love to find ways to make it quicker. At startups, where you're basically always hiring, it's easier because you can hire on a rolling basis. At my last company if somebody was eager, they could do all the stages over one or two days and we could quickly make an offer. In this case, though, this team had only one position to fill and hadn't hired together before, so we needed to see a fair number of candidates in a batch so that we could collectively calibrate. That took more time than I wanted. I definitely don't think we were too selective, though. Good developers can quickly improve both a team and a code base. Bad ones can harm both in ways that are expensive to fix. I think a lot of typical selection criteria are bunk (e.g., fancy schools, fancy companies on the resume), and I'm not always looking for amazing technical qualifications. But I definitely think it's worth time to find people who are great fits for the job.
- pjungwir 11y agoThe #1 thing I look for in a job ad is a salary range. I don't see one in the ad he links to, and I don't see any discussion of salary in the article. Without that I won't bother to apply.
- agildehaus 11y agoThen there are employers that hide entirely behind a recruiting agency. Why should I apply if I have little idea who you are and what you do?
- sopooneo 11y agoOr are hidden by a recruiting agency. A lot of agencies will do anything they can to make sure you don't go around them.
- prodigal_erik 11y agoOr employers who don't actually exist, because the agency is secretly trying to collect enough résumés to convince employers to engage them.
- sopooneo 11y agoRight. As I've heard it discussed, they've borrowed the term "honey-potting" for this in an almost exact analogue of how it is done on dating sites.
- wpietri 11y agoI think that's a reasonable heuristic. But I'd still be unlikely to put the salary in the ad. Especially for this position, which was at a non-profit with a strong mission focus, we wanted people who cared about the purpose. People whose first question is, "How much can I make?" have never worked out well for me in mission-oriented environments. When I was working in finance, on the other hand, I likely would have put the salary in if we had enough size and data to give firm salary bands.
- ianamartin 11y agoOne thing I noticed in my most recent job search was that I don't see nearly as many postings for junior and entry level positions as I seem to remember in the past. Seems like everyone is looking for a rockstar or a genius or a code ninja miracle-worker. I'm curious if anyone else sees that trend, or if I'm just making it up. One of the reasons is that several friends of mine have been bugging me for a while to help get them started with code. These are people around my age. Professional musicians from back in the time of my life when that was what I did for a living. There five of them now who have been asking, so I'm finally putting together a structured curriculum and working with them on a regular basis. When we get done in six months or so, they will have some abilities with Linux server administration, databases, Python, C#, web application frameworks, javascript,front end work, version control, and testing. I'll work in some CS theory as we hit appropriate points. Obviously, they will be very green. But they are all incredibly bright, professional, adults. One of them has a master's in Math she got after her Doctorate in music just because she was curious, and another has most of a PhD in Physics. I don't think any of them expect to waltz into a high-powered job after 6 months of me spewing at them. But I think any of them would thrive in a junior position with people around them who had the time and the inclination to do some mentoring. Are those kinds of jobs disappearing? Am I being unrealistic hoping that this could be an option for some of them? What do you think?
- ch4s3 11y agoI seem(anecdotally to be seeing the same).
- tayo42 11y agoI've been passively looking to get out of my troubleshoot Linux job to development. It seems like there is only internships or senior jobs. I guess an anecdote but managers at my company don't hire entry level developers because they don't want to pay what they can ask for and don't want to wait for them to get up to speed.
- stouset 11y agoRegardless of what organizations claim to be looking for, virtually everywhere I've been besides my current position has been staffed to the brim with junior developers, and been in dire need of at least a few people with seniority. The irony is when a senior person does come in, all their recommendations are ignored because they will slow down the pace of development. Which it will, but in exchange for setting a sustainable pace of development. A senior developer might (making numbers up here) crank out 100 lines of code per day, but a junior will crank out 1,000 while solving twice as many business problems. Unfortunately, bug counts seem to scale linearly with code size, so most of the problems you're solving are actually just a direct consequence of the ten-fold increase in bugs in the larger code base. Eventually progress grinds to a complete halt as it becomes too difficult to add business value, and the company enters zombie mode where its death is virtually inevitable, but can still operate for years through additional funding. Sorry, I may have gotten a little off point there.