Your AI Wingman for your next interview

The most comprehensive bank Interview Answer Review tooling available online.

Behavioral
What is your most significant achievement?
Software EngineerFull Stack Software EngineerProgram ManagerFrontend Engineer

Databricks

Cognizant

Babylon Health

+5

During my career I manage a large number of projects, but one of the most challenging ones was the development and launch of a Telematic Control Unit for an important car maker in Japan. The project is important to me due to technical challenges we faced, the skills I applied and the impact on the company.

As Program manager my role was to lead a cross-functional team including Design Engineers, SW Engineers, Operations teams, Material procurement teams, quality and logistics, among others to successfully launch the product to mass production.

First, I kicked-off the project. For that, I shared with the team the project scope, the goals to achieve, I shared the project plan with key milestones and defined the roles and responsibilities for the different team members.

During execution, to maintain a clear communication, I set up design review sessions with the entire engineering organization to ensure everyone was aligned and fixing potential issues in advance. Besides, I led a weekly core-team meeting where we assigned tasks to team members, and setting clear deadlines for each task. To make these tasks easier to manage, I made sure tasks were broken down into manageable sizes with clear descriptions and acceptance criteria. This helped the team to stay focus on their deliveries and maintain speed.

Another important part was to manages Risks. I worked with the team to identify and classify possible risk that might impact to the project deliverables. We defined a Risk matrix to monitor during the development process, and also a project board with the main KPIs to achieve during each stage of the project.

To ensure quality, we defined different testing processes focused on the design, and the process. We installed specific quality check for the documents and devices delivered for each of the milestones of the PDP, as well as a clear quality control in mass production.

Finally, for transparency, I reported on monthly basis to our company leaders and customer about the project status, focusing on Timing, cost, quality and scope.

By employing these strategies, we successfully launched our module on time matching with all the requirements defined by our customer. This was a great example of teamworking, and taught me the importance of breaking down large projects into smaller and easy to manage pieces. Transparent and clear communication was also a great lesson learned. This approach helped me to improve in leading teams through complex problems.

15 days ago
Behavioral
What was your most innovative idea? How did you come up with it, and how did you implement it?
Software EngineerData Engineering ManagerEngineering ManagerUX Designer

Databricks

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.

5 months ago
6 months ago

Showing 1 to 10 of 105 results

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