C3.ai New Grad Interviews: 25 Experiences (Part 1 of 2)
- Company
- C3.ai
- Reports
- 20 interview reports
- Level
- New Grad
- Stages
- OA → Phone screen → Onsite
C3.ai new grad SWE reports from 2023–2025 show a recruiter or talent screen, then a loop of four or five rounds mixing coding, design and resume talk.
At a glance
- Process: a short recruiter or talent-acquisition call (01, 03), then a loop of four or five rounds (02, 04, 05). Candidate 02's five rounds ran from Oct 17 to Nov 18, 2024: a hiring manager, a tech lead, a senior engineer, a manager, and the hiring manager again. Candidate 04 had three algorithm interviews and one on past experience.
- Asked recently: a lock-wheel search, a thread-safe queue and a union-find problem (02), a LeetCode Hard and a system design round (05). Every current report included resume or motivation questions, from bosses in past jobs (01) to ranking job-offer factors (02).
- Difficulty: candidate 05 solved the Hard but ran out of time to write the faster version. Candidate 02 felt good after every round and was still rejected.
- Practise first: Fewest Turns to Open a Wheel Lock, Design a Concurrent Multi-Producer Multi-Consumer Queue and Why do you want to work at C3.ai?
Coverage: 25 C3.ai new grad and early-career reports across two parts. This part holds the 20 Software Engineer reports (New Grad, Early Professional, Early Career, Entry Level) from the U.S., India and Mexico. Five are current, from Oct 2023 to Jul 2025: three from Mexico, one from San Francisco, and a 2025 graduate interviewing for a platform-backend role. The other 15 (2014 to Jun 2023) are history and stay out of the counts. Part 2 holds five reports from other roles.
In this series
- Part 1 (current): Software Engineer, 20 reports, with the overview
- Part 2: FDE, Solution Engineer, data and full-stack roles — 5 reports from 2019–2023, one per role
What came up
All five current reports spent time on the candidate's own background or motivation. Coding and design show up in the three that reached a loop.
| Topic | Reports | Last seen |
|---|---|---|
| Resume, past work and motivation | 5 of 5 | Jul 2025 (report date) |
| Live coding | 3 of 5 | Nov 2024 |
| Design (system design, a concurrent queue) | 2 of 5 | Nov 2024 |
| Graph search (lock-wheel BFS, union-find) | 1 of 5 | Nov 2024 |
Rows: resume 01–05; coding 02, 04, 05; design 02, 05; graph search 02.
Questions we found
These tables cover the five current reports. Older questions are indexed at the start of History.
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| LeetCode 752 style, Fewest Turns to Open a Wheel Lock | 1: 02 | Nov 2024 |
Low-Level Design (LLD/OOD)
| Question | Reports | Last seen |
|---|---|---|
| Design a Concurrent Multi-Producer Multi-Consumer Queue | 1: 02 | Nov 2024 |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| Your experience with bosses in previous jobs | 1: 01 | Jul 2025 (report date) |
| Rank the factors you consider in a job offer | 1: 02 | Nov 2024 |
| Tell me about your most challenging project | 1: 02 | Oct 2024 |
| How do your long-term goals align with C3.ai? | 1: 03 | Aug 2024 (report date) |
| Why do you want to work at C3.ai? | 1: 05 | Oct 2023 (report date) |
Technical discussion
| Question | Reports | Last seen |
|---|---|---|
| How do you approach unit testing? | 1: 02 | Oct 2024 |
5 candidate timelines from 2023–2025
01: Guadalajara recruiter screen that stayed short
Report date: Jul 2025 · Role: Software Engineer – Early Professional · Location: Guadalajara, Mexico · Result: No offer
Recruiter screen
- A quick call about past jobs, projects, and why this position.
- How the candidate had worked with bosses in earlier jobs.
The report stops after this call.
02: Five rounds for a job that wanted one to four years
Report date: Nov 23, 2024 · Role: Software Engineer, platform-backend (2025 new grad, referred) · Result: Rejected
Round 1 (Oct 17): hiring manager
- A resume walk-through and some behavioral questions.
Round 2 (Oct 25): tech lead
- Questions on the resume, including technical details of past work.
- How they go about unit testing.
- Their most challenging project.
Round 3 (Nov 14): senior engineer
- A short self-introduction.
- A queue that many threads can use safely at the same time. For practice, try the concurrent queue design.
- A union-find problem. The report doesn't say which one.
Round 4 (Nov 14): manager
- Introductions, then time for the candidate's own questions.
- A search over lock-wheel codes, close to a well-known problem: Fewest Turns to Open a Wheel Lock.
Round 5 (Nov 18): hiring manager
- Detailed questions about their projects.
- Rank the factors you weigh when choosing between offers.
The candidate noticed the experience requirement only after applying and thought it explained the long loop. Rounds 3 to 5 were booked together. A rejection email came the Saturday after round 5, with no feedback. They felt good after every round and wondered whether a May graduation date hurt them.
03: Thirty minutes with talent acquisition
Report date: Aug 2024 · Role: Software Engineer – Early Professional · Location: Guadalajara, Mexico · Result: No offer
Talent acquisition screen (about 30 minutes, Teams)
- Background, skills, weaknesses, and what they knew about the company.
- How their long-term goals line up with C3 AI.
04: Six months, a no-show, and an offer
Report date: Mar 2024 · Role: Software Engineer – Early Career · Location: Zapopan, Mexico · Result: Offer
Loop
- Three data structures and algorithms interviews.
- One interview about past experience.
It took about six months. Interviews were cancelled several times, and once nobody showed up; two weeks after an email to HR, a reschedule link arrived.
05: Four rounds, including system design
Report date: Oct 2023 · Role: Software Engineer · Location: San Francisco, CA · Result: Rejected
Loop (four rounds)
- Four rounds for a new grad, one of them system design.
- A LeetCode Hard: solved, optimization discussed, but no time to write the faster version.
- Behavioral: why do you want to work at C3.ai?
A rejection followed.
History (before Oct 2023)
Fifteen Software Engineer reports from 2014 to Jun 2023. Most of the named coding questions are here, from HackerRank tests, phone screens and onsite days.
Questions in these older reports
The Reports column names the entries; counts cover these 15 reports only.
Online tests
| Question | Reports | Last seen |
|---|---|---|
| Sort by Frequency, Then Value | 2: 16, 17 | Dec 2020 (report date) |
| LeetCode 1220 style, Count Vowel Strings With Follow Rules | 2: 16, 17 | Dec 2020 (report date) |
| Photo Album Insert Order | 2: 16, 17 | Dec 2020 (report date) |
| Largest Square Sub-Grid Within a Sum Limit | 1: 08 | Jan 2023 (report date) |
| Prefix Scores With the Running Maximum | 1: 08 | Jan 2023 (report date) |
| Count Palindromic Subsequences of Length K | 1: 11 | Mar 2022 (report date) |
| "Valid BSTs": Count Distinct Binary Search Trees | 1: 11 | Mar 2022 (report date) |
Live coding rounds
| Question | Reports | Last seen |
|---|---|---|
| Movie Schedule for Maximum Enjoyment | 1: 07 | Jan 2023 (report date) |
| LeetCode 1004 style, Longest Run of Ones After Flipping k Zeros | 1: 11 | Mar 2022 (report date) |
| LeetCode 347, Top K Frequent Elements | 1: 14 | Feb 2021 (report date) |
| LeetCode 1027, Longest Arithmetic Subsequence | 1: 14 | Feb 2021 (report date) |
| Sort events by a custom value with priority markers | 1: 15 | Jan 2021 (report date) |
| Item Prices From Material Costs | 1: 16 | Dec 2020 (report date) |
| LeetCode 134 style, Gas Station Loop | 1: 16 | Dec 2020 (report date) |
| Does the first player have a forced win? | 1: 16 | Dec 2020 (report date) |
| Adjacent-Key Lock Patterns | 1: 20 | Feb 2014 (report date) |
Design and behavioral
| Question | Reports | Last seen |
|---|---|---|
| BQ: Why do you want to work at C3.ai? | 2: 06, 16 | Jun 2023 (report date) |
| System design: Design a Collaborative Code Editor | 1: 13 | Apr 2021 (report date) |
| System design: how would you scale up a past project? | 1: 14 | Feb 2021 (report date) |
| LLD: Design a Library Circulation System | 1: 16 | Dec 2020 (report date) |
06: A Hard problem graded on thinking, not finishing
Report date: Jun 11, 2023 · Role: Software Engineer – New Grad · Location: India · Result: No offer
Round 1
- A LeetCode Easy/Medium problem.
Round 2
- A LeetCode Medium, a Hard and a system design question, each with about five minutes of behavioral.
- The candidate's read: nobody expects the Hard solved; they want to hear the approach.
- Behavioral question: why are you interested in C3.ai?
07: A movie-scheduling VO that ran out of time
Report date: Jan 14, 2023 · Role: Software Engineer (new grad) · Result: Rejected after the first VO
Phone screen
- A top-k question, which they called easy.
VO round 1
- Each movie has an id, a last day it can be watched, and an enjoyment score. Plan which movies to watch within a given number of days for the highest total enjoyment. Practice: Movie Schedule for Maximum Enjoyment. Our version assumes one movie per day, since the report gives no running times.
They needed a hint partway through. The solution worked, but there was no time left for edge cases. An automated rejection came the next day, so the second VO never happened.
08: Platform OA, two questions in 70 minutes
Report date: Jan 14, 2023 · Role: Software Engineer, platform (new grad) · Result: Not stated
Online assessment (2 questions, 70 minutes)
- Given a square grid of numbers and a limit, find the largest k for which every k × k block sums to at most the limit. Practice: Largest Square Sub-Grid Within a Sum Limit.
- For each prefix of an array, go left to right and add the current largest value to each element. A prefix's score is the sum of the result, mod 10^9 + 7; return every prefix's score. Practice: Prefix Scores With the Running Maximum.
The second one ran a little over time. The author shared the prompts as screenshots of worked examples, so both statements above are rebuilt from those examples.
09: Passed every technical round, then "not a team match"
Report date: May 2022 · Role: Software Engineer New Grad · Location: Redwood City, CA · Result: Rejected
HackerRank
- Fairly easy; every test passed.
Three technical rounds
- All LeetCode Medium: two array questions, one stack question.
- One interviewer wanted one exact answer, and the code tool wouldn't scroll.
Leadership rounds
- Planned with the team's engineering manager and a VP; the VP was away for two weeks, so two senior engineering managers stepped in.
- The first manager went through the resume point by point.
- As the second round started, the recruiter called: not a fit for the team. That interview never happened.
Six rounds counting the HackerRank.
10: Rejected the evening of the tech screen
Report date: Mar 2022 · Role: Software Engineer New Grad · Location: U.S. · Result: Rejected
HackerRank
- Two medium-to-hard questions.
Technical screen
- A long talk about the resume and the company, with technical questions on resume items.
- One easy-to-medium coding question.
An automated rejection arrived that same evening.
11: Career-fair applicant, palindromes in the OA
Report date: Mar 2022 · Role: Software Engineer · Location: U.S. · Result: Rejected
The candidate applied through a campus career fair.
HackerRank (2 questions)
- A math / DP question. The question list calls it only "Valid BSTs", likely counting distinct BSTs.
- Count palindromic subsequences of length k.
One-hour call with a senior software engineer
- About 30 minutes on previous projects.
- A LeetCode Medium, first O(n²), then linear with hints. Likely the longest run of ones with up to k zeros flipped; questions aren't mapped to rounds.
12: Late interviewers and a BFS
Report date: Sep 2021 · Role: Software Engineer (New Grad) · Location: U.S. · Result: Rejected
Online assessment
- Three questions in 90 minutes, the same set an earlier reviewer described.
Technical rounds (planned: three × 45 minutes)
- Small talk and resume, then about 30 minutes of coding.
- Topics: a BFS over a matrix, and traversing a map.
- The first interviewer was upbeat; the second seemed already decided. Every interviewer was late, and the third round never happened.
13: Super day, two managers, then the CTO
Report date: Apr 17, 2021 · Role: Software Engineer – New Grad · Location: U.S. · Result: Offer accepted
Online assessment, then a 30-minute technical interview
Super day: three back-to-back technical interviews
- Algorithms, system design, and some front-end concepts.
- Design question: how would you build a live, collaborative code-sharing app?
Behavioral rounds
- Two back-to-back sessions with department managers.
- A one-on-one with the CTO.
Each answer came within the week, scheduling was flexible, and the offer was very competitive.
14: Top K on a stream, and an offer the candidate turned down
Report date: Feb 2021 · Role: Software Engineer – Early Professional · Location: Redwood City, CA · Result: Offer declined
Technical phone screen (1 hour)
- Most of the hour went to one past project.
- Top K Frequent Elements. Follow-up: what if the numbers arrive as an endless stream?
Technical onsite (three 45-minute interviews, plus one hour half technical, half behavioral)
- System design: how would you scale up one of your past projects? Open-ended.
- Longest Arithmetic Subsequence: a slow start, then the optimal answer.
- A basic design question and an easy algorithm question.
Behavioral onsite
- Two 30-minute interviews with team leaders.
15: Custom event sorting
Report date: Jan 2021 · Role: Software Engineer, Entry Level · Location: U.S. · Result: Rejected
Online assessment, then phone interview
- Sort events by a custom value, where secondary event markers change their priority. The marker rules aren't given.
A further interview was hinted at; a rejection came instead.
16: The full late-2020 loop, round by round
Report date: Dec 2020 · Role: Software Engineer – Early Professional · Location: U.S. · Result: No reply after two weeks
HackerRank (3 problems in 2 hours: easy, medium, hard)
- Sort by frequency, then by value.
- Count Vowels Permutation, the hard one.
- The photo album problem, the easy one.
45-minute video interview
- Price each item from the materials it needs, given quantities and material prices.
Three 45-minute interviews, with 15-minute breaks
- First: can you drive once around all the gas stations? Then make it faster; the candidate went from a simple approach to the optimal one.
- Second: previous work, where you want to be, why C3.ai. Then a hard problem with about 30 minutes left: does the first player of a two-player game have a forced win? The game isn't named.
- Third: design and implement a library where a user can check out a book up to 3 times, plus a few smaller rules.
One interviewer's connection kept dropping; the candidate saw it as a one-off.
17: Passed every test, rejected within the hour
Report date: Nov 2020 · Role: Software Engineer New Grad · Location: U.S. · Result: Rejected
HackerRank (3 LeetCode medium/hard questions)
Every test passed. Within an hour, an email said the score wasn't in the passing range.
18: A pigeonhole problem and a silent interviewer
Report date: Sep 15, 2020 · Role: Software Engineer New Grad · Location: U.S. · Result: No offer
Phone interview
- A LeetCode Hard whose optimal solution needs the pigeonhole principle.
- The interviewer gave no hints and barely spoke.
Three onsite rounds are mentioned but not described.
19: Pick a track first
Report date: Sep 2020 · Role: Software Engineer New Grad · Location: U.S. · Result: No offer
Track choice
- First, choose one of three tracks: two client-facing roles and one platform role.
Online assessment (90 minutes)
- One question.
Phone interview (30 minutes, two engineers scheduled)
- One of the two engineers didn't show up.
- Somewhere in this process came a medium-to-hard sorting question.
20: Android lock patterns, from 2014
Report date: Feb 2014 · Role: Software Engineer New Grad · Location: U.S. · Result: No offer
Online test (90 minutes)
- An online compiler with test cases.
Phone interview
- Generate every Android lock-screen pattern of length 5 where each digit sits next to the previous one and no digit repeats.
Patterns across the reports
- One HackerRank set kept coming back. Candidates 16 and 17 got the same three problems in late 2020: sort by frequency then value, Count Vowels Permutation, and the photo album problem. The Forward Deployed Engineer in Part 2 (23) saw the same three in 2022.
- A LeetCode Hard in a live round. Four loops from Sep 2020 to Oct 2023 had one (05, 06, 16, 18). Candidate 06 felt it was about the approach; 05 ran out of time to write the faster version.
- Your own projects take real time. A coding round opened with, or became, a talk about past work in 10, 11, 14 and 16: half an hour in 11, most of the screen in 14. In the newest loop (02), three of five rounds centred on the resume and projects.
- Leadership rounds come last. Candidates 09, 13 and 14 had a final stage with managers, team leaders or the CTO. Candidate 09 ended there on team match; 13 and 14 got offers.
- Scheduling trouble. Cancellations, no-shows, late interviewers, a broken code tool or a bad connection come up in 04, 09, 12, 16 and 19.
- Rejections without feedback. Candidates 02 and 07 heard nothing about why, and so did the Solution Engineer in Part 2 (21).
Common questions
How many rounds is the C3.ai new grad interview?
Four or five in the current loops: five over a month for candidate 02, four for 04 and 05. Older loops (2020–2022) were usually a test, a screen, then three back-to-back technical interviews and a leadership stage (09, 13, 14, 16).
Does C3.ai give new grads an online assessment?
None of the five current reports mention one. Older reports describe HackerRank tests of two or three questions in 70 minutes to 2 hours (08, 12, 16).
How long does the C3.ai hiring process take?
It varies a lot. Candidate 04's process took about six months, with cancellations and a no-show. Candidate 02's five rounds ran from Oct 17 to Nov 18, with a rejection the Saturday after. In 2021, candidate 13 heard back within a week at each step.
How hard is the C3.ai new grad interview?
Candidate 05 got a LeetCode Hard in a four-round loop. In older reports, tests ran medium to hard (10, 17) and live Hards appeared in 06, 16 and 18; candidate 06 believed the approach mattered more than finishing.
What to practise
- Fewest Turns to Open a Wheel Lock. The only named coding task in a current report (02, Nov 2024).
- Design a Concurrent Multi-Producer Multi-Consumer Queue. The same loop's senior-engineer round (02).
- Why do you want to work at C3.ai? Asked in 05 (Oct 2023) and in two older loops (06, 16); every current report had motivation or resume questions.
- Sort by Frequency, Then Value, Count Vowel Strings With Follow Rules and Photo Album Insert Order. The HackerRank set named in three tests from 2020 to 2022 (16, 17, and 23 in Part 2). No newer test report names its questions.
Keep practicing
- Problems from this part: Fewest Turns to Open a Wheel Lock (02), Movie Schedule for Maximum Enjoyment (07), Largest Square Sub-Grid Within a Sum Limit and Prefix Scores With the Running Maximum (08), Count Palindromic Subsequences of Length K, Count Distinct Binary Search Trees and Longest Run of Ones After Flipping k Zeros (11), Top K Frequent Elements and Longest Arithmetic Subsequence (14), Item Prices From Material Costs and Gas Station Loop (16), the three test problems above (16, 17), and Adjacent-Key Lock Patterns (20).
- Design: Design a Concurrent Multi-Producer Multi-Consumer Queue (02), Design a Collaborative Code Editor (13) and Design a Library Circulation System (16), plus the C3.ai system design bank.
- C3.ai question banks: the coding bank and the behavioral bank (sign-in needed).
- C3.ai overview: the C3.ai interview page.
- More reports: the Experience feed.
In this series
- Part 1 (current)
- Part 2
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.