CAI logo

CAI Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 10 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
80% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at CAI.

Showing 3 of 10
CAI logo
CAI

Senior Software Developer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

Applied for a senior technical role online. Recruiter reached out. Had a 45-min phone screen with the person in the role I'd be replacing. We talked about my current projects, tech decisions, and general application design approaches. It wasn't super technical. Later that day, got an invite for an on-site that week. The on-site was a panel with my potential manager, the person I'd replace, a senior person from another department, and a mid-level dev from my team. It felt more like a natural discussion than a Q&A. My manager asked behavioral/client-focused questions. The senior folks asked detailed technical questions about past projects. The mid-level dev and I just chatted briefly. Got a provisional offer a few days later, pending drug test and background check.

Confirmed questions6 questions
  • What's your strategy for dealing with a challenging client who ignores your technical guidance?
  • Can you share an instance where a significant technical decision you made proved incorrect? What steps did you take to rectify it?
  • Could you provide examples of technical challenges you've faced and how you addressed them?
CAI logo
CAI

Software Developer

Engineering

Entry Easy Negative experience No offer 5 rounds
Interview process
Technical screen Group Presentation Panel Offer
Interview formats
Technical Coding Group Presentation Behavioral

They do this five day 'working interview' via zoom, 9-5, Mon-Fri. At the end, they have a 'feedback' session where they try to trash your performance and find fault. It's really messed up because you're doing good work like a full-time employee but not getting paid. They'll lie about you being late even if you're on time and leave when you're supposed to, or not share your screen when asked. They try to gang up on you during the 'working interview' to make up for the good work you did all week. If they don't like something, they don't tell you, but then use it against you later, which is their failing. They'll note down any little thing you say that could hurt your chances and bring it up when it suits them. It's a really bad, unthoughtful interview process at a company that seems poorly run. They make you do pointless things like explain how to make a peanut butter sandwich or answer trivia questions designed to trick you, just to fill the 40 hours of unpaid 'interview' time. You also go through videos on workplace inclusivity, standards, and etiquette, with tests afterwards. You have to create an elevator pitch about your background and goals. Then, you write about your work-style and how it compares to others. On Friday, you work with a group to create a Google webpage presentation for management and do mock scrum meetings, taking turns as Scrum Master and answering questions about your daily progress and any problems.

Confirmed questions1 question
  • What would be your plan for financial support if you were not offered this job?
CAI logo
CAI

Software Engineer

Engineering

Mid Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

It was for a PennDot position. First, a recruiter called to ask general background questions and check my interest in the role. Then, there was a technical screening, and I also learned more about the work from team members of 2-3 different teams and the director.

Confirmed questions4 questions
  • Questions about SQL.
  • Questions about APIs.
  • Questions about SSRS.

CAI Software Engineer Interview Questions

Quoted word for word from CAI interview reports.

What's your strategy for dealing with a challenging client who ignores your technical guidance?

Read report

What would be your plan for financial support if you were not offered this job?

Read report

Describe your methodology for architecting new software applications.

Read report

Can you share an instance where a significant technical decision you made proved incorrect? What steps did you take to rectify it?

Read report

Can you tell me about your experience with COBOL, CICS, and VSAM?

Read report

Formats, difficulty and experience

Across all 10 CAI interview reports.

Interview formats

Technical 39.1%
Behavioral 39.1%
Coding 13%
Group 4.3%
Presentation 4.3%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Positive 80%
Neutral 10%
Negative 10%