You wanting to focus on specific skills/knowledge is a fine goal, however if you really care about these things at the senior end, you should make the investment yourself as well and take the time to actually speak to a candidate. Who knows, you might just learn something new.
I'm not sure what you're suggesting? Just a chat where we go over all that stuff? I'm happy to take into consideration other ways of assessing.
Asking people to do it is discriminatory, because there are definitely people who are in life situations who can not afford the time to work their full time job and fulfill their other life obligations and do your quite extensive test.
If you're not spending equal employee time to my time in the hiring process, it's a no from the start.
I know back in the day when I travelled to interview somewhere, I got paid the mileage I drove and sometimes the time I spent there. Just curious if that kind of thing still applies.
Speaking of insults. You are wasting people's time and treating them without respect.
I say this as an applicant who has also wasted an entire day on an outrageously complex take-home assignment "estimated" to only take a couple of hours. It left a bitter taste.
In my view, anybody who phones in one of your assignments, or walks away altogether, is dodging a bullet.
I run a respectful process. I offer people ample time. I tell them that asking for more time is a-ok. I answer questions.
But at the end of the day, some people just really knock it out of the park (maybe around 30%?), and I don't think it's unfair to reward that.
You could run a fair competition by stating clear requirements. Instead, you reward those who are most willing to burn through extra personal time.
That is not respect.
Some people just really put effort in, and as I said in my top comment others don't. Often those others don't for valid reasons-- they have an offer on the table, they want another job more, etc. As I've said in other comments, I have no way of knowing who has put in more time (aside from Git history which isn't a clear picture, but indicative), nor would I create a malicious metric. Also, I clearly stated that I viewed this as a con of our hiring process. I'd love a clearer way to even out the time, but barring bringing in some more stressful process like some timed app or timed challenge, I don't think I can.
Say what you want, but rewarding folks who spent more time isn't disrespectful to other people who didn't. No job is a first come first serve scenario, you're both assessing each other on a variety of things, and it would be unfair of me to disregard people who excel out of fairness to those who don't.
If a seasoned dev hasn't been asked to do this in the past, i.e. it's not a requirement for delivery (it's the client or product manager that decides whether they want these features, not the senior engineer), then I'm fairly sure they'll get up to speed with these practices when they're asked to. I kinda feel you're probably binning some decent potential hires.
I made a decision in my career to consciously level up my skills-- testing, accessibility, documentation, etc-- all without being asked. Having good fundamentals just demonstrates interest at the end of the day. I don't want a master craftsman here. I just want someone who cares and tries to write good code. That's not an unfair ask. I have to hire someone I want to work with and collaborate with, and truth be told if someone won't learn a best practice in our field with being paid or it being requested, despite how nice they are, I'm not excited to work with them.
I'm not talking about someone with "good fundamentals", I talking about experienced devs who can tackle any task asked of them. The sort of developer who can walk up to the docs and start working productively with new (to them) technology within a few days and produce high quality code. The sort of developer who's probably keeping one eye on developments or features (say in Azure or AWS) that might be useful even if there's no remit for them to exploit those technologies right now. That stuff is always knocking about the back of their heads.
You cannot possibly expect every developer, even very experienced ones, to know every nook and cranny of every technology you specifically work with, but they are experienced enough to know how learn new skills quickly to complete a project.
> I made a decision in my career to consciously level up my skills-- testing, accessibility, documentation, etc-- all without being asked
I do the same, probably a couple of hours most evenings, but with the best will in the world there isn't enough time to learn and level up on everything. And that's even after nearly 40 years in this game.
I am specifically not doing that. Nor did my comments really warrant thinking that (maybe because I mentioned WCAG 2.0?). Testing, accessibility, architecture and good semantic code are skills that apply to all work in the front end space. If you're an experienced dev but you don't do those things, then I'm not exactly sure what experienced means? I don't want someone who has just built features without those things. It doesn't matter what framework you use or what libraries you know. I'm not sure how you took my comments to mean I'm doing this. I specifically tell candidates that we can teach them our specific tooling and about our business domain.
From my original comment I said "...aren't up to date on practices we care about, like accessibility, semantic HTML, app architecture etc" Perhaps "up to date" was the phrase that got under people's skin? Best practices are always evolving, but in all those categories, there is a pretty commonly understood bar of skills, and I often receive assignments that miss those marks.
Finally, I have encountered situations where one of those has been very under-skilled (most commonly accessibility), but the others were strong (testing, architecture, html/css). I have made calls in that case to hire with a plan that we'll work on the lagging skill.
I think in this case my comments were extrapolated on in an unwarranted manner. The internet isn't a perfect way to communicate, but at the end of the day I didn't say anything that is unreasonable. Also, it sounds like we're both in agreement on what makes for a good engineer.
Speaking of which... I'm intrigued by your test, in no small part because I'm not sure I'm up on accessibility (or much that's happened in the front-end world since 2015). Would you be willing to send it to me, along with any evaluation rubric you might have?
Email's in my profile.
Why would I put in over a thousand dollars worth of time into a "maybe"? Is your company going to pay me what I'm worth for that time? Is it worth my time to implement some useless widget?
Loads of other companies are great to work for and don't require this kind of worthless time investment.
Also, if you're making $1k for 4 hours, you definitely should not work for me, you have a good consulting gig going and I wouldn't be able to be competitive.
I demonstrate that I can program and that I am evidently not lying on my resume regarding basic requirements.
I do not spend more than whatever it takes me to finish the task or whatever amount of time I have slotted for the task, if you say your task takes 4 hours and I find it is poorly specced and there is dependency issues that have to be fixed meaning that nothing will build and it takes 4 hours to debug it all then you get not code at the end just a description of how the requirements you have written out have problems with it (happened one time), if I somehow miraculously manage to do what is required in 2 hours that's what I do. I have kids and other things to do.
If you are privileging people who spend 6-8 hours because their stuff is better than the people who spent the agreed upon 4 hours not only are you getting people to spend 6-8 hours of their time without compensating them, but also the people who spend 4 hours are probably completely wasting that time. I hope someone posts your company's details somewhere so I can avoid them if necessary. I'm much too busy to waste 4 hours like that. Either that or just say so up front so that people can say yeah, I'm currently not desperate enough to spend 6-8 hours working for free. But I guess you don't want to do that, do you?
I gave an honest assessment of what I feel are the pros and cons of a hiring process. You seem to have inferred a lot based on that comment.
Finally, I do occasionally get assignments that don't work. Why even bother doing it then? Those tend to confused me the most. Would you hire someone who sent you any work that didn't compile?
I've done a few of those take homes, and none of them ever really took me more than an hour (and were accepted). I have 50+ side projects using a few standard templates I've made for myself, so I can knock these out really fast and just show what I can build
Sounds to me like you've found a good way to filter out all but the most desperate candidates. Which, given your overall demeanor that suggests you're also a mandatory nights-and-weekends-with-no-extra-pay type of employer, is probably what you're looking for.
1) If that type of test is used early in the flow, then that is highly disrespectful. That type of time commitment should only be used at the end of the hiring funnel when everyone else has already signed off on me, and I have signed off on the company.
2) I need to know that the time commitment is symmetrical. While coding over zoom isn't perfect, at least I know the company has done the analysis to say "this candidate is worth 4 hours of our company's time". Once a hiring manager sets up a 4 hour calendar block on a senior engineer's calendar, you will immediately get pushback of "Is there anyway we can shorten this exercise to 1 hour? 45 minutes?"
2) The time commitment can often be more on our end, several engineers review it, it's probably equal or more man hours. I think doing a block of fixed time would be more stressful, I've had to do that and it wasn't fun.
One four hour offline/asych event, in practical coding rather than a whiteboard brain-teaser, to gauge the fit of a multi-year job relationship, is perfectly reasonable. I think the sense of entitlement might be getting a bit too high if people here say they would blow that off.
But, I have to assess candidates somehow-- I don't do whiteboarding, riddles, brain teasers, etc. I wish a discussion would just yield the results I need, but as many other top level comments here state, that's just not the case.
It has its hits and misses.
Hits:
1. We suss out a lot of people who've been a senior engineer on their resume for years but aren't up to date on practices we care about, like accessibility, semantic HTML, app architecture etc. That stuff is important, I don't want to hire folks who ship apps, but the apps aren't WCAG 2.0 compliant or poorly tested.
2. It can definitely help rescue a candidate that we're on the fence about.
Misses:
1. Some candidates blow it off or phone it in, and out of fairness to those that did well, we can't advance them. It's a shame too, because often the reason they do that is because they have other offers on the table, or other companies they're further along on, not because they have an attitude.
2. We say it's a four hour assignment, but in truth people who do well take around 6-8. It's not because the work takes 6-8 hours, but people go above and beyond, you can tell from the git commits.
Overall, I like it our coding challenge and won't hire without it, but I'm not saying it's perfect.