Common misconceptions about working remotely in tech—and why they’re wrong According to Stack Overflow’s 2017 Developer Survey, more than half of developers say remote work options are a top priority when looking for a new role. Yet, if you’ve never held a flexible or work-from-home job, you might have doubts about whether working remotely is a good idea. Maybe you’ve seen one too many sounds-too-good-to-be-true online job listings. Or maybe you’re just so used to going into an office that it’s hard to imagine doing anything else. We get it. Making the switch to remote work can be daunting. Let’s dig into a few common concerns:
Inside Ahmad Fathy’s journey from developer to software engineering manager Ambition, drive, hustle — we see these terms listed in job descriptions, discussed by career development experts, and praised by successful entrepreneurs. But it’s rare to see them in action in such a clear and dramatic way as is evident in Ahmad Fathy’s career. Ahmad’s connection with Crossover began when he applied for a C# engineer position at enterprise software company Aurea, one of Crossover’s largest clients. Although he had passed all the qualifications for the role, it was filled before he had the opportunity to accept. Another manager at Aurea offered Ahmad a position as a SQL developer. Although it wasn’t his first choice, he had experience in this domain and saw the offer as a challenge.