Intrado Software Engineer interview typically runs 3 rounds: two developers and a manager. It usually moves fast and is completed in about one interview, with a broad, fundamentals-focused format.
$88K
Avg. Base Comp
$88K
Avg. Total Comp
4
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Intrado is less interested in flashy system design than in whether you can explain the basics cleanly under time pressure. The strongest signal in the experience we saw was the emphasis on practical, day-to-day engineering knowledge: Unix commands, SQL/database concepts, and Java basics came up alongside a simple coding exercise. That mix tells us they’re screening for engineers who can move comfortably across the stack without getting lost in theory.
A recurring theme is how much weight they place on your current work. One candidate was asked to walk through the architecture of their project before the technical questions even started, which suggests they care about whether you can describe real implementation choices, not just recite concepts. We’ve also seen them probe for clarity on core SQL distinctions like join versus union, which is a good clue that precision matters here more than breadth. If you can answer directly and keep your reasoning tight, you’ll read as someone who can operate in a fast-moving, practical environment.
The other non-obvious pattern is the business side of the conversation. The manager closed with questions about motivation and what would make the candidate accept an offer, and the candidate noted that benefits and notice period were discussed very openly. That combination suggests Intrado is evaluating fit in a very pragmatic way: they want engineers who are technically solid, easy to work with, and realistic about the employment details from the start.
Synthetized from 1 candidates 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 Intrado process.
The interview was pretty straightforward and moved fast. I met with three people from the team: two developers handled most of the time, and the manager closed it out with a few general questions. The technical portion took about 50 minutes and felt like they were trying to cover a broad range of basics rather than go deep on any one area. They asked about Unix commands, SQL and databases, and some Java, so it was a mix of practical day-to-day knowledge and a little coding. One of the coding questions was to write a loop in any language to calculate the first 10 Fibonacci numbers, and they also asked the difference between a join and a union in SQL. That part was fast paced, so it helped to answer clearly and not overthink it.
Before the technical questions, they spent a little time on my current projects and asked me to explain the architecture of what I was working on. The manager section at the end was more general, including why I wanted to work there and what would make me accept an offer. The overall vibe was professional and smooth, though one thing that stood out from the process was that they were also very upfront about practical details like benefits and notice period. In my case, I didn’t get an offer, but the interview itself was fair and mostly focused on experience and fundamentals. I’d recommend being ready to talk through your current project architecture clearly, and brushing up on basic SQL concepts like joins versus unions along with simple coding exercises like Fibonacci or string reversal.
Prep tip from this candidate
Be ready to explain the architecture of your current project clearly, since that came up early. Also review basic SQL distinctions like join vs. union and practice writing simple loops or string logic quickly under time pressure.
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 Intrado
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Customer Orders | |
| String Shift | |
| Top 3 Users | |
| Comments Histogram | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Largest Salary by Department | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Raining in Seattle | |
| Average Quantity | |
| Job Recommendation | |
| Size of Joins | |
| Minimum Change | |
| P-value to a Layman | |
| Daily Retention Summary | |
| Address Schema | |
| Download Facts | |
| Permutation Palindrome | |
| Find the Index with Equal Left and Right Sum | |
| Google Maps Improvement | |
| Delivery Estimate Model |
Synthesized from candidate reports. Individual experiences may vary.
You meet with three people from the team: two developers and a manager. The conversation starts with your current projects and the architecture of what you have worked on, then moves into broad fundamentals across Unix commands, SQL and databases, and Java.
The technical portion is fast-paced and covers practical day-to-day knowledge rather than deep specialization. You may be asked to write a simple loop in any language, such as generating the first 10 Fibonacci numbers, and to explain basic SQL concepts like the difference between a join and a union.
The manager closes out the session with general fit questions, including why you want to work at Intrado and what would make you accept an offer. This part is more conversational and helps them gauge motivation and alignment with the role.
The team is upfront about logistics and employment details, including benefits and notice period. These topics come up as part of the same interview flow and give you a sense of the practical expectations if an offer were extended.