Macquarie Group KDB Developer Interview Experience

Online Application —

I applied for a LinkedIn job opening for a KDB Developer role at Macquarie Group on 1st July 2026.

HR Prescreening Call —

HR called me on the 3rd of July, mentioning they wanted to send my resume to the Hiring Manager. They also asked me the following questions:

• My current salary & my salary expectations.
• Notice period.
• My main motivation to look for a new role.
• My experience with KDB & Front Office.
• If I am on a work visa or not.

Online Interview —

My first interview was a 60-minute interview scheduled on the 17th of July with one of the team members.

Get Megha’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in
• In-depth questions on my 3 CEPs — business + technical prospects.
• CEP subscriptions to CTP.
• In a live ticking CEP, how to store only the last 30 minutes of data in the CEP in-memory table.
• Types of joins in KDB.
• AJ & its properties, how it works internally, keys & tables for AJ.
• WJ and use cases.
• If I have worked on building Gateways — This was one of the requirements of the role.
• Attributes for in-memory vs disk tables.
• Types of attributes in KDB.
• Sym Files, Enumerations.
• Parse Trees.
• Why is PyKX faster than QPython?
• My experience in working with PyKX — because they had a PyKX project coming up soon.
• How to recover an RDB if a TP goes down/TP Log file is corrupted.

Results —

On 24th July, I got an email from the recruiter mentioning that even though my interview went well, they would not continue with my application.
The interviewer mentioned that if I had been selected, the next steps would usually be an automated aptitude round conducted for all roles at Macquarie & then the final round would be onsite.