Lexicon is now part of Endava. For up-to-date information, please see the Endava profile..
Lexicon interview questions
based on 51 ratings - Updated Feb 8, 2024
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
47%
Recruiter
Recruiter
21%
Applied online
Applied online
15%
Employee referral
Employee referral
9%
Campus recruiting
Campus recruiting
4%
Other
Other
2%
In person
In person
2%
Recruitment agency
Recruitment agency
Interview search
51 interviews
Viewing 1 - 5 of 51 Interviews
Lexicon interviews FAQs
Glassdoor users rated their interview experience at Lexicon as 100% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Software Engineer and rated their interviews as the hardest, whereas interviews for Software Engineer and roles were rated as the easiest.
The hiring process at Lexicon takes an average of 3 days when considering 1 user submitted interviews across all job titles. Candidates applying for Software Engineer had the quickest hiring process (on average 3 days), whereas Software Engineer roles had the slowest hiring process (on average 3 days).
Interviews are typically conducted in three stages or processes. 1st is the assignment round then 2nd is the technical round, and then we have the HR cultural round
then you have a salary discussion round
Interview questions [1]
Question 1
tell me about yourself, what you have done in your previous company, and how was your experience
First interview was a video call, usual job questions, had a specific interest in my experience as a consultant. Technical interview, was half a pairing interview & then a technical Q&A.
Interview questions [1]
Question 1
Technical interview was in react. The problem was around a fake movie theatre site, and calling APIs for currency conversion.
I applied through a recruiter. The process took 2 weeks. I interviewed at Lexicon (Sydney) in Feb 2023
Interview
A recruiter from Lexicon reached out to me via Linkedin and we got in a conversation for what role is about, what the interview looks like and expectations, etc. The next stage of the interview is a live coding challenge where they sent you a coding challenge repo (this has many version in many programming languages) beforehand ( no action required ) to read and get familiar with before the interview - This is what I like best as it give you more time to prepare and really get to know the codebase. I got about 1 week to prepare for the live coding. In the live coding interview, two senior engineers gave me an extension on a feature of the codebase and asked me to complete in about 30-45min after that we discussed about how the code could be improved, how I work in the current company and consulting experience. The third and last interview is with the engineering director. It was a chill conversation, more like get to know kinda thing ( some behavioural and past experience were questions were also asked )