e-Core logo

e-Core Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
53.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at e-Core.

Showing 3 of 13
e-Core logo
e-Core

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding

The process had three interviews. First was with a Headhunter, just to get general info about me, my XP, etc. It was really trivial. Part of this chat was in english to check my english skills. Second was with the team manager, he explained the position and the everyday job better, and deepened on my technical and previous jobs experience (some questions also in english). He also gave me a really simple technical test (how to remove duplicates from a list) to solve on my machine while sharing my screen. Third and last phase was a live coding technical interview, fully in english with the team tech lead. He asked me things related to the challenge and general questions about the job. The challenge wasn't hard, solved easily using Java core features. He asked some questions on why I used this or that, what I would do to solve a different problem, how I would add some new feature or deal with a corner case. All three phases were pretty smooth, the three interviewers were very gentle, understanding and willing.

Confirmed questions8 questions
  • Tell me about the last challenge you faced at your previous job and how you resolved it.
  • What exactly is JWT?
  • Can you explain the distinction between Authorization and Authentication?
e-Core logo
e-Core

Software Developer Intern

Engineering · more than a year ago

Intern Easy Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel Group
Interview formats
Behavioral Technical Coding

The first interview was with the Recruiter and it was quite interesting, a good exchange, she asked relevant questions even in the English conversation. She mentioned that the company embraces diversity, that they respect differences, etc. There was a coding challenge and then an interview with the company professional + recently hired intern, which was also calm and interesting. The last stage was a video call with the finalists, the employees seem very happy and satisfied with what they do and this truly enchants those who wish to be called. Something that caught my attention was precisely the discourse of promoting diversity in the company, however, unfortunately, it seemed to me that in practice it might be different. On the panel there were men and women, all white, from the south (or southeast), it was mentioned in this interview that there are PCD collaborators on staff but... it struck me as strange not to see the discourse happen in practice.

Confirmed questions2 questions
  • Apply agile methodology in practice
  • About technology, state three facts, one of them false
e-Core logo
e-Core

Software Engineer

Engineering

Mid Average Positive experience Accept offer 7 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Presentation Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design Presentation

First up was an HR interview, lasting about 20-30 minutes. Then, I had a technical interview with the local team lead for about an hour. After that, there was a take-home code challenge due in 3-4 days. Next, I had a technical interview with the client I'd be working with, around 30 minutes. Then came an architectural interview where I had to present a high-level design for an app, about 40 minutes. The challenge for this was emailed about a week prior, it's a tough one, so be ready. Following that, there was a cross-functional interview with a senior software engineer and a product owner. Finally, a management interview. The whole process was very polite and transparent, especially from e-Core HR.

Confirmed questions3 questions
  • Can you describe a past project you're proud of, and be ready for follow-up technical and soft skill questions?
  • Can you describe a past project you're not proud of, and be ready for follow-up technical and soft skill questions?
  • What's your approach to onboarding a new team member?

e-Core Software Engineer Interview Questions

Quoted word for word from e-Core interview reports.

What is the difference between HTTP 400 and 500 status codes?

Read reports

Can you explain the difference between authentication and authorization?

Read report

Can you explain the distinction between Authorization and Authentication?

Read report

Implement a function to determine the winner of a Shipit/hackathon round.

Read report

Formats, difficulty and experience

Across all 13 e-Core interview reports.

Interview formats

Technical 35.1%
Behavioral 29.7%
Coding 27%
Presentation 5.4%
System Design 2.7%

Interview difficulty

Easy 7.7%
Average 76.9%
Difficult 15.4%

Candidate experience

Negative 30.8%
Positive 53.8%
Neutral 15.4%