Taro Logo

How to build meaningful relationships with your co-workers if you work remotely?

Profile picture
Software Engineer at Seed Stage Startup10 months ago

I've been working remotely for a startup for almost a year now and noticed that all my interactions with my co-workers are purely transactional. Software engineering is a team sport and I have never experienced such apathy towards the people I work with. Is this the default in remote work? How do folks who are 100% remote find ways to build relationships with other engineers?



  • 8
    Profile picture
    Senior Software Engineer [L5] at Google
    10 months ago

    Software engineering is a team sport and I have never experienced such apathy towards the people I work with.

    I love your self-awareness with this one - it's hard to admit that you feel this way! Awareness if the first step toward addressing this - and we all need to feel like we are part of a great team to excel :)

    Is this the default in remote work?

    I don't know if it's the default; I do know that, even prior to remote work becoming more accepted during covid, remote work always had extra communication challenges.

    For example, one of the core aspect of showing up in a team is presence, and while we have tools that allow remote folks to simulate in-person presence to a degree, nothing we have comes close to speaking to a person face to face yet. (Or even just watching a teammate physically come into the office, working hard on their own.)

    You might want to check out this question on remote communication for suggestions on what you can do.

    Lastly, if you are genuinely looking to build genuine relationships, the most important thing to focus on is getting to know the people on an individual basis. For example, do you know who on the teams shares similar hobbies as you? Or who has the most interesting side-gigs? Do you know what are the career goals of your fellow teammates? And what motivates them to work for the seed stage startup you all work at? You'll likely have to take the initiative to get to know them and ask them questions first before they reciprocate for you.

  • 10
    Profile picture
    Junior Software Engineer at Series B Startup
    10 months ago

    Fellow remote, also at a Startup here. From my experience so far, the social climate seems predominantly swayed by management and then the engineers in leadership positions. There were times when I felt like I was on a team and times when I felt like I hardly knew anyone; our interactions were tense and vapid, I think akin to what you're describing. The former was when we had a leaders who strived to be inclusive and transparent as possible whereas during the latter, there was a lot of tension in upper management, which then led to lead engineers getting over-burdened and micromanaged, whose stress infected the rest of us.

    That said, I do believe not all hope is lost (especially in regards to building relationships), just that there is more proactivity required from us. The following are ways that have helped me (and continue to regardless of company climate):

    • Set up regular times with one or two colleagues to pair program or rubber-duck so that you both have a good excuse to connect while working
      • I liked having one with a teammate and another outside of my team, each on a weekly basis. This way I not only got an 'insider' and 'outsider' perspective on my code but also a feel for overall morale (this probably only works for those of us at startups).
    • Create a social channel (such as #pets-at-our-company to share cute photos of your furry family)
      • Everyone seems to show their soft side in these channels, and that is always a nice reminder
    • Be the first one to be 'vulnerable', oftentimes just initiating that behavior disarms the rest of the room
      • Rather than robotically announcing my updates during standup, I have been trying to infuse some human element. For example, sharing a new thing I learned during yesterday's debugging or giving a shoutout to a colleague whose PR I enjoyed reviewing or whose insight helped me get unblocked. Although sometimes I feel like I'm oversharing, I feel that it has encouraged others to open up.
    • Create a Friday happy hour
      • I know a colleague who started this for their own team and it influenced other team managers to do so as well. Not everyone shows up, but it is definitely a nice way to remember how awkward we can all be and get to know each other:)
  • 5
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    10 months ago

    Potentially a cop-out answer: could you meet up IRL with your coworkers every so often? (presumably on the company's dime)

    You said you're 100% remote, but I know many companies which are 100% remote that still have offsite every 3-6 months. The whole team (or the whole company, since you're at a Seed Stage startup) flies into a city for discussion, hangout, and a fun time.

    The trust you build with these meetings is incredibly powerful and effectively acts as the fuel for the activities that Kuan and Grace suggested.

  • 10
    Profile picture
    Mid-Level Software Engineer at Series B Startup
    10 months ago

    I feel you, I had that issue with my first remote job. You can definitely build meaningful relationships, I have, but it will take some effort and vulnerability. I don't know if it's necessarily the default with remote work, but it's way easier to fall into comfortable disconnected patterns, especially with the focused work of developers.

    It's easy for interactions to be transactional when they're about work. A code review is way less personal than raving about your favorite tv show or venting about a frustration in your life. I found making an effort to be fun, kind, and human makes it easy for others to return the favor.

    One way to break the ice of vulnerability is with public praise. Either in a public slack channel or decent sized meeting, give a coworker a shoutout for something helpful they do. I remember almost every time someone has given me a genuine compliment and it makes it much easier for me to connect with them on a personal level.

    A few things I found useful

    1. Schedule a half an hour one one with someone and make the goal not to mention work.
    2. Use liberal memes and jokes when interacting with coworkers in private chats.
    3. Share your suffering. If your stuck debugging some niche issue for a few hours or are putting out a fire, involve someone else. Patching a prod database in a pair programming session builds way more trust and connection than a async code review.

    If you try to make an effort, other people will reciprocate. So just find a way that to reach out that makes you the least uncomfortable.

  • 4
    Profile picture
    Senior Software Engineer @ Auditboard
    5 months ago

    Building relationships requires vulnerability. And vulnerability comes from speaking your truth and not knowing how the other person is going to respond.

    I graduated coding bootcamp in 2019 and moved from junior to mid to senior engineer during the pandemic.

    A few tips that can be helpful:

    • Develop a consistent support system inside and outside of work. You want to fill these 4 buckets:
      • (1) Network Horizontally - find peers who are around your level who you can speak freely around. And then make sure these are people who don't one up you when you have positive news and people who don't tell you about how much worse they have it when you have negative news. Find people who can just listen to your struggles and speak with empathy.
      • Networking Up - Mentor Buckets
        • (2) - Find someone 1-2 steps ahead of you. Ideally this will be another junior developer who is crushing it and on their way for a promotion or a mid-level engineer. There's an abundance of people in this category on Taro.
        • (3) - Find someone 3-5 steps ahead of you. This should be a senior+ engineer.
        • (4) - Find someone 10-15 steps ahead of you. This could be a SVP of engineering, CTO at a mid-stage company, a staff software engineer that has super high impact at a larger tech company. This is Rahul and Alex for everyone in Taro.
    • Get comfortable with writing. Most engineers aren't strong with people skills. Many engineers have little tolerance for mistakes and especially repeat mistakes. Structured writing exercises is your best option. I always recommend the full Self Authoring suite by Dr. Peterson.