Chronicled logo

Chronicled Interview Questions
& Process

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

Based on 11 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
27.3% Positive experience

Which role are you interviewing for?

5 roles · 11 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Chronicled.

Showing 4 of 11
Chronicled logo
Chronicled

Site Reliability Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Technical Coding

After going through three interview rounds back in March 2023, I was told the job was put on pause. Then on April 18, they said they wanted to move forward. But since then, it's been radio silence from them, even though I've tried reaching out twice. It's been pretty disappointing not hearing back.

Confirmed questions3 questions
  • What's your approach to rolling back a database deployment?
  • How would you handle uploading large files to S3 from different regions cost-effectively?
  • Can you explain how to undo a Kubernetes deployment?
Chronicled logo
Chronicled

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 7 rounds
Interview process
Phone screen Technical screen Onsite Background check Offer
Interview formats
Coding Technical System Design Behavioral

it started with 2 rounds of phone tech interviews. onsite was as others, total 5 rounds: 3 code interviews (1 blockchain, 1 database, 1 server/front end), 1 architecture, 1 QA, 1 followup resume discussion with CTO

Confirmed questions8 questions
  • Discuss database design principles.
  • Explain your approach to functional programming in coding.
  • Coding focused on blockchain.
Chronicled logo
Chronicled

Recruiter

HR · more than a year ago

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

Applied online and got a quick call back for a 15-minute chat to overview my background. Then there was an onsite interview that lasted 2 hours which was a bit concerning because I thought they'd ask more about processes and metrics before bringing someone onsite. I met with some senior folks: CEO, CTO, VP of Product, and the Director of People Ops. About 10 minutes into my talk with the CTO, I realized they were looking for someone more like a 'technical recruiter'. I was upfront that while it hasn't been my main focus, I could get up to speed. The CEO interview felt a bit strange as he didn't make eye contact and took notes on my resume. The interview overall was just okay, but they could have handled rejections better. If your brand isn't well-known, I suggest giving candidates a call to thank them for their time to make it more personal instead of sending a standard rejection email, because I'll definitely write a Glassdoor review reflecting my experience.

Confirmed questions3 questions
  • What is your approach to recruiting?
  • What can you tell me about Chronicled?
  • Can you describe the most challenging role you've recruited for?
Chronicled logo
Chronicled

Software Engineer

Engineering

Senior Average Negative experience No offer 8 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen
Interview formats
Technical Technical Technical Technical Technical Technical Technical Technical Technical

After seven 45-minute interviews, plus an initial long chat with a recruiter, and getting good feedback each time, I was told that they reevaluated their team's technical needs and wouldn't move forward at that time. So, what was mostly a good experience turned out to be a huge waste of time and effort (and the interviewers' too!). No clue if they get that or care; I would have appreciated it if they'd ended the process sooner.

Confirmed questions3 questions
  • Discuss problem solving approaches.
  • Explain your testing strategies.
  • Describe your experience with functional programming.

Chronicled Interview Questions

Quoted word for word from Chronicled interview reports.

Could you write a function that accepts a lambda function and provides an output, structured in a map-reduce format?

Read reports

How would you handle uploading large files to S3 from different regions cost-effectively?

Read reports

What's your approach to rolling back a database deployment?

Read report

Can you explain the theoretical underpinnings of how various technologies function?

Read report

Formats, difficulty and experience

Across all 11 Chronicled interview reports.

Interview formats

Technical 56.7%
Coding 20%
Behavioral 20%
System Design 3.3%

Interview difficulty

Easy 18.2%
Average 72.7%
Difficult 9.1%

Candidate experience

Negative 63.6%
Neutral 9.1%
Positive 27.3%

Reports by job function

Engineering 8
Analytics 1
HR 1
Operations 1