3 ms·
It is beauty competition. Disclaimer: I am biased gray-hair contractor who's milking own network. "fairly typical run-of-the-mill mid-size enterprise software
by imhoguy 4y ago
It is beauty competition. Disclaimer: I am biased gray-hair contractor who's milking own network.
"fairly typical run-of-the-mill mid-size enterprise software vendor" - read: boring, maintenance, legacy, but that is ok, I work on such stuff when it pays decent daily rate;
"fully-remote SWEs in the "DevOps" software space (Linux, containers, k8s, yadda yadda)", "higher percentage non-code" - sysadmin, jira queue, SEVs, on-call duty, yaml development, no essential prog lang skill, o'rly you need SWE?
"we're junior-heavy already" - babysitting, scrum;
"haven't even managed to backfill a retirement from six months ago", "the work requires a reasonably deep understanding of the underlying platforms" - seek Sol. Architect or on-board into small area first, legacy can wait;
"take-home technical assignment (~4h) or similar at candidate's choosing" - what? take-home k8s cluster? Maybe better try some gig/probation week, daily rate applies ofc.
I think I would fit, but why I should move my lazy ass off my golden handcuffs just before summer?
- jelling 4y agoI feel similar but just want to add that letting people do a ~20 hour probation week could be useful for both parties here. Meaning they can keep their same job, but you're going to pay them to do 1-2 weeks at 20 hours per week. This doesn't sound like a sensitive IP situation, either. Also, if you can't get someone up and delivering value in 20 hours that's good data about your internal setup. My goal is a minor commit on day 1. And if you can't spec out value that could be delivered in that time frame you probably have weak requirements.