It's a lot easier for me to observe a junior struggling, spinning their wheels, and give corrective feedback in the office. I don't know the remote equivalent of glancing at their screen and body language while I get up for a bathroom break.

Listen to what they say during the daily team meeting, and occasionally ask by chat how they're doing. It's true that it has to be a bit more explicit, and it may be a bit slower, but it's far from impossible.

That's one point of contact per day. I was able to continuously be aware of anyone struggling before. I can't continuously ping them throughout the day. Even 4 times a day seems much too high contact to not be patronizing, and that still leaves them to stew for up to two hours at a time

It's really this simple. Junior employees need to be more actively managed than senior employees. They literally do not know what they're doing, that's what makes them junior. Remote or local, they need more oversight to help them learn and become productive.

Can you give me advice on how to provide oversight in a way that's not demoralizing, infuriating, patronizing?

I found working with juniors _fun_ and rewarding in person. Remote i have hated it and don't think I've been good at it

One thing that has worked for me in the past is to do some regularly scheduled pair programming. When I'm driving I narrate my thought process and encourage questions. They get to see things and when I make a little typo and they can catch it, not only does it save me a few seconds but it makes them feel GREAT that they helped the senior dev. Making this highly interactive and the senior driving FIRST makes it still "fun" when the junior is in the driver's seat.

One of the biggest skills you're helping a junior to learn is how to break apart a big task into small, workable components. Maybe they are assigned a user story, but that user story is going to need multiple functions written, or something like that. So you might start with pseudo-coding or creating the interfaces together, talk high level about how a particular method should work, and then let them do that part by themself. "Let me know if you get stuck or done with that and then let's do a little informal code review."

Beyond that it's the normal management stuff of compliment sandwich on negative feedback, etc. The normal things you do to build and maintain rapport with coworkers.

Oh, another thing I find helpful is to make it clear up front what I'm doing and why. I don't just narrate what I'm literally doing in the programming, I narrate why we're doing this at the meta level and what the expectations are. I also make it clear that as they get more comfortable there will be less oversight.

The difference is it in the office you can just actively see that somebody is anxious and you can ask them what’s up.

True, but there have been plenty of cases where juniors languishing in an office with little guidance. And remote you can still ask them how they're doing by chat.

It's true that the barrier is a bit higher remote, but it's not unsurpassable.

In office, there's watercooler chat that can lead to debugging session. In remote there isn't.

That being said, with the former culture, it's harder to ask question online and asynchronously, since usually they prefer and wait to have in face session instead.

The equivalent in remote is a chat/thread turn into a call with a screen share. Managers and seniors encourage juniors to ask questions or just “speak” their minds. There are multiple touchpoints for that to happen, dailies, 1:1’s, spontaneous check-ins b/c people care. In a culture where remote work habits are good, these will be imparted on new-joiners, especially less experienced ones.