GovTech logo

GovTech Software Engineer Interview Questions
& Process

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

Based on 77 interview experiences · FREE TO READ

2.2 Rounds average
Average Typical difficulty
68.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at GovTech.

Showing 3 of 77
GovTech logo
GovTech

Software Engineer

Engineering · half a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Panel Group
Interview formats
Behavioral Technical Group

The hiring process felt more like idea collection than actual hiring, with the hiring manager absent from both selection rounds. Instead of focusing on past achievements, current engineers asked about their ongoing challenges. The HR was unprofessional and unaware of the team's work, directing me to the hiring team during the interview. The hiring team also lacked clarity on the company's direction. The online panel interview was online but only one or two out of seven interviewers had their cameras on, which felt disrespectful. It also seemed like the hiring team hadn't properly reviewed my resume, possibly using an AI tool without validation, as some acronyms caused confusion despite being explained in my CV.

Confirmed questions1 question
  • What's your approach when management provides unclear or no direction for a task?
GovTech logo
GovTech

Software Engineer

Engineering · nearly a year ago

Entry Difficult Positive experience No offer 3 rounds
Interview process
Take home Technical screen Onsite Background check
Interview formats
Coding System Design Behavioral

i had a timed hackerrank take-home assignment, which was a frontend vue3 assignment building a mini web-based game, which i found a bit odd for a full-stack role. if i passed that, i had a 3-hour onsite interview with three back-to-back sessions: a leetcode-style problem on a whiteboard, an architecture discussion also on a whiteboard, and a deep dive into my resume.

Confirmed questions1 question
  • Could you solve a moving average problem?
GovTech logo
GovTech

Software Engineer Intern

Engineering · nearly a year ago

Intern Difficult Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

The interviewers were nice and made me feel comfortable. We started with introductions and talked about my previous work and internships. Then, I was given a 45-minute technical problem. It wasn't a typical LeetCode problem, but more of an open-ended one where I had to break it down and think through different ways to solve it.

Confirmed questions1 question
  • Can you share some of your strengths and weaknesses.

GovTech Software Engineer Interview Questions

Quoted word for word from GovTech interview reports.

Can you use regex to check if a string matches a certain pattern?

Read reports

Can you create a button using React that increments and decrements a value?

Read reports

Could you write a sorting algorithm in C++ without using the standard library?

Read reports

Regarding graph traversal, what are the optimal and worst-case time complexities for element searching, and can you demonstrate a recursive implementation of a graph search algorithm?

Read reports

Could you build a web application that includes both backend and frontend components?

Read report

Could you build a CRUD web application using Node.JS, given specific endpoints and their expected actions?

Read report

Could you replicate the functionalities of the given sample application using React?

Read report

Can you code a solution for this LeetCode problem, analyzing edge cases and using any IDE and language of your choice?

Read report

What would be your reaction if your manager decided to terminate a project you had poured a lot of effort into and felt very passionate about?

Read report

Formats, difficulty and experience

Across all 77 GovTech interview reports.

Interview formats

Behavioral 32%
Coding 30.9%
Technical 28.6%
Group 2.9%
System Design 2.3%

Interview difficulty

Easy 16.9%
Average 67.5%
Difficult 15.6%

Candidate experience

Positive 68.8%
Negative 10.4%
Neutral 20.8%