Dayforce logo

Dayforce Fullstack Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Dayforce.

Showing 3 of 7
Dayforce logo
Dayforce

Full Stack Developer

Engineering · a year ago

Entry Easy Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Technical

This was the first interview, it was just a quick chat to talk about my background and experience, figure out when I could start, ask why I'm looking to leave my current job, and discuss salary expectations. It was only 20 minutes long, and they told me right after that I'd be moving on to the next round where they'd ask technical questions.

Confirmed questions1 question
  • When would you be able to start working for us?
Dayforce logo
Dayforce

Fullstack Developer

Engineering · more than a year ago

Mid Average Negative experience Decline offer 1 round
Interview process
Group Technical screen
Interview formats
Technical Coding Group

I had a group interview with three people where we looked at some code on StackBlitz that was either not working or incorrect. The interviewers weren't really sure what they wanted to ask and made up scenarios about the code. But these scenarios didn't have enough detail or a full use case, so it was hard to give good answers. They'd ask random questions and then follow up with a 'what if' that had nothing to do with the original code. Like, they showed a simple lambda for updating user data and then suddenly asked, 'What if I had six containers with lambdas like this?' even though containers were never mentioned. The questions felt random and disconnected. The interview was messy because it was hard to answer without knowing what the code was supposed to do, which only they knew. The technical part was okay, but it was clear the interviewers weren't ready. This was with the MX team. They didn't seem to have the skills for good interviews. I'd tell the MX team to prepare better and maybe hire someone experienced for interviews. I decided to stop after the second part. It made me wonder how they handle project management if interviews are this disorganized and unclear.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Dayforce logo
Dayforce

Full Stack Developer

Engineering

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Recruiter call
Interview formats
Behavioral Technical

i had a pre-call screening with HR which lasted for 1 hour. Then, a first technical interview with a software developer who seemed less experienced than me, also lasting 1 hour. Following that, a second technical round that was supposed to be 2 hours with two senior developers. However, they cut it short to 30 minutes because their manager was on leave, and they said I'd have a managerial round the next week. I thought I did really well, answering almost all questions and impressing the interviewers, but they didn't select me. The worst part is they didn't even send a rejection email after wasting my time; I had to email HR multiple times just to get a regret email saying I lacked strong skills. I'm not even sure what they were looking for.

Confirmed questions3 questions
  • What are your thoughts on OOPS concepts?
  • Can you tell me about your experience with React?
  • What are the SOLID principles and how do you apply them?

Dayforce Fullstack Engineer Interview Questions

Quoted word for word from Dayforce interview reports.

Can you explain the Histogram - water filling coding question?

Read report

Can you explain object-oriented programming principles?

Read report

Formats, difficulty and experience

Across all 7 Dayforce interview reports.

Interview formats

Technical 41.2%
Behavioral 23.5%
Coding 23.5%
Group 5.9%
System Design 5.9%

Interview difficulty

Easy 28.6%
Average 57.1%
Difficult 14.3%

Candidate experience

Negative 57.1%
Positive 42.9%