OutSystems logo

OutSystems Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 64 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
84.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at OutSystems.

Showing 3 of 64
OutSystems logo
OutSystems

Senior Software Engineer

Engineering · half a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Background check Technical screen Technical screen
Interview formats
Behavioral Technical Coding System Design

I applied on Workday. The recruiter reached out. They explained the whole process after the first contact. There are 4 interviews in total, including the first recruiter call. Each interview is about 1 hour long. The stages are: Recruitment, Hiring Manager (for cultural fit), Tech (testing tech knowledge, C#, and a pair programming exercise), and another Tech interview focusing on System Design and a practical exercise.

Confirmed questions7 questions
  • Tell me about cultural fit.
  • How would you describe your experience with C#?
  • Can you explain Solid principles?
OutSystems logo
OutSystems

Software Engineer

Engineering · nearly a year ago

Entry Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Take home Presentation
Interview formats
Behavioral Technical Coding Presentation

I was contacted by a recruiter who thought I would be a good fit, so I applied. I received a quick response for an initial screening call with a very nice and enthusiastic recruiter. Soon after, a cultural interview with the hiring manager was scheduled. This interview included a brief, simple technical challenge. Next, I was given a take-home assessment with a flexible one-week deadline. After submitting it, another interview was set up to present my work. Unfortunately, the engineers during this presentation were extremely rude and dismissive, constantly interrupting me and invalidating my responses and implementation before I could fully explain. They seemed to lack understanding of the assignment's scope and had unrealistic expectations for the work I submitted. This was a terrible interview experience. If this is indicative of the company culture, I'm glad I didn't proceed. Hopefully, this was an isolated incident.

Confirmed questions1 question
  • Build an Event Booking System.
OutSystems logo
OutSystems

Software Engineer

Engineering · a year ago

Lead Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

Applied through LinkedIn, got contacted by recruiting 2 weeks later for an initial chat. First up was a non-technical 'get to know you' chat about my background and college. Then, I met with the hiring manager for a standard discussion on my job history and experience. Next, a technical interview with one of their Lead Software Engineers where I tackled two DSA questions on HackerRank. Finally, I had a longer, enjoyable conversation with an architect about application architecture.

Confirmed questions2 questions
  • Can you tell me about a project you were involved in that wasn't successful?
  • Tell me about a time a project you worked on did not go as planned.

OutSystems Software Engineer Interview Questions

Quoted word for word from OutSystems interview reports.

Could you write a function that takes an ordered array of integers and a target sum, and returns all pairs of integers within the array that add up to the target sum?

Read reports

Could you write an efficient algorithm to find a pair of numbers in a given sequence that adds up to X?

Read reports

Can you explain the different types of JOINS in SQL, such as Left, Right, and Inner JOINs?

Read reports

When building a serverside publisher service for a collaborative product, how would you manage simultaneous code changes from multiple subscribers to prevent data loss and maintain request order on the server?

Read reports

Can you explain what a microservice is in your own terms?

Read report

What are five potential issues that could arise in the communication between an application server and a database, and how would you address them?

Read report

Can you define DevOps basics, its uses, implementation strategies, and other related tools knowledge?

Read report

How would you optimize a given SQL query, and would you suggest changes to the supporting data model if necessary?

Read report

Describe how you would manage the lifecycle of VM instances to ensure current ones are maintained while older ones are retired.

Read report

Formats, difficulty and experience

Across all 64 OutSystems interview reports.

Interview formats

Technical 32.8%
Behavioral 30.2%
Coding 23.8%
System Design 8.5%
Presentation 3.7%

Interview difficulty

Easy 9.4%
Average 64.1%
Difficult 26.6%

Candidate experience

Negative 9.4%
Positive 84.4%
Neutral 6.2%