MarkLogic is now part of Progress. For up-to-date information, please see the Progress profile..
MarkLogic Software Engineer interview questions
Updated 10 Nov 2020
based on 3 ratings
Difficulty
Average
Experience
Very positive
How others got an interview
50%
Employee referral
Employee referral
50%
Campus recruiting
Campus recruiting
Interview search
3 interviews
MarkLogic interviews FAQs
Software Engineer applicants have rated the interview process at MarkLogic with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 100% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 7 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at MarkLogic overall takes an average of 7 days.
Common stages of the interview process at MarkLogic as a Software Engineer according to 1 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
Multiple phone interviews that included some technical questions. Most were frontend related questions. Overall good interview process and very nice interviewers. No online assessment given. Would interview again. Interview process was overall really great.
I applied through university. The process took 1 week. I interviewed at MarkLogic
Interview
Phone interview. First I introduced my self, then I was asked some questions about my projects and basic knowledges. Finally there is a simple algorithm question. Overall, it is not hard, and interviewer very friendly.
Interview questions [1]
Question 1
Basic questions about OS, database, concurrent programming
I applied through an employee referral. I interviewed at MarkLogic in Feb 2018
Interview
Applied on Jan 25th, responsed on 26th and a phone interview on Feb 5th. The interviewer is nice and kind. Questions are related to basic CS knowledge and data structure.
Interview questions [1]
Question 1
OS thread, process, page fault
TCP/UDP
C++ knowledge, 'static' key word, memory leak.