Candidates describe a Tyler Technologies engineering interview that opens with a recruiter or HR screen, then moves to a technical panel or group interview. Reports lean toward PL/SQL and SQL, with behavioral questions throughout.
$98K
Avg. Base Comp
$120K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe a Tyler Technologies engineering interview that is practical rather than puzzle-driven, though the technical content clearly varies by role. The four reports here come from two Software Engineer applicants, an Oracle PL/SQL Developer and a DevOps Intern, so read them as a range of experiences rather than one fixed loop.
The process starts with a recruiter or HR conversation. One Software Engineer applicant described a 15 to 20 minute call covering "tell me about yourself" and "why Tyler Technologies", with no coding. Another was asked to walk through a challenging situation from a previous role. The first of those applicants was then invited to a group interview that mixed technical and behavioral questions, and did not receive an offer.
The heaviest technical content is database-focused. The other Software Engineer applicant faced a three-person panel on packages, triggers, views, stored procedures and functions. The next round was seven SQL and PL/SQL questions in 60 minutes, delivered through Notepad, covering functions, bulk collections and query optimization. That candidate did not advance. The Oracle PL/SQL Developer described a two-hour technical session with three panelists: resume and conceptual questions on triggers, indexes, SQL tuning and UNION versus UNION ALL, then hands-on queries and procedures. That candidate also heard nothing after a positive HR email.
The DevOps Intern had a lighter experience: an online assessment, then a virtual interview built around explaining Object Oriented Programming, discussing projects and answering teamwork questions. That candidate received an offer. If your team works with Oracle, practice writing PL/SQL without an IDE, and keep concrete project examples ready.
Synthesized from 5 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 Tyler Technologies process.
I got recruited directly by Tyler Technologies, which was a pretty good sign off the bat. The process moved fairly quickly — after an initial recruiter conversation, I took on an online assessment and then moved into a virtual technical interview. The whole thing felt pretty low-pressure compared to what I'd heard about other companies' processes.
The technical interview itself wasn't a typical LeetCode grind. Instead, the interviewer asked me to explain Object Oriented Programming, which turned out to be more about demonstrating my understanding of foundational concepts rather than solving algorithmic problems. The focus seemed to be on my communication and how well I could break down ideas, not on optimizing time complexity. My interviewer was genuinely nice, which made the conversation feel natural rather than adversarial. They seemed interested in learning how I think about code organization and design principles.
Beyond the technical question, there was a lot of discussion about my resume — projects I'd worked on, internships, and how I'd handled challenges in those roles. The interviewer also threw in standard behavioral questions about teamwork, how I deal with difficult situations, and whether I could step into leadership roles. It felt like they were trying to get a sense of who I am as a person and how I'd fit into their team, not just whether I could reverse a linked list in under 20 minutes.
Overall, the experience was straightforward and encouraging. I accepted the offer because the process itself signaled that Tyler Technologies values communication and practical skills over algorithm memorization, and the interviewer's approachability made me feel like I'd actually enjoy working there.
Prep tip from this candidate
Focus on being able to explain foundational OOP concepts clearly rather than grinding LeetCode — Tyler Technologies seems to prioritize understanding and communication over pure algorithmic problem-solving. Have concrete examples from your resume ready to discuss in depth, as they'll dig into your past projects and internship work.
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 Tyler Technologies
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| Prime to N | |
| Rolling Bank Transactions | |
| String Shift | |
| Top 3 Users | |
| Customer Orders | |
| Raining in Seattle | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| Minimum Change | |
| Flight Records | |
| Download Facts | |
| Upsell Transactions | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| First Touch Attribution | |
| P-value to a Layman | |
| Job Recommendation | |
| Google Maps Improvement | |
| Recurring Character | |
| Find Bigrams | |
| Find the Missing Number | |
| Scrambled Tickets |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe an opening conversation with a recruiter or HR. One Software Engineer applicant described a 15 to 20 minute call with "tell me about yourself" and "why Tyler Technologies" and no coding. Another was asked to walk through a challenging situation from a previous role. Prepare a concise motivation answer and a couple of project stories.
Two candidates describe three-person technical panels. A Software Engineer applicant was asked about PL/SQL packages, triggers, views, stored procedures and functions. An Oracle PL/SQL Developer spent the first hour on resume questions and conceptual topics: triggers, indexes, SQL tuning, and UNION versus UNION ALL. Concrete project examples helped.
Formats differed. One Software Engineer applicant faced seven SQL and PL/SQL questions in 60 minutes in Notepad, with functions, bulk collections and query optimization, and did not advance. The Oracle PL/SQL Developer wrote SQL queries and procedures in the second hour of the panel. Another Software Engineer applicant described a group interview mixing technical and behavioral questions.
