Taro Logo

Engineering Team Leader Interview Experience - Japan

May 1, 2023
Neutral ExperienceNo Offer

Process

Interview process is as they state it on their website. However there are a few things that could use improvement: TL;DR don't trust the (well intentioned but maybe misinformed) recruiters.

  1. Recruiter made things confusing by giving incorrect and confusing information. //Example A: They said "you will get a non-elixir assignment, with 10-20% in Elixir code at most", when in actuality the assignment was still 100% in Elixir//Example B: They said "for team interview no need to prep anything other than reflecting on the assignment". I spent all my time prepping that and in the team interview most of the time was spent on my experiences and behavioral things

  2. The non-elixir assignment takes way too long for those who are inexperienced with the language. I'm an experienced dev (10 years experience) and it took more than 10 hours. Learning the framework, syntax, paradigm, setting up env, then actually working on the assignment is immensely time consuming. Remote should either narrow down the scope of the assignment, or tell the candidate what to focus on (e.g. refactoring, unit testing, clearing errors, DB design)

Questions

Tell me about your experience working with the product side.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Remote Engineering Team Leader role in Japan.

Success Rate

0%
Pass Rate

Remote's interview process for their Engineering Team Leader roles in Japan is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Remote's Engineering Team Leader interview process in Japan.

Remote Work Experiences