Credit One Bank Systems Engineer Interview Questions
& Process

I applied through their website and after about two weeks, they contacted me for a phone interview. This initial call, lasting around 45 minutes, is designed to be challenging. They focus on a specific technical area, like VMWare troubleshooting for me, and relentlessly question you until you admit you don't know the next step. They then switch topics and repeat the process. Following this, it takes another couple of weeks to schedule an in-person interview, which typically occurs during standard business hours, meaning you'll likely need to take time off work. It's advisable to take the whole day off, as they don't seem to rush and made me wait about 25 minutes past my scheduled 1:00 PM interview time. The in-person interview involved a three-person panel who subjected me to similar intense questioning, this time focusing on Group Policy and deployment. They again pushed a scenario until I had to concede I didn't know the specific answer, followed by some trick questions. The panel members who weren't Windows or VMWare specialists asked easier questions. A significant concern is their hiring practice: you must first work as a W4 contractor for at least 90 days, with the stated reason being it's easier to let people go. This raises worries about potential perpetual contract work or easy termination post-project. They also mentioned working around 50 hours weekly, plus one weekend a month, and I'm concerned about how they'd react if one only worked 50 and not 60 hours. Information on benefits was scarce and difficult to obtain, with details on insurance providers, premiums, and coverage being withheld. When I inquired about career advancement, the response was dismissive, suggesting one would need to 'really impress them,' implying excessive work hours. Upon declining the offer, the call was abrupt, and I was hung up on before finishing my explanation, indicating a lack of interest in feedback.

The interview process started with a phone interview with 2-3 IT people. These guys were pretty intense and seemed to enjoy asking super obscure IT questions from what felt like an MCSE book, focusing on things most sys admins rarely use, like Windows Server Backup instead of enterprise solutions. A big concern they brought up was the expectation of after-hours and weekend work, with multiple on-call periods each month. When I responded neutrally, they sarcastically emphasized it's part of IT and pressed on how quickly I'd respond to night calls. They seem to have high turnover due to this, and it felt like they'd work you to death and look for any excuse to let you go within the initial 3-month contract period, which is their standard hiring method before potentially going permanent. It feels like an unsustainable and unhappy environment.

Had a personality meeting to get to know me, not much technical knowledge was really needed to get the role. Nice managers and the process was very smooth overall.