Remote,
2 min read.
What remote teams actually look for in a first call
It is less about your home office and more about how you write, plan and ask for help.
Elias Lindqvist
Engineering
I have sat on both sides of a lot of first calls for remote roles. The people who get through are rarely the ones with the best camera or the quietest room. They are the ones who show, in thirty minutes, that they can work well without someone next to them.
They listen for how you write
Most remote work happens in writing: tickets, pull requests, short notes at the end of the day. Expect a question like “tell me about something you explained to a team you never met”. A good answer has a document in it, not a meeting.
They want to hear how you get unstuck
Being stuck alone is the hardest part of remote work. Teams want to know what you do after an hour of going nowhere. “I write down what I tried and ask in the team channel” beats “I keep going until I figure it out” every time.
They check the hours, not the place
Most remote roles on Carriera are open anywhere in Europe, but they still have a team that works in one or two time zones. Say plainly which hours you can overlap. It is the most practical thing you can offer, and the easiest to get wrong later.
They notice if you have done it before
You do not need years of remote work. But if you have worked across offices, run a project with a team abroad, or kept a side project going with people you only met online, say so. It is the same skill.
What you should ask them
How often the team meets in person, who pays for the trip, and what happens when someone is ill on a launch week. The answers tell you whether remote is a policy or a habit.
