4 ms·
> I'm not gonna try to attribute numbers but it's clear to many that the junior members are more prone to not adapting to remote work easily. It's a problem, fo
by 908B64B197 4y ago
> I'm not gonna try to attribute numbers but it's clear to many that the junior members are more prone to not adapting to remote work easily. It's a problem, for which we need to find a solution. Not necessarily going back to office tho.
The issue is with hiring. When hiring remote junior, you need to look out for above average communication skills and debugging abilities. That's often not present for a lot of new grads entering the market because of a lack of experience or relevant work. Think of three month bootcamp grads where each week's assignment was spoon fed by the instructors who themselves are students who couldn't get a real job.
Some places that hired from that pipeline are finding out it's simply impossible to bring these programmers up to speed, but places hiring real engineers have way less issues (because a serious program will include challenging work and select for people capable of debugging and reasoning independently).
- eschneider 4y agoWhen leading/mentoring junior engineers, it's important to check in periodically and ask questions so that you know that they understand what they're working on and that they're not stuck. You can't expect them to raise those issues themselves. That's one of the things that makes them juniors. So yeah, you've got to spend some time every day syncing up with them and making sure things are on track. That's true if they're remote or in the office, but if they're remote, managers need to be a bit more proactive in asking questions and following progress.