Remote logo

Remote Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 15 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
46.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Remote.

Showing 3 of 15
Remote logo
Remote

Software Engineer

Engineering · a year ago

Senior Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

First there was an initial screening, then I had a meeting with an engineering manager, followed by a take-home assignment. Finally, I met with the team to go over the assignment, discuss the approach I chose, and answer some technical questions and questions about the scope of my previous role.

Confirmed questions3 questions
  • Could you tell me more about the assignment and the reasoning behind your chosen approach?
  • Can you elaborate on the specific approach you selected for the assignment and why?
  • What was your thought process for selecting that particular approach for the assignment?
Remote logo
Remote

Senior Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding

So, the interview process went like this: first an HR chat, then an interview with the manager. After that, there was a take-home assignment, which I really put a lot of extra effort into. Then, a team interview to discuss the assignment. Finally, an interview with the head of engineering. I made it to the team interview stage but unfortunately got rejected. I felt like I went above and beyond on the take-home, and then got rejected for one minor thing that wasn't perfect. It feels disproportionate to the effort and quality I put in, and I feel like my time was wasted. My advice is to make sure your assignment is absolutely flawless if you want to work there.

Confirmed questions1 question
  • Could you build an Elixir-Phoenix application to demonstrate your skills?
Remote logo
Remote

Software Engineering Team Lead

Engineering · more than a year ago

Lead Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding

I went through the initial 3 parts of the hiring: Recruiter screening, talking with the Engineering Manager, and a coding assignment to do at home. The first two were good experiences; they made me feel at ease and asked straightforward questions about how I do my work. The take-home exercise, however, could be better. It felt too extensive for someone not already familiar with Elixir, and it wasn't clear what aspects were being evaluated. For instance, it was unclear if the focus should be on Elixir best practices, flawless feature implementation, or code documentation. Knowing this upfront might have changed how I approached it. Although they said there's no time limit, it's tough for a candidate who really wants the job not to rush to finish quickly, worrying about others who might have started earlier.

Confirmed questions1 question
  • Could you complete a coding assignment at home?

Remote Software Engineer Interview Questions

Quoted word for word from Remote interview reports.

Out of Remote's core values, which one speaks to you the most and what's your reasoning behind that?

Read reports

Can you discuss the performance aspects and any edge cases related to the project?

Read report

What was your thought process for selecting that particular approach for the assignment?

Read report

Formats, difficulty and experience

Across all 15 Remote interview reports.

Interview formats

Behavioral 36.8%
Technical 34.2%
Coding 23.7%
Presentation 5.3%

Interview difficulty

Easy 20%
Average 66.7%
Difficult 13.3%

Candidate experience

Positive 46.7%
Negative 33.3%
Neutral 20%