A significant source of frustration at $dayjob recently has been the _inability_ to test in production. We've just deployed Stripe, and if you're using prod API keys, there's no testing possible without spending real money. Deploy to production and pray to the tech gods I guess.
One of the earlier things I tried was to encourage myself to learn using a less awful layout (DVORAK as you suggested), and it didn't go very well unfortunately :(
That's very interesting about "developing" my fingers, I'll think on that, thank you!
Remote is in the title of the post and mentioned multiple times throughout the post.
I dare say we're not posting frequently enough, that's a good point.
It's against company policy to put the range in the ad. Very very stupid, but probably nothing I can do about that.
We have three languages mentioned in the ad. But any senior candidate can be introduced to new technologies so they're not in the "requirements" section.
We could probably improve turnaround time, but the lack of applicants alongside natural attrition is making that even harder to make happen.
Thank you jhot!
Copypasta: This is a throwaway because I'm just an engineer on the team wondering if there's something obvious we're doing wrong, and I don't imagine this would be considered desirable attention by management.
> It's against company policy to put the range in the ad. Very very stupid, but probably nothing I can do about that.
This is already against the rules in CO and soon WA and NYC. Your company may as well get use to posting ranges. Ranges are also thought of to lead to more equitable outcomes for those working at the company.
I am in CO and saw one ad that had a link to a special page on their website to "comply" with this regulation. It was a blanket statement that salary can be between $20k (can't remember the low end but it was something like that) and $1MM based on position and experience. I was very put off by that and did not apply. I didn't take the time to look into the legality of using a blanket statement like that but it seems sketchy to me.
The legality is "not so much" but for smaller companies they can get away with it (because small companies are unlikely to have defined titles and bands to begin with).
This is a throwaway because I'm just an engineer on the team wondering if there's something obvious we're doing wrong, and I don't imagine this would be considered desirable attention by management.
Would posting a job ad on AskHN requesting feedback be acceptable? I ask because I'd have expected to see it a bunch if it were. @dang would be very appreciative of your word one way or another. Thanks mattbee.
I'd say don't post your actual ad because we will find you and give you more help than you wanted ;) Like maybe your team page is all white men, or your defence contracts are very prominent, or your CEO is a public dong.
It's a bit of a yellow flag that you don't feel you can go to your managers with this to help fix a team you're obviously invested in? But here's two tips that you might be able to implement or influence by yourself:
1) Treat incoming candidates like GOLD. Respond to them within hours, same day where at all possible. Make decisions really fast, schedule interviews within 1-2 days, drop other things to make that happen. Have future managers & engineers communicate directly, lightly backed up by HR if you have that function (and you trust them). Keep. It. Moving. Make it clear their time is more valuable than yours.
2) Document the whole interview process up-front, put it prominently on your ads, specify the damned salary, and stick to your word the whole way.
If you execute on both of these points, the FAANGs will not be able to come close in a really critical part of the process. They will be unclear about what happens next, who you're meeting, how important it is, maybe it will be a week, maybe it will be 12 weeks, who knows. But they got the prestige and the big bucks, and candidates will put up with a lot for that.
(fwiw, I co-designed careers.bytemark.co.uk/full-process for most of the above reasons, and my current role went from introductory chat->3 interviews->contract signed in about 10 days flat - I like fast recruitment!).
1) Treat incoming candidates like GOLD. Respond to them within hours, same day where at all possible.
This is a huge point and something to work on. Act quickly and work out as many things in advance as you can. Don't be like unnamed company X who kept changing interview times and stretching it out so the candidate just took the offer from unnamed large company Y instead.
If you get some nibbles on your pipeline treat them quite fast, and note where they drop off. Likely for the process you have the salary is too low, and people skip out to find the same money easier or more money at the same difficulty.
This also includes being very, very, very upfront on whether your "remote" is:
a) real, honest 100% remote,
b) 100% remote unless you are within X miles of the office, in which case it's hybrid,
c) hybrid that your management thinks is "remote",
d) "remote until..." which means you will be called back into the office at the C-suite's whim, or
e) on-site unless you are sick or have to meet a repair person at home.
> Have future managers & engineers communicate directly, lightly backed up by HR if you have that function (and you trust them). Keep. It. Moving. Make it clear their time is more valuable than yours.
Yeah, this.
Not that I dislike recruiters or HR folks or don't appreciate the work they do, but with someone with engineering experience I can talk to them on an equal level and don't need to "dumb down" describing my skills or past experiences, and I can usually be a lot more straightforward and/or have an actual conversation instead of reading my CV out loud, which is what a lot of initial screenings are like (it's okay to use the CV as a starting point for the conversation). Talking to an engineer is also a signal I'm being taken serious as a candidate.
I get that people use recruiters for an initial screen, but if it's "recruiter → another recruiter → HR person → coding test → finally I talk to a damn engineer (or engineering lead)" then that's a bit of a turn-off. At this point you're expecting me to spend time to "prove" my technical skills and I don't even know if I want to work for you because I have no idea what your engineering is like beyond the buzzwords your HR people dropped (which is very little information).
If you've got more candidates than you know what to do with then that's fine, but if not... Using a recruiter for the initial (short) screening is fine to go through some basic preconditions from both sides, but the second person should really be an engineering lead if you're desperate for people IMHO.
If you do insist on a code test and you intent on hiring the person if nothing strange comes falling out then say so. A lot of times I have the impression these things are shotgunned to a bunch of candidates.
There is no on-call. Like I say, it's not a DevOps position, but an SWE position requiring more significant knowledge (not administration) of the underlying platform than is typical.
To echo what a few other comments have said, seeing "DevOps" as part of the responsibilities for a role is an immediate turn off to me. I want nothing to do with DevOps. It isn't interesting work (to me) and there are currently a lot of opportunities to do interesting work. DevOps also isn't challenging work (to me), it is simply frustrating work because I do not want to learn it, I just want to complete my dev task and move on to the next.
I've been having the same problem. It's actually a lot to ask of someone to be a solid coder but also willing to do on-call support. The direction we're looking is to replace "DevOps" with "Platform Engineering" and retain an MSP to do on-call tier 1 and 2 support.
Thanks for 4dayweek.io! Quick bit of feedback: It's the only job site I check regularly that doesn't have a feed I can subscribe to (that I could find, anyway). It's made worse by having to scroll past the same group of prioritized listings every time I visit. Would really appreciate some improvement here <3
