LINE logo

LINE Backend Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at LINE.

Showing 3 of 5
LINE logo
LINE

Backend Engineer

Engineering · a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Take home Technical screen Group Recruiter call
Interview formats
Coding System Design Technical Behavioral

So the interview process had a few steps. First, there was a coding test that took about 3 hours, and it included 3 LeetCode medium problems, an LRU cache question, and a system design question. Then, before the main interview, I had to do an online algo test within 30 minutes. The interview itself focused on reviewing that test and my background. After that, there was an online culture fit test. Finally, there was an HR call. I didn't pass the culture fit test.

Confirmed questions1 question
  • Can you explain the difference between multi-threading and multi-processing?
LINE logo
LINE

Backend Developer

Engineering · more than a year ago

Mid Easy Negative experience No offer 2 rounds
Interview process
Technical screen Technical screen Onsite
Interview formats
Coding Technical Behavioral

I applied for the Fukuoka office. The first part was a 3-hour online coding test with 4 general data structure and algorithm questions like leetcode, and one small system design question that had minimal requirements. The next part was a 1-hour online assessment followed by a 2-hour video interview with 2 backend engineers and an interpreter. The assessment had 6 questions on basic backend dev knowledge and one on evaluating the time complexity of search algorithms. The video interview was kind of a mess. The interpreter didn't know tech stuff and couldn't translate well. I only saw one interviewer, the other one was hidden. The worst part was they were interviewing me for a backend monitoring job, not the backend developer job I applied for. They asked me 'what command would you use if the system went down?' without any context, and when I asked for clarification, they just repeated the question. I didn't get an offer, but I wouldn't have taken it anyway. The engineers didn't seem passionate about their jobs.

Confirmed questions2 questions
  • General leet code questions were asked.
  • General leet code questions were asked.
LINE logo
LINE

Back End Engineer

Engineering · more than a year ago

Entry Average Neutral experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Coding Technical

I applied through a recruiter. The first interview will involve a coding test and the second interview will focus on programming concept questions. The interviewer will then discuss your answers after you complete the test.

Confirmed questions1 question
  • What is the time complexity of a given algorithm?

LINE Backend Engineer Interview Questions

Quoted word for word from LINE interview reports.

Can you explain the difference between multi-threading and multi-processing?

Read reports

Can you describe a situation that demonstrates your attitude?

Read report

Formats, difficulty and experience

Across all 5 LINE interview reports.

Interview formats

Coding 33.3%
Technical 33.3%
Behavioral 20%
System Design 13.3%

Interview difficulty

Easy 20%
Average 60%
Difficult 20%

Candidate experience

Positive 60%
Negative 20%
Neutral 20%