I'm Ben Greenbank, a software engineer at Algolia, and I'm excited to delve deeper into strategies that can elevate your impact as a developer, even when you're not actively coding.

This blog is taken from a presentation I gave at DevCon 2024, and if you’re interested you can watch the entire presentation below.

The challenges of remote work and async communication

Let's begin with a common experience for many of us: remote work. Even after many years of working from home, I still find async work challenging. The isolation, the lack of spontaneous communication that comes naturally in an office setting, and the challenges of conveying tone and nuance over Slack can all take a toll. It can be harder to build relationships, ask for help, and receive timely feedback.

However, remote work doesn't have to be synonymous with isolation. Once I realized that Algolia's culture values helping others and encourages curiosity, it became easier. The Harvard Business Review highlights some of the unique challenges of asking for help remotely, and personally I've learned to adapt by being proactive, clear, and specific in my communication.

 Here are some learnings from my experiences so far:

• Reduced visual cues. There are different communication cues you get in person versus online, although I’ve learned to not be too hard on myself if it takes time to adjust.

• Ask how your team works best. Some prefer tickets for tracking tasks, others prefer Slack huddles for quick discussions. If you’re new to remote work, you’ll find out what works for your team and adapt accordingly.

• Don't be shy to ask for help. Be clear and concise in your requests, and don't hesitate to reach out to colleagues for assistance.

• Value in-person connection. When possible, meet your teammates face-to-face to build stronger relationships and foster collaboration. My team recently had an offsite in Paris. It was the first time we were all together in person as a team. It proved that the occasional in-person collaboration really does add the icing on the cake. 

Imposter syndrome: we've all been there

When I joined Algolia, I was intimidated by the talent around me and constantly worried about making mistakes. I felt like I wasn't as good as other engineers, leading to imposter syndrome, the persistent feeling that my success wasn't deserved..

I tried to "fix" this by working harder, taking on side projects, and spending countless hours on LeetCode. But it didn't work. Eventually, I realized that my worth as an engineer wasn't solely defined by my technical skills.

Key takeaways for imposter syndrome:

• Engineering isn't everything. Being technically proficient is important, but it's not the only thing that matters. Soft skills, communication, and teamwork are equally valuable.

• Focus on other ways to amplify your impact. Cross-functional collaboration, mentoring colleagues, and enabling other teams are all valuable ways to contribute.

• Remember why you were hired. You have nothing to prove. Your skills and potential were recognized, and you were chosen for a reason.

In case you’re looking for additional resources on this, I’ve always found that Mike Cannon-Brooke’s talk on imposter syndrome to be quite useful. 

Embracing different cultures and feedback styles

Having only worked in the UK before, I experienced culture shock when I encountered the more direct feedback style of my Romanian colleagues. British communication is often indirect, relying on subtle cues, sarcasm, and implied meaning.

It was initially challenging not to take direct feedback personally, but I learned to recognize and embrace these cultural differences as opportunities for growth and understanding.

• Different cultures are... different. Recognize and appreciate these differences, and avoid making assumptions based on your own cultural norms.
  

• Embrace diversity. It's more fulfilling and enriching to work with people from diverse backgrounds and perspectives than to have the same experiences repeatedly.

• Be authentic. Don't change yourself for anyone, but be open to adapting your communication style to better connect with colleagues from different cultures.

• Learn about other cultures. If you can travel, make the most of it. Immerse yourself in different cultures, learn about their customs and traditions, and broaden your horizons.

Recap 

Remember that soft skills are just as important as technical skills, and amplifying your impact doesn't always require writing code. Contributing to documentation, sharing knowledge, and supporting your colleagues are all valuable ways to make a difference. Watch the original presentation here. 

Thanks for reading!