REPOSTING IN THE CORRECT CHANNEL Happy Wednesday ...
# hiring
t
REPOSTING IN THE CORRECT CHANNEL Happy Wednesday Kotlin lovers... I currently have 2 contract positions open for Back End engineers in central London. The roles will be remote during COVID however will be based in Office once lockdown is over! It’s with a sustainability ML start-up and will run full time for at least 12 months. Kotlin and spring experience is key. Ping me a message if you’re keen!
t
hope you don’t mind me asking - but if the position can be remote, why make it London based once lockdown is over?
👆 3
3
👍 8
💯 2
r
@tddmonkey to be able to se how you are typing your code 😄
t
I ask as I am based in Yorkshire, but I work in London and travel down to down 3-4 days a week in the office. Obviously I’ve been working full time from home for weeks now and it leaves me questioning why I’d go back to the previous model when this one not only works better, but leaves me happier. It just seems that as we’ve all adapted to remote working, opening up a job like this that you’re happy to have remote gives you a much bigger talent pool to draw from if you remove the “London” restriction
4
c
There is a big difference between allowing employees you have interviewed, hired, and worked with for hours to work from home compared to hiring someone remotely and never met
I agree a lot of things are going to change after covid, but there are clear downsides to this entirely remote thing
t
Would you like to elaborate?
e
I don't see clear downsides if you have a scrum team mature enough to do the onboarding of new members to the team... I have worked with team 300km appart from my home, some of which I never met in person, I was able to deliver quality work. The only downside I see is the project managers and bosses that can feel less relevant because they can't sneak over your shoulder or get you in impromptus pointless meetings whenever they want. If you want to be sure you hire the right person, give him/her a trial period and a mini project to see how they thrive.
c
Engineers never see any downsides to 100% remote work, but everybody else responsible to actually ship the product usually does 🙂
It can work, but it's not as straightforward as saying "I was able to deliver quality code".
And this has nothing to do with micromanager bosses, it's a lot more nuanced than that.
e
Surprisingly, it was pretty straightforward. But I'm not a junior programmer too. I don't need someone to hold my hand. Might be harder for someone less experienced.
c
Even though you are senior, you might still be missing the bigger picture that shipping a product is much bigger than developers producing quality code.
e
Well, but quality code is pretty essential though... Garbage in, garbage out... ;)
c
It's a necessary condition but far from being sufficient.
e
True, but 100% remote team can work, I don't say it's easy but not impossible either, and to produce a good product that the customer want to use. Anyway, right now a lot of people is remote, it might bring some questioning about how we work. Wich is good I think. Hope you will find the right candidate for your job opening. Have a nice day, take care.
t
Let’s assume that some of us here are in fact experienced enough to understand what exactly is involved in shipping a product and aren’t just code monkeys - what do you think the downsides are? And if we want to be holistic, are those downsides offset by the potential gains?