Software Developer applicants have rated the interview process at Knak with 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 55.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 28 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Knak overall takes an average of 25 days.
Common stages of the interview process at Knak as a Software Developer according to 3 Glassdoor interviews include:
Personality test: 33%
Phone interview: 33%
Skills test: 33%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Knak in Feb 2026
Interview
The interview process consisted of HR, the Hiring Manager, and a Technical Interview. Everything up to a technical part was fair, while they were prolonging the interview lingering it more than they should. I was not told what to prepare and which IDE to have installed. Was asked questions being expected to know someone else's code by seeing it first-time. The only pressure was from not knowing what to expect, they were causal, but expected a lot.
Interview questions [1]
Question 1
Do the systems design of the mail-sending service via AWS or whatever you choose.
It was five rounds. The first was with a recruiter. The next was a manager. The next was an exercise. The next was a team interview with peers where we went over the exercise. The final stage was leadership. Everyone was awesome!
Interview questions [1]
Question 1
Give us an example of something you built recently.
I applied online. The process took 4 weeks. I interviewed at Knak (Ottawa, ON)
Interview
Standard multi step interview process. Things were great, but the CEO needs to know about what people do in their free time. The answer impacts an offer. If you have a side project, even if it’s not the same industry, don’t disclose it in the process. Incredibly intrusive.
Interview questions [1]
Question 1
Standard coding challenge on a timer. Questions were more math focused than programming. Unnecessary for the role.