18 ms·
I spent three months working full time to get a job
- dilemma 10y ago>While I do have some ideas of how to improve the process, I do not have a suggested perfect hiring process. Partially because it is impossible to craft a single process that will work for all roles, for all candidates, for all companies. We need to balance being unbiased and impartial with respecting the experience and background of the candidate. It is relatively easy to do in one-off situations but very hard to do at scale. The thing to do is to remove proxies for competence and intermediary parties. Talk directly to the candidate, about the actual work (don't try to "see how the handle" odd questions). However, this requires decentralization of decision making which reduces control.
- gogopuppygogo 10y agoIt'll be fun to get paid for this time when http://www.joinjune.com http://www.joinjune.com is back online.
- vinceguidry 10y agoI think there's an inherent collective bias against making interviewing and hiring easier because that would make the hiring market more liquid, meaning their best people will be able to more easily find jobs elsewhere.
- yummyfajitas 10y agoNot really - what you describe is a prisoners dilemma. If it gets me good people to defect (make my hiring easier), I win. The world won't copy me so once I hire people, I can still keep them. I don't do this because I don't think I'll get good people.
- vinceguidry 10y agoI said the bias was collective, not individual. Individual Germans may not have thought of themselves as particularly bigoted against Jews, but that didn't stop them from participating in regimes that marginalized them. Most of the people fighting against slavery owned slaves. Jim Crow persisted well into the sixties and it's probable that many of the people against slavery would have been for Jim Crow. It's very possible for the hiring market to be biased against liquidity even when everyone wishes it were easier to hire.
- bitexploder 10y agoI replied to you elsewhere but I did just remember that Google / Apple poaching deal. That isn't even a bias, but outright manipulation at a massive scale that hurt the market more than any bias probably could. I am just wondering where in the hierarchy things like this go vs. subtler market forces you are theorizing.
- vinceguidry 10y agoWell, things evolve over time. Market manipulation would be slavery, while bias is just Jim Crow. The whole world is operating under a biased, ugly regime, it just gets better little by little over time.
- yummyfajitas 10y agoThe market is made up of individuals acting in their own self interest. Why would any individual not make hiring easier if they thought they could gain from it? Note that Jim Crow/Davis Bacon/etc was a legal regime, a "must discriminate" set of laws to prevent people from acting in their own self interest. What such mechanism exists today preventing me from acting in my own interest?
- bitexploder 10y agoSpeaking as a business owner actively hiring... the cost of a mishire is huge. It is difficult to understate mishire costs. This means you have to simply spend a lot of time with candidates. Even then you have a narrow window of time, relative to how long the business and employee have to live with one another, to figure out if it is a match. This means you will say no to a lot of people after investing significant time and effort into them (and them into your business). We owe it to our teams to hire well. If that means making it harder, so be it. Think about if it is easier for the wrong people to slip in under the radar. It can wreck culture and team quick. Most teams and businesses dont spend enough time. In Work Rules (Bock) they found the first four long interviews they did helped a lot at Google. After that interviews added one percent accuracy in judging a hire. It is a hard problem and I think the first and foremost goal in any hiring process that is well developed aims to make good hires the #1 priority. I won't discount your theory of a bias, but I think it is a small influencer if it exists.
- vinceguidry 10y agoIn my experience, hiring is the most political act a company does, meaning individual goals very often take priority over company goals. Well above avoiding mishires, loyalty concerns are paramount in every organization I've worked for. You'd think that they'd treat hiring as the quintessential bet-the-company decision, and operate accordingly, but this simply doesn't happen. Leadership creates policies and procedures designed to introduce opacity in the process with the ostensible goal of avoiding mishires, but the real goal of preserving power.
- bitexploder 10y agoAgree. The best thing a business can do is standardize their hiring practices to weed out intentional and unintentional bias and politics. It is hard, though, but possible. Guess that is why I love working in a small business. We keep it transparent and real. We just want to hack things and work with good people.
- sokoloff 10y ago> the cost of a mishire is huge. Absolutely agree and I'll add that you're shopping in a market for lemons. There are multiple adverse selection criteria against the pool of job seekers. (Excellent engineers are more likely to be retained/less likely to be fired. Excellent engineers are more likely to receive an offer when they do interview. Poor engineers are less likely to be retained, more likely to be fired, less likely to be hired.) In steady state, the applicant pool is of lower overall average quality than the pool of employed engineers.
- danblick 10y agoHow do you measure - measure a job search? https://www.youtube.com/watch?v=hj7LRuusFqo https://www.youtube.com/watch?v=hj7LRuusFqo
- navalsaini 10y agonice
- rguzman 10y ago> Use homework assignments to assess the candidate’s engineering skills while homework problems can be better than in-person interviews, they can also be a lot worse. for one, because they are NOT time-bound. secondly, they are much more difficult to setup and evaluate: do you provide a spec? code to modify? third, asking people to do work for free in order to explore the potential relationship is a big ask. lastly, they are very time-consuming for the company. in grad school i learned the hard way to always ask for in-class exams instead of take-homes :-). time and scope constraints can be favorable both for the company and the candidate. > Enough with the graph traversal problems. the point of asking graph-traversals and similar algorithms questions is not that they are the relevant job skill. it is that they are a way to gain information about the candidate's problem-solving ability in a limited amount of time. unavoidably, these questions test for speed and familiarity along with problem-solving. that makes them a lot less than perfect, but i've generally found them valuable.
- jplasmeier 10y agoThe issue with tricky algorithms questions is that they often become tests of how well you can keep your cool. I've (and I'm sure others have also) bombed relatively easy questions due to nervousness compounding. I've also done much better than expected on other interviews because I remained calm and kept the interview flowing smoothly. This is the real skill under test, IMO. Of course, your ability to solve problems is still important, and a subset of what's being tested. The issue is just that there's a lot of (possibly inherently random) factors that cloud that signal.
- base698 10y agoMy favorite example of this is when an interviewer asked me about an algorithm. In the course of the problem it occurred to me, what I needed was to break down the input integer into two parts--two equal parts that could be multiplied together. I kept referring to these two parts as such. After the interview he said I was clearly weak on math because I didn't know the definition of a square root. Something I did know (10 or so college math courses in linear algebra, calc etc) and was describing, but was at a loss for words.
- u_wot_m8 10y agoFrom what I've seen the best hiring process seems to be Automattic's. They do a short interview over chat then give them a project if they pass the interview where they pay them $25/hr and then evaluate at the end. Minimal time wasted for both parties.
- shawn-butler 10y agoThe 1099 paperwork burden must be a headache.
- agildehaus 10y agoDon't need to file 1099s if under $600.
- theparanoid 10y agoThe only interview experience I've enjoyed was Google. Mostly because the interviewers were relaxed. Silicon Valley fosters a stressful environment.
- oriolid 10y agoFrom the many interviews I have been to, Google was one of the three where I had the feeling that the interviewers had any idea what they were doing.
- mr_tristan 10y agoMy current company used a "homework assignment" and they bought a lot of my trust with it. 1. The "assignment" took me about 4 hours, which they expected and told me off the bat. 2. It involved mostly relevant code with 1-2 wrinkles that were not odd just not everyday sorts of things. For the proceeding interview, I was able to sit with 3-4 engineers for 1-2 hours really just diving into details about my experience and their processes, etc. So if I could offer advice it would be to find a "homework problem" your existing crew could build independently in 4 hours or so. As in you've actually had more than 1 team member attempt the request, and they did it in about 4 hours each. This was actually an interview process I didn't mind. I have 15-ish years of experience doing development. I can spare half a day for a prospect no problem. It was actually kind of fun. 4 hours seems to be a good "sweet spot". You can ask something sufficiently technical and oriented to the daily work without being a bore. And when the interview comes around, you can make sure it's not some ego-bound contest, more of a conversation.
- phamilton 10y agoAdditionally, most of us are more willing to do interview work in our off time. Taking a vacation day to interview is a direct financial investment. Spending a Saturday doing a 4 hour home work is a sacrifice, but doesn't require taking vacation time. Taking an early afternoon off to go talk with 3-4 engineers for 1-2 hours is something that can much more easily fit into ones schedule. EDIT: I want to provide an anecdote around this. If your salary is $150k, it may cost you roughly $400 in gross pay to interview somewhere. Sure, you could take paid vacation, but vacation time is paid out in cash when you leave so it still costs you. Companies with unlimited vacation are a different story.
- pmiller2 10y agoI'd totally go for a 4 hour homework problem, if it got me out of 2-3 hours worth of technical interviews.
- mcbits 10y agoI'd rather do 2-3 hours of technical interviews than 2-3 hours of "revive your most traumatic memory and tell me about it."
- jsemrau 10y ago20,000 emails, 1000 phone calls, 100's of presentations to get your product off the ground. It never stops. *Disclaimer: All numbers are estimates. Product can be something you work on internally for a big company to battle office politics or externally when doing your own thing. Convincing people that what you do is righteous takes time.
- 505 10y ago9 days, 8 hours, and 15 minutes
- johnloeber 10y ago> In the prior 17 years of professional experience, I have never needed to write a graph traversal algorithm. I don't get this. I'm in my early 20s and have professionally implemented graph traversal algorithms at least five times. Graphs are extremely powerful data structures, and if you have them, then you can expect to traverse/search them.
- squaredpants 10y agoIt is also not a trivial thing to do efficiently though. I would much rather use a mature library to represent and traverse graphs than to try and implement a graph traversal algorithm myself. I do have some knowledge on the subject, which allows me to work with the available libraries, but some things are just too complex to implement from scratch in a timely fashion, I believe.
- hex13 10y agoI agree that sometimes the best solution is to use existing library, but I can't agree that traversing graphs is "too complex to implement from scratch in a timely fashion". This very statement reminds me of famous "why can't programmers program" article: https://blog.codinghorror.com/why-cant-programmers-program/ https://blog.codinghorror.com/why-cant-programmers-program/ Programming needs some technical skill anyway. And learning "how to use library X" often takes more time than learning "how to implement algorithm X". Libraries are often bloated, bugged, hard to debug or have terrible API. In these moments basic programming skill set is very useful.
- computerex 10y agoThe premise of open source ecosystems such as node is that reusable libs are tested by the whole community. Don't reinvent the wheel. I am not saying you shouldn't learn graphs/CS topics. But you should absolutely utilize the ecosystem.
- hex13 10y agoI think it goes beyond subjective likes/dislikes. I personally like reinventing the wheel, you personally believe in ecosystem, these are just our beliefs. But I think in the long run everything depends on exact project rather on our wishful thinking. I had experiences when use of library was much better solution than own baked one, but I also had experiences where none of the libraries I had found were quite fitted for the project and many times I just had to throw library and write something from scratch in simple way. > reusable libs are tested by the whole community. reusable libs are often FOR the whole community and not for YOUR project. Ofc sometimes you need exactly what rest of community needs, but sometimes not.
- ploggingdev 10y ago54 companies? That seems very inefficient. I like Triplebytes [1] focused approach to hiring engineers. I think they used to interview candidates to assess their skills rather than depend on whiteboards or resumes. If the candidate passes the interview, they would be connected to relevant companies, take up interviews with the companies and negotiate the offer(s). Now it looks like they changed the process slightly to introduce online coding tests to make it easier to screen more candidates. Edit : As pointed out below, the online coding test is the first step followed by one on one interviews. [1] https://triplebyte.com/ https://triplebyte.com/
- pimlottc 10y agoThey still do one-on-one skills interviewing, the online test is just the first step. It seems like a promising approach!
- amorphid 10y agoI think Triplebyte's initial technical screen is kind of lame. It focuses on solving problems that aren't all that interesting to me, and they start a countdown timer before I've even had a chance to read the problem. It feels like I'm competing against a microwave cooking someone else's dinner.
- ammon 10y agoI'm sorry you did not like our process! For what it's worth, we've tested a bunch of types of questions, and relatively easy questions answered quickly provide the highest accuracy / time ratio. We also cover a bunch of topics (to give everyone a chance to show their strength), so we don't expect everyone to do well on all the questions.
- amorphid 10y agoYeah, I can understand that. I think you'll probably discover in the long run that you eliminate a whole bunch of people who might otherwise be good hires. It's kind of like only doing analysis on how your current customers like your product, while completely ignoring potential customers. And maybe that's for the best. It'd certainly better to build a recruiting tool that serves part of the market well vs. serving none of it well. Here are a few things that kept personally me from completing the screening process (which I was checking out because I was a recruiter, and now I'm a developer): - You don't (or didn't) support Elixir, which is what I've primarily been using for the last 12 months, so I spent a few minutes dusting off the "what's the syntax in Ruby" knowlegde - I'm wasn't emotionally invested into applying, as I don't really know who you'll be connecting me with, and if I want to be challenged, I'll continue working on some personal code (which is what I did) - Not having my glasses with me, and a bit of the ol' ADHD, made reading just a bit harder, so the countdown timer was basically reminding me the entire time that I couldn't read fast enough
- deleted 10y ago[deleted]
- madamelic 10y ago> Interviewing for CTO / VPE > Still getting programming homework interviews Kill me.
- deleted 10y ago[deleted]
- mdip 10y agoWith a homework assignment that is not timed, you let the candidate do her best possible work in her ideal environment, and yes, while a work environment is sometimes chaotic, when she needs to get her work done, she is going to make her environment as perfect as possible. I'd like to second this comment as someone who was recently laid off, did a bunch of interviews[0] and landed a job I'm enjoying very much. The company I picked had a "homework assignment". It wasn't a real project that had any useful purpose to them, which I've seen suggestions about doing[1], but a simple web based app. At first, I was a little less enthusiastic about the approach -- I have GitHub repos and other examples of competency out there -- but as I thought about it, this "test app" was in line with what they were looking for and when they described the approach, I liked it. The first thing they did correctly was provide a basic spec sheet. It wasn't overly specific and I think this was by design. It was basically a CRUD web app, with a statement of "feel free to get creative; do as little or as much as you feel it needs". I provided a self-hosted CRUD app that worked on multiple devices, syncing state between them in real-time, documentation, an installer and everything else that was needed to make it a complete product. Most of that wasn't on the spec sheet, but in line with thinking about the project as "something I'd deliver", those were things I'd consider to make it complete and it also gave me an opportunity to demonstrate competency in different frameworks, provide examples of functional/OOP design and other areas that gave them an adequate look at what I could do. The app, itself, was a really minimal web app that took me a couple of hours to write, but after all of the additions, it landed in at a day and a half or so -- not a terrible amount of work for someone out of work and worth it since I landed the job. Frankly, given the choice between shoulder-surf coding, whiteboard coding[2] and test projects, I'll take the test project. I hate whiteboard interviews and thankfully there were none of those this time around. I've had two whiteboard interviews in the last five years. In one case, I got lucky in that the first algorithm was one I had written into an app I had on a private (personal) BitBucket repo, so I pivoted with "I can marker up your board here or I can show you a good implementation that I did a few weeks ago". We spent the rest of the interview with them asking questions about my choices and that was one of the most enjoyable interviews I've had. I didn't take that job. The other, I didn't get as lucky and actually ended up turning down the job on my way out of the interview room[2]. I agree with the author about having empathy for the job seeker. This empathy, though, works both ways. In my case, I had filled in for a dev team in a pinch -- at the last minute -- to run an interview. They hired the guy on my recommendation and he ended up being a great employee so I was pulled in to most of the interviews for several of the dev teams from that point forward. Never mind that I did development on an ops/security team and didn't work with any of these teams, making whether or not they hired a particular person -- or anyone at all -- of now benefit to anything I was responsible for. As a guy who had an already overbooked week, I didn't enjoy being pulled into these and I really didn't appreciate the massive number of woefully under-qualified candidates or the fact that all of that time was often spent on a great candidate who turned down the job in the end. Because of this, I express thanks at various times during the interview process and specifically mention how grateful I am for the time taken out of their already busy work-life. I was glad for the opportunity to interview at all of the places that chose to interview me so I simply made that known. The cool thing about that is later interviews felt more at-ease with the team as a result[3]. [0] I had quite better luck than the author, but did fewer interviews, and was seeking a position that was right in line with my experience. [1] I like this idea, too, provided compensation is provided -- after all, if you intend to use the product of the work a candidate performs, they're technically a contractor and I wouldn't do work like this for free. [2] I actually do pretty well on my toes -- I'm good at rationalizing out loud, and breaking up the tension with a little humor (to the point that I've been given hints at answers when I was stuck). Despite turning down this job, they made a really good offer to me two weeks later that I declined -- the job itself was in a domain I wasn't excited about, but the whiteboarding didn't help. [3] Felt being the operative word -- these were later interviews which means the team was already more interested in me as a candidate than in the first interview. I also remember the first time a candidate specifically thanked me for the time I spent interviewing him and very likely projected that onto my interviewer. But at the same time, it increased my confidence so if it was all in my head, I'm OK with that. I also feel that it was "the right thing to do".
- rent127389 10y agoHow about ... love?
- bit_logic 10y agoI remember somewhat recently there was a new job site for older engineers. Is there one for companies that don't do the bullshit Google style interview? Something like a noalgorithmdatastructurestechincalinterview.com? It would be great if not doing these kinds of interviews became a hiring advantage for companies and a site like that would help greatly.
- andai 10y agoThis comes to mind https://news.ycombinator.com/item?id=13194074 https://news.ycombinator.com/item?id=13194074 http://tryoldster.com/ http://tryoldster.com/
- coding123 10y agoAnd now that you've posted this article, you can probably choose between 150 different jobs :) (if you wanted to)
- StevePerkins 10y agoI know that "homeworks" aren't very popular on HN or Reddit. However, when job-hunting I have infinitely greater respect for companies who use them, rather than sophomore C.S. whiteboard exercises. As imperfect as ALL technical recruiting styles may be, at least a short coding assignment (i.e. < 4 hrs) is halfway-related to the real world. I have written code against a set of requirements nearly every day of my professional career. Outside of the interview context, I haven't balanced a red-black tree since I was in undergrad over 15 years ago. Frankly, whenever I hear people favoring the latter over the former, I always assume that it's just because they're fresh out of school themselves. Yeah, doing dozens of homework assignments for multiple companies could be a massive time sink. However, I've almost universally felt like I wasted my time when going through the interview process with companies who don't use them. Perhaps my perspective is a bit colored, as I'm far enough along in my career that I can be choosy about which companies I invest time in. I only talk with a dozen or fewer companies in each job search, and so I won't do a 4-hour homework assignment unless I'm already interested in working for you. If I were closer to entry level, and therefore had to go through the process with a hundred companies to land an offer, maybe I'd have a different opinion. Regardless, the original post here is some entrepreneur, writing a small novel about his lengthy process of figuring out which job title to seek at a real company ("CTO"? "VP"? "Architect"? "Principal"?) Of course it took him 200+ hours to get a clue.
- colechristensen 10y agoIf you're not willing to pay me on the order of $100/hr to do your homework, I'm not willing to play your recruitment game. My time is valuable and if an employer isn't willing to give equal effort in the interview process, I'm not interested. Also I'm not particularly interested in a workplace – especially a startup – that insists on this in a recruitment process. It leads to only hiring employees who are willing to play the game which is much more likely to exclude people who want to live lives outside of their job and fosters a culture of obsessive overwork as well as not having the diversity of opinion/demeanor/background/etc. which is valuable in a healthy workplace. If you want to bring me in and spend a day with me talking and working in your office, fine. I won't, however, spend 4-10 hours working on a problem for you while working at the job I already have and doing the rest of life.
- adevine 10y agoRandom question: Did you just hand-cut the svg code for the graph on the left side of the page? I took a quick look through the source code and didn't see any evidence of a specific tool. The reason I ask is that that kind of behavior, where you click on the node and it highlights the paths to that node but grays out everything else, is super useful for complicated architecture diagrams where you want to put a ton of stuff in one diagram, but still be able to see where edges go when you have a big spider web of connections. I've been looking for diagramming software that would create these clickable kinds of diagrams for my company, but haven't found anything that exactly fits the bill (Most tools I've found generate static diagrams, and some mind mapping software I've seen doesn't totally fit the bill, either).
- Drew_ 10y agoHe used D3.js. It produces standard HTML SVG elements which is why it looks handcrafted, but you can see the d3.min.js link at the bottom of the body. D3 is very powerful and can probably be used to do what you want but has a very steep learning curve imo.
- GlennS 10y agoFor web things, I would recommend the combination of dagre (https://github.com/cpettitt/dagre https://github.com/cpettitt/dagre), which will calculate node and edge positions, and d3.js (https://d3js.org/ https://d3js.org/), which you can use to layout your nodes as an SVG. I did some work on something a little bit similar for an EU research project, which you are welcome to take a look at. It's probably not directly applicable, but it may give you some thoughts about what does and doesn't work as a UI: https://github.com/cse-bristol/process-model/ https://github.com/cse-bristol/process-model/ https://tools.smartsteep.eu/process-model/?name=actionplanning https://tools.smartsteep.eu/process-model/?name=actionplanni...
- known 10y agoRelevant, relevant and relevant experience/expertize is needed
- grandalf 10y agoI like to give homework assignments too. It's amazing how many candidates will simply not do it, so it's a great filter.
- donovanm 10y agoThis article does a decent job at capturing the grind that is interviewing in software engineering. The expectations during the interview process are high and only get higher the longer you've been in the industry. I wonder how much of this contributes to burnout?
- lj3 10y agoI don't think the interview process contributes to burnout. That happens after you get the job. But, it does make recovering from a burnout a pain in the ass. You need to catch up with the latest trends and refresh on the basics like algos and DS. On top of all of that studying you need to come up with something to fill that 2-3 year gap in your resume.
- prions 10y agoI'm still breaking into a software job and had a homework problem for a company, with a week deadline. Since I worked full time, I spent the majority of my free time working on this problem. I was happy with my solution, and disappointed when I was rejected. Rejection is fine, but what upset me more was radio silence when asking for any feedback on my solution. As a young engineer it would have been amazing to get feedback from professionals.
- hackinthebochs 10y agoThis is exactly why HW problems without any commitment by the employer is plainly exploitation.
- ryandrake 10y ago> If you don’t fit their mold (“We need a Javascript engineer with 5 years of experience writing full stack consumer-focused applications.”), they won’t know what to do with you This is the truth and it hurts. Take a company with 20 job openings, each of which you are probably semi-qualified for, and could see yourself doing. As a candidate, you're limited to applying for one of them, and if you strike out, you're back to square one--often below square one because companies make you wait N months before applying again. I'd love it if a company were to say, "Hey we're going to pass on you for this job in Division X but you know you're smart and Division Y's role is a MUCH better fit for you--why don't we hire you for that?" I've never seen this happen in my life. Try talking to any company's recruiter and say, "You know, I specifically want to work for your company but am not sure what the right role is. Why don't we do an interview and then determine where the best fit is" and watch their brains explode. Nobody does it that way, but wouldn't it be so much better?
- madamelic 10y ago>I'd love it if a company were to say, "Hey we're going to pass on you for this job in Division X but you know you're smart and Division Y's role is a MUCH better fit for you--why don't we hire you for that?" I've never seen this happen in my life. I've had it happen twice (almost 3). I just find a company, look through the listings, find a job I like then send an email explaining my qualifications and my interest. I think it works well if the company is small and roles are fairly undefined ("You aren't an exact fit for this, but we want your skills for something else")
- seanp2k2 10y agoI've also seen this happen a few times, and it's happened to a few of my friends as well. Google does it a bit differently and makes you pass their gauntlet of interviews to ensure that you're totally overqualified for any position you end up in. Once you get hired there, they find a spot for you, but many many engineers there are super overqualified for what they end up doing. They end up turning away many qualified engineers because they're Google and have enough applicants anyway. If you're not Google or Apple or Facebook, you probably can't afford to do the same thing.
- pfarnsworth 10y agoFYI Unreadable on Chrome, at least for me. The SVG graphic takes up around half of the text.
- desdiv 10y agoFWIW that's the intended presentation, so it's not a browser issue. They're trying to be "artsy" with the huge ass interactive chart. I tried zooming in, but even just 110% zoom breaks the text.
- manish_gill 10y agoHomework assignments suck. I was once asked to basically create a clone of Yelp in a week (during which I was working full time). I would rather take a full day off and go interview on whiteboards - come at me, algorithms. What I do not have time for, is setting up an entirely new project and work on it in my space time to impress one dude that will be useless in a few days. Edit: Why are people scared of whiteboards interviews so much? Don't you use them every day to map thoughts out, working with your colleagues etc etc? I'm not saying some questions are (used to be) absurd - the Google/MSFT manhole thing. But why is it so scary to talk about a linked list, a graph traversal algorithm etc? Most of this is stuff that's taught in basic CS classes. Sorry to sound condescending but it almost feels like that as technology spreads and more and more people come into the field who haven't actually studied proper CS, they're blaming the system instead of trying to learn.
- navalsaini 10y agoOne forgets most of that stuff over years in the industry. They are not difficult to remember either or solve in real time - but it does require practice for achieving consistency. Only having to revise them for an interview is really a waste of time. Let me elaborate with an real life example - programming challenges that require graph traversal and other approaches. If I give one after preparing and revising for few hours over 1-2 days, I can solve all 3-4 questions in an hour. If I revise for one or two hours, I am likely to solve 3, but maybe falter on the 4th. I am the same person in both the cases. Maybe that elaborates the problem and disgruntlement - it pisses me when I pass some and get rejected in another. There is no consistency in the test. :)
- lettersdigits 10y ago> I was once asked to basically create a clone of Yelp in a week That's just unfair, inconsiderate and unsustainable, and is also a red flag (ie: I would not go to that company). Giving up a week of your life for an interview ? and for free ? And most importantly - what if ALL companies did this ? you would have to spend months working from home, for free, just to get to the next level of the hiring process . I don't know what the solution IS, but I know for sure that it IS NOT a 1-week work-from-home-for-free task . (edit:formatting and some grammar) Edit2: people will actually pay good money for a yelp (or craigslist/etc/etc) clone on places like upwork. And they asked you to do it for free .
- sumanthvepa 10y agoThe problem I have with giving homework assignments, at least with junior candidates in India, is that very often they just cheat. In one case, the candidate had his college instructor help him answer the questions over the phone, and do the homework assignment. When we brought the candidate in, it took about all of 30sec to realize that the person who had solved the problems over the phone and the person attending the interview were not the same.
- lukejduncan 10y agoIf you've spent 17 years in industry and haven't written a graph traversal algorithm... you probably don't recognize when you're writting a graph traversal algorithm.
- uptownfunk 10y agoThe interview needs to assess skills that will be used in the job. While I can appreciate the spirit of the homework assignment, our role requires client-facing capabilities. With that comes the necessity of being able to answer questions on-the-spot. Sometimes we have meetings with C-level executives with whom we can only get time once every month or every six weeks, and if something happens to come up in one of those meetings, "I'll get back to you in four hours" is rarely an acceptable answer. I think what would really help transform the hiring process is to assess skills that would be required on the job. I think that was the spirit of the original submission here, but I just wanted to explicitly state that I don't think homework is the solution to remedying the current state of hiring in all cases insofar as actually assessing the skills that would be required on the job.
- lettersdigits 10y ago> Hours spent talking: 224 > Hours doing homeworks: 33 I would prefer this to be the opposite: more homework, less talking . That's what the job is going to be like, anyway .. (edit:Formatting)
- GoToRO 10y agoAt my company they do a technical test for an hour followed by a technical interview. It's like an exam. The test is decisive. I prefer this kind of tests, as they only require an hour of effort, and they are objective. All the time a technical test was involved I received a quick and good offer. When I had to convince them about my skills just by talking I either got no offer or I got an offer that was way to low for my experience (like half or worse). As an example, the hardest problem in the test was a C function that receives two parameters, one by value, another by reference, and it did some modifications to those parameters. The problem was further complicated by having two global variables with the exact same names as the parameters that were used to call the function but with the variables switched (global a went to parameter b, global b went in parameter a). At the end they asked what's the value of global a, b?
- killbrad 10y agoThe tldr is: "I wanted a lofty title and a very specific role at some future company. It took a long time and hard work. That's not good for some reason, which I won't go into here."
- tyingq 10y agoHmm. The author says: "I found the process to be dehumanizing, stressful, chaotic, inaccurate, opaque..." Then goes on to talk about pigeon holing, other issues, and some suggestions. You could criticize his conclusions or suggestions, but I don't see how you would summarize it as "not good for some reason which I won't go into here".
- djhworld 10y agoI've interviewed with one of the "big 4" before, their interview process was very structured and very gruelling. Didn't get the job, feedback was that I wouldn't even meet their junior developer criteria. I'm not bitter about it, just crossed it off as a learning experience and moved on, but every time I see one of these articles about interviewing for tech roles, I'm constantly wondering what the best process is. The big 4 tend to hire the best they can get, and have enough applications to pick from a wide talent pool so can afford to spend time doing whiteboard interviews etc, but for other organisations? I'm not so sure.
- daodedickinson 10y agoI wish I could get a job someday. I have degrees and great grades and would love to work for so many places but I find the job application process so soul crushing and inhumane and lonely that I've never gotten through it to a job. I don't really think the process is evil or anything, I just have had a lot of emotional trauma so it does not work for me because I can't handle rejection like that. I just wish there was a company where I could go there and work for free for a few months and if I was able to help out then I can stay. Even if I got rejected then, at least I would see what work was like and how to get better and it wouldn't be cramming a bunch of stuff to get through one of these torture gauntlets. AI makes me so intimidated and depressed and I spend a lot of time worried that I will never be able to get a job because I can't keep up with how fast things are progressing. I really really want a job so I can move out of my parent's basement and I would like to go on a date someday and have someone to love and be loved by. Does anyone know a way for high functioning people with developmental disorders to get to where they can have a job? I admit I don't have a lot of intrinsic motivation for technology because it's ultimately nonsense to have a such a thing. Technology is means of achieving goals, not a goal in itself, so I don't believe in technology for its own sake, I just wish there was something that an employer wanted me to do for them but I can't motivate myself to do something useless. I want a job so I can then be able to afford friends and a family, and wish I could find a job it's just that I'm so depressed about my chances that I'm paralyzed. To me the statistic that matters, the real measure of quality of life, is seen in how fewer and fewer people have close friends and I understand how Facebook, automation, etc. are driving that so I am torn between trying to fight my way to where at least I can be on top of the machine rather than under it and by empathy for the way spirits are being destroyed underneath that machine and the material "wealth" or "stuff" it is producing is not a trade that I can begin to find worthwhile even if I try to fake it so until I make it so. Siiiiiiigh. Are any of you problem solvers? Can you help me at all? It is as from Perlin's foreword to SICP: "The computers are never large enough or fast enough. Each breakthrough in hardware technology leads to more massive programming enterprises, new organizational principles, and an enrichment of abstract models. Every reader should ask himself periodically ``Toward what end, toward what end?'' -- but do not ask it too often lest you pass up the fun of programming for the constipation of bittersweet philosophy." I am stuck in this constipation, because I feel lonely, and I feel the computer is driving us to lonelier and lonelier ends, and, as much as I feel terrible hatred at my lack of employment, I would rather play with you than work with you if our work really is making the world lonelier and more and more dependent on anti-depressants to make up for how we have somehow missed something precious, perhaps glimpsed by Harry Harlow, in our mad dash to try to replace terrycloth and humble fare with wire mesh and our cornucopia of junk.
- js8 10y agoIt's only going to get worse. As automation continues, jobs are going to be less about "being efficient and useful to society" and more about "proving other humans that you deserve to get money". And interviews are one manifestation of the latter. I think SWE as a profession is in a little bit of denial, because we honestly (want to) believe we are being efficient. But the reality probably is that most SW companies don't do very useful work, but rather, struggling to make ends meet, are fighting tooth and nail to prove (often through deception and introducing complexity) that somebody needs their software. And this of course in turn affects the workers in these companies. So SWEs will have to admit (mostly like everybody else) that it is actually a game of musical chairs, and if they don't want this game to happen in this fashion, they will have to institute some other way to play this game (of proving that you are useful), for example, by having a profession association and a profession exam. Think about it. If there would really be that much work to be done in SWE, the companies would just take everybody. But they don't, they are more and more picky. There have been other articles linked from HN (such as http://spectrum.ieee.org/at-work/education/the-stem-crisis-is-a-myth http://spectrum.ieee.org/at-work/education/the-stem-crisis-i...) that say the same thing.
- throw2016 10y agoI think there will always be mistakes in hiring. There is no way to tell perfectly from a set of interactions however much one can wish. We are unpredictable, some are great at deception, we have massive mood swings and phases where we are not at our best, we can deteriorate rapidly and get distracted. What is supposed to be a stable reflection is our education degrees and experience and ideally coupled with a few conversations this should be enough. The problem here is companies have convinced themselves they can find the perfect candidate for every hire and pursue this unicorn relentlessly. Even with all the ado they will frequently get it wrong. It would be more mature and productive to loosen up and deal with the risks than subject everyone to the kind of process.
- macspoofing 10y ago>Use homework assignments to assess the candidate’s engineering skills That could be abused. If the assignment takes longer than, say, an hour - it's unfair to have someone waste their time, especially if every prospective job has one too.
- jondubois 10y agoI also went through something similar over the past month looking for work. My main problem was that a lot of startups tried to lure me into their teams by offering a really senior technical management role, then once I had passed all the technical tests, the role ended up being 'senior engineer' (or similar) even though they said they were extremely happy with my test results and interviews. It's clear to me that they had never intended to offer the senior position and just used it as bait. Other times, they said I would be interviewing with the CEO but when I got there, they put me through some standard recruitment process and I didn't even see the CEO. This destroys the startup's credibility in my eyes. I cannot work for liars. Making me do all these tests before telling me what I was really applying for shows that they completely disregarded the value of my time.
- user5994461 10y agoSurprised noone commented on the layout of that website? These unaligned 3 screens-long pictures with sections all over the place is a mess. I can't tell if the layout is just weird on purpose? the site is buggy? or adblock/noscript are screwing something?
- bane 10y agoA few years ago I decided to leave my job, I was secure but unhappy with the company, so I took some time to try to find a good fit. Looking for a new job wasn't a full-time affair, but I'd say I spent about 10 hours a week on it. I didn't collect metrics like this, but it took about a year and something north of 170 applications/reachouts. I received zero direct rejections. Probably actually talked to about 15 different companies. Phone interviewed with 3 or 4 and interviewed directly with 2. I ended up not getting any of those positions. But I don't feel bad about it, the positions where I made it to the interview rounds weren't even the ones I applied to within those companies. Both of the interviews were friendly, but almost entirely pointless and were non-representative of what I would have likely been doing there anyway. Finally, after really wanting to leave, I just did the time honored thing of asking a few friends who worked at places I was interested in if they'd refer me. Two places said they'd like to talk, and I work at one of them now. This process took about 3 weeks and I ended up in as near a perfect fit as you can get. Side-effect, after working at this new place for a couple years, those friends I asked, keep popping up every once in a while to see if I'd be interested in something where they currently work...so they've kept in mind that I both: - switch jobs - thought of them when I was looking to do it I'm not a developer, I'm much more into Technical Project/Program Management, so YMMV, but I also noticed that the hiring processes for people like me have almost no steam behind them. Most companies tried real hard to fit me into developer or engineer pipelines, they had almost no ability to entertain anybody outside of that kind of hiring experience. Of the few that I phone interviewed with, at some point the subject of doing a coding assignment came up and I simply told them that we'd all be sad at events around that idea: I'm a passable coder, but years out of date. I haven't coded professionally for probably getting onto 15 years now. The job I wanted didn't involve any software development, so the exercise wasn't very useful. If I passed it, it both said something about their engineering maturity (and I wouldn't want to work there) and again wouldn't be representative of my work. The actual hiring machine at most companies seems impossibly broken. I ran into a few good recruiters, but most were just trying to make quota or show effort.
- lj3 10y agoThe last time I got a referral from an old co-worker, it got me past the resume screen and no farther. The rest of the interview was identical to what you'd face if you had applied cold off the street. YMMV.
- rafiki6 10y agoThe discussion I'm reading is absurd. Why has no one suggested a credential yet? Every other profession has it. It's insanely inefficient for our industry to behave like this. Software development and engineering is mature. We need candidates to build stuff not spend time reviewing cs101 or hours doing coding assignments
- thr0waway1239 10y agoCredentialing in software probably has a really short half life. I agree with the comment about how insanely inefficient it is though! I have this near conspiracy theory about why the interviewing process includes such ridiculous things as balancing red black trees. Like every other regulation/tax, the propagation of crazy ideas about interviewing practices is really self serving for the tech giants. In a large orgy of stupidity, companies which can neither afford the impedance of nor are particularly good at these CS type questions mimic the practices because they are probably trying to show that they have a high bar. Unfortunately, the multi-billion dollar companies can churn through the candidate selection process and waste more money in the process than many other companies' annual revenue. But I am sure they realize the halo effect of making a great deal of noise about this practice, because this is one of those strategies with very little downside and all kinds of unintended upside. If I were a recruiter at one of the top 10 companies, I would spend half my time creating fictitious accounts on various social platforms to ask about the CS question du jour at these interviews. It would be the equivalent of click fraud in tech job search. On a more serious note, I wonder if companies trying to hire these employees ever really do a cost analysis of the interview process itself? At what point does it stop making sense to "just wait till we get that truly exceptional candidate"?
- rafiki6 10y agoReally? Yet it seems that the "standard" CS101 interview is still pretty much the same. Unless you're talking strictly about credentialing for a specific language or framework which I would agree would be stupid. Also, as with other professions we can frequently update the credential to ensure it stays relevant. The IEEE has already created a software body of knowledge. There are fundamentals every software engineer should know that aren't the latest JavaScript framework.
- z3t4 10y agoif you cant find out if someone can do a job or not. how do you know if your current employes are doing their job? how do you evaluate them ?
- Schwolop 10y agoSo this is evidently the wrong forum in which to ask, but what's it like interviewing in other fields? Do chemists have to perform a titration in front of the panel? Do surgeons have to demonstrate an anatomy lesson on a cadaver? Do bricklayers have to build a wall in under an hour?