Programme Analyst applicants have rated the interview process at KUBRA with 2.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 30% positive. This is according to Glassdoor user ratings.
Candidates applying for Programme Analyst roles take an average of 10 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at KUBRA overall takes an average of 14 days.
Common stages of the interview process at KUBRA as a Programme Analyst according to 4 Glassdoor interviews include:
One on one interview: 29%
Skills test: 21%
Phone interview: 14%
Group panel interview: 14%
Background check: 14%
Personality test: 7%
Here are the most commonly searched roles for interview reports -
I applied through college or university. I interviewed at KUBRA
Interview
Easy. They conduct a simple 30 min phone interview initially. They then call you in for a one to one interview with team leads, manager and maybe director. Usually HR gives a test before you meet with the team leads. They review it with you.
Interview questions [1]
Question 1
behavioral questions, simple test on programming logic
Fair, slightly technical but you will not use the coding experience for a majority of the job.Majority of the job is troubleshooting across multiple teams. Questions regarding cookies, sessions, C# in the interview.
Support Clients. utility company.
Participate in the Software Development Life Cycle (SDLC) including Analysis, Design, Implementation, Testing and Maintenance with Agile Methodology.
Build and maintain efficient, reusable, and reliable code.
Design test procedure, create test data and automate testing.
Prepare technical documentation of development modules to be used as part of product release documentation.
I applied online. The process took 1 week. I interviewed at KUBRA (Toronto, ON) in Dec 2021
Interview
Phone screening with HR first, then teams interview with team lead and tech leads 50% technical questions and 50% behavioural questions, overall it wasn't too difficult as long as you got the basics