AKUNA CAPITAL Python Developer interview questions
based on 29 ratings - Updated Oct 15, 2023
Averageinterview difficulty
Mixedinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
29 interviews
Viewing 6 - 10 of 29 Interviews
AKUNA CAPITAL interviews FAQs
Python Developer applicants have rated the interview process at AKUNA CAPITAL with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 39% positive. To compare, the company-average is 41.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Python Developer roles take an average of 13 days to get hired, when considering 23 user submitted interviews for this role. To compare, the hiring process at AKUNA CAPITAL overall takes an average of 18 days.
Common stages of the interview process at AKUNA CAPITAL as a Python Developer according to 23 Glassdoor interviews include:
Presentation: 50%
Phone interview: 31%
Other: 19%
Here are the most commonly searched roles for interview reports -
3 Hackerrank questions pertaining to situations that could be presented on the job. The first and third questions were quite easy (albeit never finishing), but question 2 was confusing as it required question 1 to be finished and working. Never got past the first interview, so not sure about after.
Interview questions [1]
Question 1
Questions about obtaining metainformation from stock data.
I applied online. The process took 2 months. I interviewed at AKUNA CAPITAL in Mar 2021
Interview
Started with a Coding Assessment. Leetcode Medium to hard level.
Followed by a screening. Mainly asking about features of Python Language.
Finally a two hour virtual onsite. One on coding and one on object oriented programming.
I applied online. The process took 3 weeks. I interviewed at AKUNA CAPITAL (Sydney) in Mar 2021
Interview
Applied online. Received online coding challenge (HackerRank algorithm) in 2 days. Once that's done, an internal recruiter contacted me and arranged an online paired coding test with an Akuna engineer. The coding test was still HackerRank algorithm, but I was expected to explain my thoughts while solving it. A day later, I received an invitation to come on-site for the final interview. Before coming on-site, I was asked to provide past salaries and references.
The final round consisted of 3 interviews. The first one was with an engineer on a HackerRank system design problem. The second interview was with a team lead on technical experiences and a non-coding problem solving challenge. The third interview was a chat with a company lead with no pre-set topic.
Received en email of rejection about a week after the interview. I reached out to the recruiter for some feedback but they were reluctant to provide any.
Overall the interview was well-organised. My feedback are 1.) I think there is an over-emphasis on using HackerRank. I would like to see more questions on real-world problems from production. 2.) I don't think the interview with the company lead is a good indicator of culture fit for a software engineer. Things a software engineer should care about is very different from what a company lead should.