DigiCert software engineer interviews, as three candidates describe them, mix JavaScript and frontend fundamentals with an open-ended take-home. Here is what each report covered and how to prepare.
$153K
Avg. Base Comp
$175K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
The three DigiCert reports here come from different levels and describe different formats, so they are best read separately rather than as one fixed process.
A senior-level candidate described a first technical round of two medium JavaScript data structures and algorithms questions: comparing objects and implementing memoization for a function. They shared code through JS Fiddle and said the round tested fundamentals rather than system design. A principal-level candidate described two technical rounds of open-ended frontend questions on React, vanilla JavaScript and CSS, with performance optimization and security considerations. A hiring manager round was planned but never happened for them. The third candidate, at the software engineer level, went through a recruiter conversation, a talent partner screening call and a take-home API project. The task was to build an application that stores structured data and retrieves it through an API.
Practice writing clean JavaScript under time pressure, and be ready to explain frontend performance and security trade-offs aloud without waiting for the interviewer to confirm your answers. For the take-home, ask for the deadline in writing and leave room for storage and endpoint design decisions. All three candidates reported no offer, and two said they received little feedback, so ask what the next step is at the end of each conversation.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Digicert process.
I interviewed at DigiCert for a Senior Software Engineer role and went through what was supposed to be two technical rounds followed by a managerial round. The first technical round consisted of two medium-level DSA questions, both JavaScript-based. One focused on object comparison logic, and the other was about implementing memoization for a function. I solved both problems and shared my code via JS Fiddle with the interviewer. The questions tested problem-solving and JavaScript fundamentals rather than system design or architecture, which I found a bit surprising for a senior-level position. I felt confident walking out—I'd worked through the logic clearly, explained my approach, and delivered working code. Two days later, I called HR to follow up. She said I wasn't moving forward. I called again, hoping for feedback, but got the same answer with no real explanation. That's where things got frustrating. I put genuine effort into preparing and executing well during the interview, yet the feedback loop was essentially nonexistent. It felt less like a rigorous evaluation and more like the hiring bar kept shifting.
Prep tip from this candidate
If you interview at DigiCert for this role, be prepared for JavaScript-focused DSA questions on objects and functional programming patterns like memoization. More importantly, try to get specific feedback during or immediately after each round—the lack of clarity on why candidates are rejected after passing technical questions suggests asking pointed questions about what they're looking for can help clarify expectations.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Digicert
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report that a recruiter explained the steps and scheduled the rounds. One candidate said scheduling happened quickly. Another was then handed to a talent partner. Confirm the number of rounds and any take-home deadline at this stage.
One software engineer candidate described a screening call with a talent partner that went fine but repeated questions already answered earlier. It may help to keep a short written summary of your background ready so you can answer consistently and quickly.
Two candidates describe technical rounds. A senior candidate reported two medium JavaScript questions on object comparison and memoization, shared through JS Fiddle. A principal candidate reported open-ended React, JavaScript and CSS questions on performance and security, with little interviewer engagement.
One candidate received an open-ended take-home to build an application that stores structured information and exposes it through an API, with freedom over storage and endpoints. The deadline arrived shorter than the recruiter had described, so confirm the timeline in writing before accepting.
Two candidates described a planned final or managerial round, which neither reached. All three reported no offer, and two described limited feedback. It may be worth asking directly what the evaluation focuses on and what the next step is.
