1st Phone interview, essentially a meet and greet. Second phone interview, somewhat technical question. Followed later by a take home coding assignment, where you get to choose between two different assignments and are given a week to do this. 3rd interview is a 4 hour onsite interview. 4 hours onsite interview: (specific details left out due to NDA and not sure what can talk about) 1-peer review / pair coding assignment where they want you to explain and then to change your code. (first few minutes speaking about get to know you type questions) 2- (get to know you, ask more questions about background, situations with previous work group) Technical question about making client server more efficient. 3- (more get to know you, ask previous work experience, behavioral question,) System Design 4 - ( more get to know you, behavioral question) followed by Data-structure question (not sure if this was the intention)? What impressed me most was the positive vibe that everyone gave. Most people seemed down to earth and friendly. Especially the recruiting coordinator. What was odd I thought was that there were essentially 3 different white-boarding questions with zero high level or conceptual questions about software engineering/programming languages. (a little rant, feel free to ignore) Each hour segment started off with get to know you and ask questions and or about previous job experience. A good chunk of time was spent on behavioral and non technical questions at the beginning of each hour, rather than leaving most time for technical questions. The technical questions were a little open ended and seemed like it should take more time to discuss the problem space, so if you didn't know what they wanted right away it was not going to end well. Many common interview questions weren't asked, so I felt I had spent a lot of time preparing for questions and not for what they wanted(it's too bad they didn't ask about finally in a try block because they weren't going to be tricky on that one! but nope. There were no backend/java questions, oop, polymorphism , abstraction vs interface, design pattern, no questions on sorting, or searching algorithms... I had read on some other glassdoor reviews for tyler tech that they might ask something like given a sorted array, make this into a binary tree. Nope, these were more open ended questions that could have more than one right answer. And wasn't prepared to talk about json values being passed to webpages/xml as webdesign and xml definitely was not on my resume. I even spent time reviewing SQL, but none of those questions were asked either. :( :( For the one system design question, I started out writing notes on paper and was prompted to stop and go to the whiteboard. This segment of the interview was the most odd to me, because I thought for system design, a lot of the time should be spent getting to know about the input, output, constraints, goal, users etc before even attempting to go to the whiteboard. But the interviewer seemed to not want to answer these questions and or gave very vague answers, like maybe, or that's a possibility, let's allow for that. So rather than being able to narrow the problem space down and make it more concrete, asking questions ended up being slightly detrimental, made the problem space bigger. It's possible she wanted to give you free reign to do what you want as long as it made sense. However, that gave off the impression that she thought it was a very simple question and I should just get to white-boarding right away (and maybe annoyed that I was asking so many questions, or they weren't necessary for the problem space). Furthermore, I felt like the other questions, when it came to what they wanted also written on the whiteboard, they wanted us to get right to it... The 4th segment when it came to white-boarding question, they wanted us to code right away. And this is nearing the end of the 4th hour of a interview process.