Get tailored insights about working at Citilabs in one quick step.
Citilabs interview questions
Updated Jul 20, 2018
based on 4 ratings
Difficulty
Easy
Experience
Very positive
How others got an interview
75%
Applied online
Applied online
25%
Campus Recruiting
Campus Recruiting
Interview search
4 interviews
Citilabs interviews FAQs
Glassdoor users rated their interview experience at Citilabs as 100% positive with a difficulty rating score of 1.33 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Traffic Data Analyst and Data Entry Specialist rated their interviews as the hardest, whereas interviews for Traffic Data Analyst and Data Entry Specialist roles were rated as the easiest.
The hiring process at Citilabs takes an average of 8 days when considering 3 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for Data Entry Specialist had the quickest hiring process (on average 6 days), whereas Traffic Data Analyst roles had the slowest hiring process (on average 14 days).
Took about a week. Included a pre-screening phone call and a few preliminary emails. The process concluded with a video interview since I wasn't local. An average interview experience overall.
Interview questions [1]
Question 1
Rate yourself (on a scale from 1-5) on your abilities in R and Python.
I applied through college or university. The process took 2 weeks. I interviewed at Citilabs (Tallahassee, FL) in Jan 2014
Interview
I applied online through my university job posting website, I got an interview a few days later and started working 2 weeks after that. The hiring manager was very nice and it was professional and also casual at the same time.
I applied online. The process took 1 day. I interviewed at Citilabs (Tallahassee, FL) in Dec 2013
Interview
1 on 1 interview with CEO, questions were about resume and skills for the job as well as experience, then he explained the goals of the project we were to work on