Kronos Incorporated Interview Experience | On-Campus Internship
Question Details
Kronos came to our campus to hire interns as well as full-time employees. The profile they were hiring for was a software development engineer . For the interns, they were...
Full Details
Kronos came to our campus to hire interns as well as full-time employees. The profile they were hiring for was a software development engineer . For the interns, they were providing with a 2-month long internship. It had CGPA criteria: Above 7.5.
Round 1 Aptitude and programming Test: It included a one hour long the aptitude and programming test. This test was conducted on the hackerearth platform. Aptitude test: It consisted of 10 questions(multiple choice and one mark each with no negative marking) of which some were of basic maths and reasoning while others were of basic c++ and java programming. These questions were really easy to crack if one has basic knowledge of programming. Programming test: It included two questions(10 marks each and wrong submissions weren't considered and it also included partial marking). These two questions were of a very basic level of competitive programming. Not to forget: They only provided us with 3 languages to code in i.e java, C++ and C. So, those who used to code in python had no options left for themselves. question 1: It was a basic implementation of a stack with conditions. question 2: It was a cakewalk type question in which he had to check the stream of input and print out either yes or no. Both the questions were easy to crack. 8 students were selected from 80 students who applied for the internship, for the
next round.
Round 2 A ( technical + HR ) interview : In this interview, the resume plays a key role as the recruiters do not expect much technical knowledge about the core subjects like operating systems or database management systems. They are more interested in the type of skills one has developed in the past two years of college. They do expect a basic knowledge of data structures as you have already cleared the programming round. The candidate should be able to defend everything written on the resume. Remember: Never mention false things in the resume or else you would not be able to defend it in the interview. In the technical part of my interview, I was asked these questions: a) what is an API? b) what is a rest API? mention some types of APIs. c)what is the difference between a rest and a soap API? d)what is a session? what is a cookie? These questions were asked to me on the basis of my resume. I was given a basic reasoning puzzle to solve. I had participated in the smart India hackathon so I was asked to share my experience and my work as a team player. Then the questions related to the HR part started which included : a)why did I drop for one year after class 12th, before starting my graduation. b)What are my interests except for coding or studying? Am I into extracurricular activities? c) How many family members do I have? d)A question related to the pre-placement talk they conducted before the recruitment process. The interview ended on the note that did I had any questions for them related to Kronos for them. 2 students were selected out of 8 for the position.
About This Question
This is a reported interview question from a kronos interview for a eng manager role (intern level) during the phone screen round reported in 2019.
It covers the following topics: Sql, Networking, Stack Queue, Os, Stack .
Difficulty rating: Easy
Topics
About Kronos Interview Reports
This question was reported by a candidate who interviewed at Kronos. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Kronos are the higher-signal extractions to take from this report.
For broader preparation context, the Kronos interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Kronos reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Kronos Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Kronos reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.