
LINE Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 18 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at LINE.
Front End Engineer
Had a nice interview with the lead of the team I applied to. They asked some good questions about UI/UX and React. I actually learned a lot about front-end development trying to find answers for the questions afterward.
- What were your thoughts on their main application interface?
Frontend Developer
When you apply, HR sends you an email with a basic markdown survey about yourself. You need to reply with the markdown converted to PDF. After a few days, you'll get a simple assignment involving basic JavaScript DOM manipulation, which should be straightforward if you've worked with web JavaScript, especially pre-jQuery. You have 50 minutes to submit it. Then, they'll ask for your availability for a technical interview, which has 2 sessions. They'll ask about your background, your previous assignment, security, basic JavaScript, algorithms, and more. Some interviewers might not have strong English skills, and you might encounter some unclear questions, so be ready for that.
- Tell me about basic JavaScript.
- Can you explain some algorithms?
- What can you tell me about your background?
Frontend Developer
I applied for a Frontend Developer job at LINE in Thailand. The interview process had three main stages. The first was a general interview with the Hiring Manager. The second was a take-home test where I had to build a website using Vue.JS. They gave me an API, but it didn't work, so I had to get the raw JSON data from HR. The third stage involved reviewing my code and adding new features, which included live coding. This round was supposed to have the Team Lead join, but they didn't, so HR scheduled another round for me. In the fourth round, I was unexpectedly put into an interview for a Fullstack Team role, even though I applied for Frontend Developer. I only found out during the interview itself, and I wasn't happy about it because I didn't agree to this change. Initially, they said it was just a general interview to check for culture fit and asked about my passion for programming. I was honest about my reasons, but I suspect they might have wanted a more 'ideal' answer, suggesting that sometimes you might have to lie to satisfy interviewers. They also asked me to do live coding again, this time to set up an API with Express.JS. I failed this part because I wasn't prepared for backend tasks, and it's not my strong suit. On the positive side, the HR team was very professional and responsive, always answering my questions and helping me follow up on the results. The main issue was being interviewed for a Fullstack role when I applied for Frontend, without my consent or input. It makes me question why we choose specific positions initially if they aren't considered later. I hope they take this feedback to improve their confusing process, so other candidates don't feel like they've wasted two months due to an unprofessional approach.
- What is your motivation for pursuing a career as a programmer?
- How would you design a system for the LINE melody service?
- Can you live code the initiation of an API?
LINE Frontend Engineer Interview Questions
Quoted word for word from LINE interview reports.
“What are basic maps?”
Read reports →“How do you add simple events to buttons?”
Read reports →“Can you explain the difference between `var`, `let`, and `const`?”
Read reports →“In javascript, how would you find the maximum profit given the problem input?”
Read reports →“How can a tree be optimized?”
Read report →“How would you design a system for the LINE melody service?”
Read report →“What are your favorite books?”
Read report →“Can you live code the initiation of an API?”
Read report →“Can you explain callback functions?”
Read report →Formats, difficulty and experience
Across all 18 LINE interview reports.