Your AI Wingman for your next interview

The most comprehensive bank Interview Answer Review tooling available online.

Behavioral
What was the most innovative idea you've ever had? How did you come up with it and how did you go about implementing it?
Full Stack Software EngineerData Engineering ManagerEngineering ManagerUX Designer
GetYourGuide Logo

GetYourGuide

NetApp Logo

NetApp

Bill.com Logo

Bill.com

+7

When I joined my new team , I took lead on a new project which was complex in nature, had many unknowns and our team had to work on new framework, techstack, data models. The team was following agile methodology and will start with the work in first sprint. there was no concept of zero sprint or story grooming prior to the start of first sprint.

with the existing approach I envisioned some issues:

1. Because the number of unknown were high, the chances of doing wrong estimations for development were high.

2. There were high chances that the prioritisation is not right and we might have to revisit the features again and again.

3.  We might find out about unknowns while we are in the development process and that might cause delays.

To overcome these issues, I suggested some changes in our approach:

1. Increase the planning for one more release cycle and group the features as now, next and later.

2. For the features planned in the now group , prioritise them for the next release and complete the research and PRDs for them one sprint early. That means dev and QA will have 2 weeks extra to go through the stories, find out the dependencies and share the feedback. This helped in identifying if we need POCs for any feature or we can right away start developing them. Or if further modularisation is required.

3. I suggested to track the features related to new project in a different group, because to begin with the pace of the delivery will be slow.

When we begin, we took one complete release only in the RnD and understanding the new framework and doing small POCs to validate our understanding.

From second release, when we as a team were ready with good understanding on the expectations and other tech dependencies we started delivering and we could complete 2 full flows from end to end.

We had very less amount of spillover and could complete almost everything in the backlog, which was a big issue in earlier releases.

2 months ago
2 months ago
Behavioral
I want to hear about a time when you had to work together on a project with a coworker who you didn't like.
Full Stack Software EngineerData Engineering ManagerEngineering ManagerUX Designer
GetYourGuide Logo

GetYourGuide

Amazon Logo

Amazon

Figma Logo

Figma

3 months ago
Behavioral
What was your experience one time when you were asked to help a colleague in an area out of your sphere of responsibility?
Full Stack Software EngineerTechnical Program ManagerSoftware EngineerProduct Manager
GetYourGuide Logo

GetYourGuide

DeviantArt Logo

DeviantArt

Lenskart Logo

Lenskart

7 months ago
Behavioral
Tell me about a time where you showed ownership
Full Stack Software EngineerTechnical Program ManagerSoftware EngineerProduct Manager
GetYourGuide Logo

GetYourGuide

ApplyBoard Logo

ApplyBoard

Naspers Logo

Naspers

+11

At my current job one of our biggest customer raised the  issue they were facing in our notification service. The issue was they were not receiving any notifications from our system on their new infrastructure. Their production infra was working fine.

I reviewed their configuration and everything was looking fine at the same time we hadn't done any changes to on our end which could cause this issue. Since their contract was up for renewal the issue, we needed quick resolution. I setup a live debugging session with customer to understand the issue in detail and their new infrastructure. After the first call it was clear that the issue was happening during https handshake or at network layer. To keep the momentum going I setup recurring call with with them and assured them that we are treating this as a high priority. On the next call I involved our security expert and SRE team for further debugging. However the issue not futher progress was made, at this point I insisted SRE team that we contact Azure support to understand if there is any issue at the tcp layer. Azure team looked at the turned on debug logs and found that our network was default MTU (maximum transmission unit) was higher than customers network MTU and customer network was dropping packets.

Finally I worked with SRE team to lower our MTU to match the customer configuration and ran tests. After the config change issue was resolved, our customer confirmed that they could see the notifications. This was really difficult issue I had ran across but I worked with various teams to get to the bottom of it and delivered results to customers satisfaction.

8 months ago

Showing 1 to 10 of 77 results

*All interview questions are submitted by recent GetYourGuide Full Stack Software Engineer candidates, labelled and categorized by Prepfully, and then published after being verified by Full Stack Software Engineers at GetYourGuide.