
Praxent Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 43 interview experiences · FREE TO READ
Which role are you interviewing for?
11 roles · 43 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Praxent.
Delivery Director
I got to the very last interview, but Praxent told me they had already filled the position before it happened. They asked if I still wanted to do the final interview, and I said yes—and I’m really happy I did. The whole process was clear, nice, and felt human. HR kept me in the loop always, told me what to expect, and I never had to wonder what was going on. This communication is way better than at many other places where you interview for weeks and then get ghosted. Even though the job was taken, I still have a great impression of Praxent. It was different from most interview experiences, and I’d definitely like to interview with them again.
- Can you share an experience of leading a complicated delivery involving multiple teams? Describe how you managed conflicting priorities and maintained client trust throughout the project.
ABM Campaign Content Strategist
My interview process at Praxent, while challenging and thorough, was really good at exploring my background and seeing how it fit the role. Laz, who I mostly communicated with, was great at giving detailed info on what to expect so I could prep well. Each interview had a different goal, and Laz clearly explained what they were about. For instance, before my biographical interview, Laz told me they'd go through each part of my career and ask about what I was hired to do, my biggest wins and losses in that period, and so on. I was also told to get ready to talk about 'stories and examples that mirror the types of problems [someone in that role is likely to] face day to day.' It was so refreshing to get specifics on what examples to share, as interviewing can be such a frustrating guessing game. You know, the worst is having the exact experience a company wants but not being able to explain it well or being unsure what they're asking. That wasn't a problem here! As we went on, the questions got more specific and deeper, which I expected. For the last interview, I presented two past campaigns (anonymized) to show my skills. The questions and talks were intense, but I felt they were valuable. By the end, I felt the team really understood what I could bring. It was tough, but in a good way, like a great workout where you know you'll feel it but you're getting stronger. Even though it wasn't easy, I could explain my career accomplishments in detail. It felt good knowing I gave it my all. They really live by their CAN/DO values, which became clear throughout. Many companies just have values on paper, but at Praxent, they're real. I was expecting them to be like other tech companies that prioritize money over values, but they haven't. So, if you want a challenge but also support and a place to thrive, I highly recommend Praxent.
- Can you tell me what you were hired to do during this phase of your career?
- What were your greatest achievements during this career chapter?
- What were the most difficult aspects of this chapter of your career?
Software Engineer
So the interview process for me was like four parts. First, there was an HR chat, you know, standard stuff but they really wanted to hear about my strengths and weaknesses, like what I'm good and not so good at. Then came a technical interview, for me it was C# and Angular. They really dive deep into the tech stack you're interviewing for, asking lots of conceptual questions. Like, if it's C#, be prepped to explain OOP and other C#-specific stuff. After that, someone went over my resume, asking about my past roles, why I moved on, and what went well. They're looking for stories about your work, how you handled challenges, that sort of thing. The last interview was with the client, which I guess isn't always part of it. This one felt more relaxed, I think it was mainly for them to check my English. Overall, it felt like a solid interview, no whiteboard stuff, but they definitely want you to be able to talk smoothly about the concepts in your main tech stack.
- Can you discuss your strengths and weaknesses?
- What are your thoughts on OOP concepts within C#?
- Could you elaborate on C# interfaces?
Technical Director
The whole thing took about two months, which felt a bit long, but I guess it happens sometimes, especially around the holidays. Most of the interviews were pretty standard, a mix of technical stuff and seeing if I'd fit in. The last one, though, was something else. There were two people on the call. One just sat there the whole time, didn't say a word. The other one was mostly eating soup, head down, and clearly wasn't paying attention, even asking me to repeat questions. It made me feel really undervalued, like they didn't care. Then, at the very end, they dropped the bomb that there wasn't actually an open position, they were just interviewing for a potential future role. It felt really dishonest to drag someone along for months for a job that didn't even exist, and then just send a generic rejection. Definitely avoid this company.
- Can you share an example of your most significant failure in a leadership role?
Praxent Interview Questions
Quoted word for word from Praxent interview reports.
“Could you define what a linter is and explain its functionality?”
Read reports →“Can you explain the distinction between an interface and an abstract class?”
Read reports →“Can you explain the different keywords used for declaring variables in Javascript and their distinctions?”
Read reports →“Could you define encapsulation in the context of OOP?”
Read reports →“How do package management tools operate and what is their benefit?”
Read report →“What is your understanding of dependency injection in C#?”
Read report →“Can you explain the difference between horizontal and vertical scaling?”
Read report →“Can you explain the difference between synchronous and asynchronous operations?”
Read report →“Describe how you would deploy a spring service using AWS.”
Read report →Formats, difficulty and experience
Across all 43 Praxent interview reports.