5 ms·
Last summer I had an interview with a large insurance company for a front end role. The take home test was to produce 5 HTML+CSS+JS components to their existing
by onion2k 7y ago
Last summer I had an interview with a large insurance company for a front end role. The take home test was to produce 5 HTML+CSS+JS components to their existing designs (basically to take a PNG and turn it in to a web component). The components were a hero element, an information card, a notification banner, a list and a working calendar with selectable date ranges across different months. They were all to be made without any CSS or JS frameworks and they needed to be responsive. They suggested this would take about 4 hours.
I read through it and spent a couple of hours on it before abandoning the test and sending them an email to withdraw my application. If I was making those components properly I'd spend about week of solid dev time on them - 1/2 a day on each of the first four components and 3 days on the calendar..
Maybe I'm a terrible dev and very slow, but all that test really told me was that the developers there hack things together without spending time thinking about what they're doing, and on reflection I didn't want to do that.
- simplecto 7y agoI can respect that position. However, as a hiring manager I can see their perspective. That perspective being, "How fast are you at good enough?" Food for thought in the future. As a hiring manager I would have accepted all 5 done for 50% of all screen types, with developer comments on where you got stuck or what compromises you chose to make. In my opinion that should be made clear in take-home tests. "You are allowed to cut corners, but please comment on WHY you did so"
- ryandrake 7y agoAre you really looking for “engineers” who can half-ass a project from start to finish in 4 hours? That’s the quality bar? If I were in OP’s shoes and feeling frisky I would point out to the hiring manager that for a real world project like that it would take at least 4 hours to just gather the requirements, write a design doc, and provide an estimate. 4 hours to do design, implement, and test something properly is ridiculous. And if you aren’t focused on doing it properly, then——wait, what company are you hiring manager at? OP’s hiring company was an insurance company, not an Uber-For-Cats startup. The software he or she is eventually expected to write on the job is supposed to work.
- megous 7y agoAn engineer should be capable of selecting the best solution for given constraints. That's a core of the job. If the constraint is 4 hours, the manager can't expect nothing but 4h quality.
- subhobroto 7y ago> If the constraint is 4 hours, the manager can't expect nothing but 4h quality. Yes, but how does the manager estimate that it indeed typically should take 4 hours when the numbers he gets are: 1. From his employees who work at that company, intimately familiar with the problem domain, tools and possibly came up with the problem statement in the first place and solved it in 4 hours after thinking about and working on it with no other distractions 2. From candidates self reporting the time it took to complete the problem severely undereporting the time it took them because they want to impress the employer? Is 4 hours of focused, uninterrrupted time equal to 8 4 hours of unfocused, interrrupted time? How does the manager discover the truth?
- megous 7y agoBy looking at the result of 4 hours of such work, obviously. :)
- twh270 7y agoThe trouble is that the determination of "fast enough" is provided by a senior developer who has 2 years of experience with that toolchain, and that's a ridiculous expectation. Given a weekend, I can come up to speed well enough on an unfamiliar toolchain to start being productive. Given a month, my productivity is going to be high enough to be good enough for any shop that isn't looking for rock stars. I interview candidates on their fundamental skills and ability to solve problems. If you're reasonably intelligent, can communicate well, and have logical and higher-order thinking skills, I don't care what tools you've used in the past. Many times I've recommended someone who has absolutely zero experience with the tools my team uses.
- subhobroto 7y ago> The trouble is that the determination of "fast enough" is provided by a senior developer who has 2 years of experience with that toolchain, and that's a ridiculous expectation. I dont think it's a ridiculous expectation. People rarely apply for Django jobs if all they know and have been working with is Java and have never coded a Django app. However, I think the OP is severely biased and blinded by their viewpoint as an employer and have failed to view it from the viewpoint of an employee who's so frustrated with their current employer that they are willing to put up with hours of looking for job posts, doing background research on companies, filling out forms, following up on applications, answering random trivia questions and random take home assignments at the end of their full work day > I interview candidates on their fundamental skills and ability to solve problems. If you're reasonably intelligent, can communicate well, and have logical and higher-order thinking skills, I don't care what tools you've used in the past. Many times I've recommended someone who has absolutely zero experience with the tools my team uses. This sounds so refreshing and atypical of the standard interview that I would love to give this a go. My email is my handle at gmail.com No obligation. I just want to connect with an individual who thinks deeply about real life problems.
- subhobroto 7y ago> That perspective being, "How fast are you at good enough?" That's a great question to ask. However, I now ask you if that's really the question you are indeed asking an engineer who already has a full time job with possibly a hour or longer commute and is attacking your problem at the end of the day or week. If that's the case, what you are really asking the question "How fast are you at good enough when you are extremely tired and nearly exhausted?" Either that or you're selecting for candidates who are not challenged enough at work and work at a place that does not fill the rest of their employee's time with busy work to make up for the slack so they have time left over to work on your project. You have thought of the problem from your viewpoint as an employer but have you viewed it from the viewpoint of an employee who's so frustrated with their current employer that they are willing to put up with hours of looking for job posts, doing background research on companies, filling out forms, following up on applications, answering random trivia questions and random take home assignments at the end of their full work day?
- raxxorrax 7y agoIncredible... I think if you want to develop solid components, I don't think the time spend is high at all, on the contrary. Right decision to withdraw the application in my opinion. I like it if I can gather some points with an assignment, but I would have mentioned their ridiculous time estimation and how they determined the required effort. If that wouldn't lead to a significant alteration of the task, the interview would already be concluded. You pay quite high prices to have such components developed.
- subhobroto 7y ago> You pay quite high prices to have such components developed. Exactly! I would be VERY happy if I got the software I needed for the hours quoted on take home assignments. I heard about this last year from a co-worker and became so intrigued that I started to fill out some applications to really see if it was the truth! It indeed is! What confuses me is why are managers falling for it? One hypothesis is that they have bad data - something I commented on elsewhere on this thread.
- ryandrake 7y agoI don’t understand these time limits measured in hours. What practical job skill are they testing? If it’s “we just promised a customer a new UI to be delivered working and tested by end-of-day!” then you dodged a bullet by withdrawing. Maybe I’m just really lucky, but I’ve never had a grownup job where a new, never before seen engineering project was due in a time period of less than a few days.
- megous 7y agoIt's a home assignment, not an engineering job. It shows expectation on how much time at most you're expected to waste on it to get hired there. Though to be fair, they should make the limit strict, otherwise they're selecting for people willing to do more for free, if they just then compare results without comparing the actual time spent.
- ryandrake 7y agoIf I was looking for a builder to build me a home, I wouldn’t ask candidates to show me they can build a doghouse in 4 hours.
- megous 7y agoSure, but you're looking for a programmer. :)
- subhobroto 7y ago... and how exactly is developing code from scratch within 4 hours different from developing code a doghouse scratch within 4 hours? Both require good thought, design and a plan to execute. The only way to deliver a doghouse from scratch within 4 hours is to have a doghouse template that's prefabricated, ready and available.
- megous 7y agoAn experienced web developer will have template in his head for various typical problems. So that should not be an issue at all. It's just typing it out for the component at hand. Asking for using web components will of course limit the pool of candidates having a mental template quite a bit, since it's a fairly recent technology, and even then, most people probably never used the raw API, or if they do, they wrap it a bit, so it will not be something they'll remember right away. That's the major pitfall here, to me.
- megous 7y agoAre these tests supposed to reflect real-world programming? If not then the month view "calendar" widget has just three state variables: current view start, selection start, selection end, and the rest is just calculated from that. 4 hours for everything is a bit harsh, but a basic calendar view shouldn't take more than a few hours using just the today's web tech. It will certainly take more hours if you try to make it accessible or compatible with too many browser versions, or start adding features like DnD range selection, or start optimizing, etc. But if company expected me to make a fully fledged usable component on a home assignment, that they can just use, I'd send them a quote, lol.
- crimsonalucard 7y agoWhy test real world programming when you can test for things that are harder and select candidates who can perform better than "real world."?
- subhobroto 7y ago> Are these tests supposed to reflect real-world programming? That absolutely is the expectation. These are not tests for basic coding proficiency. These are not tests to see whether you can build a single component or widget. These are tests to check if you can build a full suite of components or widgets including a README, tests. ... and candidates are apparently delivering. I can get a GraphQL/Express server up and running from a frequently used template I built, in 90 minutes will full support for Query, Mutation and Subscription. Create new users, tasks, updates, votes? Check Update users, tasks, updates, votes? Check Get realtime notification of changes to users, tasks, updates, votes? Check Apparently there are others who can not only do this but also implement a react frontend that puts the UI support for these as well in just 30 minutes more. Either candidates are reusing templates they have built in previous projects and not reporting the time it took them to build the template when they report the time Or, they are grossly under-reporting the time it took for them to complete the assignment. We are doing this to ourselves. We should not deflect the blame. If we feed garbage data to companies and then companies base their decisions off that, it's absolutely unfair to blame companies for not being realistic
- 7y ago
- crimsonalucard 7y agoI was once given a take home with unlimited time. They wanted me to give them the best possible solution. They would compare all candidates based off of the best work they could produce. I went all out and wrote a solution that was point free. No variables. Now it is my default paradigm.
- altmind 7y agoAnd you articulated what are you caring the most in your solution. Giving them a lot of food for thought.
- crimsonalucard 7y agoA lot of them haven't even heard of the point free style using function composition let alone function composition. One of the core tenants they wanted me to ascribe to was to not overdo it with abstractions. The fact that I actually used minimal abstraction (I didn't use the abstraction of object orientation or even variables) was lost on them. Instead the foreignness of function composition and of a program that was simply just pipelines of functions appeared as if I overdid it with abstraction. Less food for thought but more biases and gut reactions and the same typical stuff you see among all people. I learned that people interview for a stereotype based off of their experience, if you introduce something outside of the stereotype then you're a goner.
- b0rsuk 7y agoThey told me they would mail me a programming assignment, giving me one week but a skilled dev would really only need 2 hours for that. I asked them "what contract"? And they were befuddled I expected to be paid for a week's worth of work. Anyway, I told them, in a non-committal manner, that I would take a look. The assignment was to write a Django app (module) related to restaurants. Backend, templates, some light pagination, documentation, and at least 70% test case coverage. I re-adjusted my priorities and did it at my own pace. I didn't bother sending them the finished work, just treated it as a programing exercise. It struck me that with such requirements it's basically production ready and they can use my work with perhaps two or three small adjustments, even if they reject my application. Entitlement is high among programming reviewers.
- subhobroto 7y agoUpvoted. You are absolutely correct that this would take a magnitude longer to build from scratch. > a skilled dev would really only need 2 hours for that Ah. I think that's the problem. I suspect the "skilled dev" is keyword for "reuse existing project". I can absolutely see myself reworking a Django app to support a backend, templates, some light pagination, documentation, and at least 70% test case coverage in 2 hours if I had an existing similar Django app with a backend, templates, some light pagination, documentation, and 90% test case coverage and I needed to rework it. I think your competition cheated in reporting the total time it actually took them
- subhobroto 7y agoYou are not accounting for the third option: cheating. I think there's a major disconnect in candidates wanting to be treated respectfully and companies that offer take homes I have a suspicion that companies that offer take homes expect the candidate to cheat in some way or the other and begin with assuming the worst. ... or they are simply going off the data that they have. I think majority of the candidates cheat by simply severely under-reporting the time it took for them to complete the assignment. 99% of the take home offers I receive are "our candidates typically take 2 hours to complete this assignment". These are not tests for basic coding proficiency. These are tests to check if you can build a full stack application - backend AND frontend including a README, tests and majority of candidates are typically taking 2 hours to complete. I can get a GraphQL/Express server up and running from a frequently used template I built, in 90 minutes will full support for Query, Mutation and Subscription. Create new users, tasks, updates, votes? Check Update users, tasks, updates, votes? Check Get realtime notification of changes to users, tasks, updates, votes? Check Apparently there are others who can not only do this but also implement a react frontend that puts the UI support for these as well in just 30 minutes more. Either candidates are reusing templates they have built in previous projects and not reporting the time it took them to build the template when they report the time Or, they are grossly under-reporting the time it took for them to complete the assignment. We are doing this to ourselves. We should not deflect the blame. If we feed garbage data to companies and then companies base their decisions off that, it's absolutely unfair to blame companies for not being realistic
- pan69 7y ago> They suggested this would take about 4 hours. Software developers are notioriously bad at esimating. Personally I have started to refuse take-home tests and whiteboard puzzels. I now use it as an indicator of people I don't want to work with.
- subhobroto 7y ago> Software developers are notioriously bad at esimating. While that's true, understand that the numbers companies are quoting are not esimates but rather actual time candidates self reported after finishing an assignment. I expanded a bit more on this in a sibling comment.