<story><title>How to set junior employees up for success in remote</title><url>https://slite.com/blog/micromanagement-is-not-a-bad-word</url></story><parent_chain><item><author>slackfan</author><text>For junior engineers it&amp;#x27;s really easy to fall into the trap of trying to solve everything themselves instead of asking for help when they are remote. I say this as somebody who has spent the last five years working remote team-based gigs.</text></item></parent_chain><comment><author>itsmemattchung</author><text>&amp;gt; For junior engineers it&amp;#x27;s really easy to fall into the trap of trying to solve everything themselves instead of asking for help when they are remote&lt;p&gt;Senior folks do this. All the time.&lt;p&gt;Despite having 10+ years of experience and leading engineers at AWS, my default is to &amp;quot;spin my wheels&amp;quot;. Now that I understand myself a little better, anytime I find myself laser focused on a problem, but making 0% progress, then I either:&lt;p&gt;1) distance myself from the problem or
2) ask for help
3) both&lt;p&gt;Junior or not. Asking for help can be difficult</text></comment>
<story><title>How to set junior employees up for success in remote</title><url>https://slite.com/blog/micromanagement-is-not-a-bad-word</url></story><parent_chain><item><author>slackfan</author><text>For junior engineers it&amp;#x27;s really easy to fall into the trap of trying to solve everything themselves instead of asking for help when they are remote. I say this as somebody who has spent the last five years working remote team-based gigs.</text></item></parent_chain><comment><author>_fat_santa</author><text>One thing I started as a team lead is telling all my Jr and Mid level engineers to reach out to me for help if they need it, and that I would always be happy to get on a call with them. I had a pretty small team so this was easily manageable. At first I wouldn&amp;#x27;t get any folks reaching out for help, but eventually they all got comfortable with calling&amp;#x2F;messaging me if they had an issue.&lt;p&gt;I think a bit part of this is how you see yourself on the team. I gave myself the personal title: &amp;quot;Specialist and Support Person&amp;quot;. On any given day I really only have two tasks:&lt;p&gt;* Work on &amp;quot;specialist&amp;quot; stuff within the app, stuff that is way over the heads of any of the Jr&amp;#x27;s or Mid level devs.&lt;p&gt;* Provide Support on everything else. Since my engineers are the ones pumping out most of the code, the biggest part is making sure they are supported in every way imaginable.&lt;p&gt;There are other responsibilities obviously, but within the context of &amp;quot;day to day&amp;quot; on the team, I found aligning myself with those responsibilities really helped my team.</text></comment>