Get tailored insights about working at fi360 in one quick step.
fi360 interview questions
based on 2 ratings - Updated Sep 6, 2018
Easyinterview difficulty
Very positiveinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
2 interviews
fi360 interviews FAQs
Glassdoor users rated their interview experience at fi360 as 50% positive with a difficulty rating score of 2 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Manager and Software Engineering Team Lead rated their interviews as the hardest, whereas interviews for Manager and Software Engineering Team Lead roles were rated as the easiest.
The hiring process at fi360 takes an average of 30 days when considering 2 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 Manager had the quickest hiring process (on average 30 days), whereas Manager roles had the slowest hiring process (on average 30 days).
A technical phone screen lasted for about 20 minutes. The questions were standard baselines for C#, ASP.NET, and SQL. Several terms from the Scrum framework were used but it did not sound like an agile product development environment.
The onsite interview consisted of three panels and lasted just shy of two hours.
The first was technical in nature consisting of the Solution Architect and Lead Developers. Several of the questions asked were the same as from the phone screen, even being asked by the same individual. Another panelist asked only one question and otherwise seemed disinterested in participating. Statements that deadlines were of great importance, efforts were centered around quarterly releases, lead roles generally spend 50% "leading" (meaning mostly attending meetings), unit tests and automation are not the norm, developers primarily work in isolation, tasks are assigned by seniors to juniors, and output being the primary metric highlighted the Taylor mentality.
Technical Product Analysts and the Quality Assurance manager began the second panel by stating that one was the beginning of the process and the other was the end, serving as another indicator of the waterfall approach. There is no risk-based approach to prioritizing the minimal test automation and there is a poor implementation of cases for data-based operations. Non-collaborative, throw it over the wall, hand offs were the exit and entry points for each phase of work. The latest project was presented as creating a monolith instead of a more maintainable and extendable architecture.
Closing the interview was a brief session with the Development Manager and VP. The discussion included culture. Learning and professional development have not been a priority, but they may be putting some effort into that in the next few quarters. It was stressed that the process is not the Agile(tm) method but included various aspects, which were actually traditional project meetings branded as Scrum events, further exposing misunderstanding of the agile philosophy.
Most of the people were pleasant and friendly, but the environment is not one of collaboration and learning.
I applied online. The process took 4 weeks. I interviewed at fi360 (Pittsburgh, PA) in May 2011
Interview
It was okay. To be honest, it was a bit too easy. That can be expected of that company. They are still very young, but running as if they have been around for years. It's odd to work for a organization which still focuses on top-down-management.