New hires do not say where onboarding failed until the 90-day review | SaaS & Technology

What it costs you today

Your onboarding program looks solid on paper. By the time new hires feel comfortable enough to give honest feedback, it is 90 days in and the damage is done. Ramp time is longer than it should be because of avoidable confusion in week two, but nobody told you about it at the time.

How RadRoot is used here

RadRoot sends new hires a five-question adaptive check-in at the end of each week for the first four weeks. Short enough to feel lightweight, structured enough to surface real friction. "I did not understand how to access X" leads to "is that resolved or still blocking you."

The file you would upload

A BambooHR - New Hires Report export. One row is one new hire record. RadRoot reads the whole row, so every question can name something the person already knows is true.

Employee ID	Employee Name	Job Title	Department	Start Date	Work Email	Manager Name
VTX-2401	Marcus Chen	Software Engineer	Engineering - Platform	2026-01-06	marcus.chen@vertexanalytics.example.com	Diana Okoye
VTX-2402	Priya Sharma	Product Designer	Product	2026-01-06	priya.sharma@vertexanalytics.example.com	Luke Morrison
VTX-2403	Jordan Blake	Software Engineer	Engineering - Backend	2026-01-13	jordan.blake@vertexanalytics.example.com	Sarah Kim
VTX-2404	Elena Rodriguez	Data Scientist	Data & Analytics	2026-01-13	elena.rodriguez@vertexanalytics.example.com	Tom Bradshaw
VTX-2405	Cameron Wright	Software Engineer	Engineering - Frontend	2026-01-20	cameron.wright@vertexanalytics.example.com	Diana Okoye

First 5 of 20 rows, first 7 of 12 columns. RadRoot interviewed the software engineer on each row, and 8 of 20 answered.

One interview, exactly as it ran

Six options every time, including the ones that reflect badly on whoever sent it. Each question was written after the answer above it landed.

Q1You started on December 16 and just finished week four. How quickly were you able to start contributing to the codebase?

·I started contributing to small tasks in my first week
✓I started reviewing code in week two and had my first PR merged in week three
·I was able to pick up my first ticket by the end of week two
·I have been reading code and asking questions but have not contributed much yet
·I am still waiting on access so I have not been able to do much
·I have not started contributing yet because I am still getting up to speed on the domain

Q2That is solid progress. How long did it take to get access to production after you started?

·I had access within the first few days
·It took about a week
·I got access by the end of week two
✓It took about ten days, which felt longer than I expected
·It took almost three weeks and I had to follow up multiple times
·I still do not have full production access

Q3You have a buddy assigned according to the system. How helpful have they been when Diana is not around?

·Very helpful, they check in regularly and answer questions quickly
·Pretty helpful, they respond when I reach out
·Somewhat helpful, but they are often busy with their own work
·Not very helpful, they are hard to reach most of the time
✓They were assigned but I only heard from them once in the first week and then nothing
·They have not reached out at all and do not respond when I contact them

Q4Since your buddy was not engaged, how did you find answers during week two?

·I asked other engineers on the team and they were helpful
·I posted in Slack and got answers from whoever was available
✓I read through documentation and asked questions during team standups
·I mostly waited until Diana was free to answer my questions
·I searched online and pieced things together as best I could
·I did not find many answers, I just did my best to move forward

Q5How often did you need Diana for something urgent when she was unavailable?

·Almost never, she has been very available
·Once or twice but it was not a big deal
✓A couple of times, but I usually figured it out on my own eventually
·A few times, and it did slow me down a bit
·Pretty often, which has been frustrating
·Very frequently, and it has been a major blocker

The verdict it produced

Written for whoever ran the campaign. The respondent never sees it.

Isaiah ramped reasonably well, merging his first pull request in week three. But the ten-day wait for production access felt long, and his assigned buddy only contacted him once before going silent. He compensated by using documentation and standups, and when Diana was unavailable he solved problems himself. He succeeded despite the system, not because of it, and that kind of self-rescue is not scalable across all hires.

access delay negative medium confidence

Isaiah waited ten days for production access, which he found longer than expected.

buddy system gap negative high confidence

Isaiah was assigned a buddy who contacted him once in week one and then disengaged completely.

ramp friction positive medium confidence

Isaiah began reviewing code in week two and merged his first pull request in week three.

week-two clarity mixed medium confidence

Isaiah navigated week two by reading documentation and asking questions in standups.

manager availability mixed low confidence

Isaiah needed Diana urgently a couple of times when she was unavailable and eventually solved issues himself.

See this on your own data

Fifteen minutes, screen to screen. We run your real question through RadRoot while you watch, and you leave with the follow-up it wrote and a price.

Book 15 minutes Answer one yourself