The most comprehensive bank Interview Answer Review tooling available online.

Today I didn’t want to come to office directly, I wanted to start my day by visiting a temple, So, I first searched in map, to talk aloud of the temples nearby when I am driving my bike. 

It started mentioning take left to go to abc temple, I know, if I take that left, it will be very long to my office. so, I skipped that left and proceeded further in my regular route to office. After few kms, it again started saying take right to go to def temple. This time, I wanted to take that route.

So, I have proceeded as per google map, and I reached the temple after 20 mins of drive. I finished my visit and started by bike again. I have again asked to talk aloud about the hotels nearby as I didn’t eat my breakfast today to accommodate to temple visit.

It again started directing me in the similar way.

In this whole journey, the problem which I faced as a user is, I haven’t changed my final destination which is real page, now that I am diverting to temple and hotel, its not talking aloud with the overall distance increased to RealPage, also the different routes I should take because of this diversion, which in turn leads me to more traffic than usual, and I will be delayed to office. 

So, Problem statement here: Final destination is not changed, but requests for interim destination should also talk aloud on the possible route changes for the final destination and distance increase to the final destination

Persona: Dailu commuters who may have some diversions for other personal work.

PainPoints: Not easy to get the right route and the distance increased due to the diversion the user took.

Proposed solution:

Voice assistant to mention the increase of distance to the final destination, and mention the alternative routes, for Every diversion the user takes.

In my current role, there was a time when operation and engineering team was not aligned which was causing lots of delays during deployment. as per operation team build should be deployed in same branch which was available on pre-prod but as we were running multiple projects/features parallelly. it was difficult to develop and test everything in one branch and made it ready for deployment in a short time.

I had to work with my team (engineering team) and operational team to come up with a solution where we both are aligned and can reduce delivery time as well.

Initially i had proposed a solution when we were developing and testing work on feature branch and once its fully tested by QA on feature branch we push all changes to staging branch where we can do final testing. for some time this approach worked but we start facing new issue which is related to code merge as after merge features were impacting each other and require additional time to fix those issues and make it ready within planned time.

We added one more process if features/fixes are small and won't impact much then we merge else we try to plan deployment sequentially to avoid any further delay. 

This approach helped team to deliver project/feature on time and operational team was happy as they don't need to keep track of multiple branches during deployment.

I have an overall experience of 11 years in the fintech and healthcare industries. I started my journey as a front end developer for Banking and healthcare applications. I have been in a program manager role since 2018 managing healthcare and fintech projects. As part of the healthcare project, I was managing a patient health dashboard tracking application where I was collaborating with multiple crafts like engineering, creative design, product managers and external clients. As part of the fintech projects, I was working for the Lending verticals collaborating with product managers, engineering, and external partners.

I see myself working at the intersection of engineering and quantitative finance ideally at a hedge fund such as Two Sigma. My past experiences at Harvard Medical School and internships at MITRE/rapStudy have given me an interest in creating scalable systems that are high performant and capable of ingesting large amounts of data for model development and research.  I strongly believe Two Sigma is the perfect place for me to work on these highly technical projects. Additionally, I also look forward to the prospect of entering leadership roles during my career, where I can play a more impactful role in prioritizing cultivation of engineering talent and projects in fields such as low-latency and data engineering.

One product I really love is Notion. Notion is an all-in-one workspace that blends note-taking, task management, database creation, and collaboration tools into a highly customizable interface. It’s versatile, powerful, and has become a go-to tool for both personal and professional organization.

What I Love About Notion:

• Flexibility: Notion’s modular structure allows users to create anything from simple notes to complex databases, all within the same workspace.

• Customization: You can tailor the interface to your specific needs, whether you’re managing a personal to-do list or a company-wide project.

• Collaboration: It supports seamless collaboration with features like shared workspaces, real-time editing, and integration with other tools.

• Unified Workspace: It consolidates various tools (notes, tasks, databases, etc.) into one platform, reducing the need to switch between multiple apps.

Improvements Without Limitations:

1. Advanced AI Integration:Personalized Suggestions: I would implement AI that understands user behavior and context, offering personalized suggestions for organizing content, automating repetitive tasks, and surfacing relevant information when needed.
   Smart Summarization: Introduce an AI-powered summarization feature that can condense long-form content into key points, making it easier to digest and reference large amounts of information.
   
   

2. Enhanced Collaboration Tools:Real-Time Co-Editing with Conflict Resolution: Upgrade the real-time collaboration feature with advanced conflict resolution, allowing multiple users to work on the same block of text or database entry simultaneously without overwriting each other’s changes.
   Video and Voice Chat Integration: Integrate native video and voice chat directly within Notion, allowing teams to discuss content without leaving the workspace.
   
   

3. Universal API and Integration Hub:Seamless Integration: Build an open API and a powerful integration hub that allows Notion to connect more deeply with a broader range of tools and services. This would enable users to pull in data from any source and automate complex workflows across platforms.
   Bi-Directional Sync: Ensure that integrations offer true bi-directional sync, so changes made in Notion reflect in other tools and vice versa, creating a seamless multi-tool ecosystem.
   
   

4. Advanced Data Analytics and Visualization:Customizable Dashboards: Add advanced data analytics capabilities, allowing users to create dynamic dashboards that visualize information from their databases in charts, graphs, and other formats.
   Automated Insights: Introduce automated insights that identify trends, anomalies, or opportunities within user data, helping teams make data-driven decisions directly within the app.
   
   

5. Offline Functionality:Full Offline Mode: Enhance offline capabilities so that users can access and edit all content without an internet connection, with changes automatically syncing when they go back online.
   Mobile Optimization: Improve the mobile app’s offline functionality, ensuring that it mirrors the desktop experience even without connectivity.
   
   

6. Enhanced Security Features:End-to-End Encryption: Implement end-to-end encryption for all user data, ensuring that content remains secure and private even when stored on Notion’s servers.
   Granular Access Control: Offer more granular access control options, including role-based permissions, time-limited access, and audit logs to track changes and access history.
   
   

7. Global Accessibility and Localization:Multilingual Support: Expand Notion’s language support and offer full localization for more languages, ensuring that users worldwide can access and use the platform in their native languages.
   Accessibility Enhancements: Improve accessibility features for users with disabilities, such as screen reader compatibility, voice commands, and customizable interface options for visually impaired users.
   
   

8. Creative Content Tools:In-App Design Tools: Integrate advanced design and content creation tools, such as a vector graphics editor or video editor, allowing users to create and embed rich media content directly within Notion without needing external apps.
   Template Marketplace: Expand the template library into a full-fledged marketplace where users can buy, sell, or share custom templates, scripts, and integrations, fostering a community-driven ecosystem.
   
   

Conclusion:

With these improvements, Notion could evolve from an excellent productivity tool into a truly unparalleled platform for personal and professional organization, collaboration, and innovation. These enhancements would make Notion even more indispensable, catering to a wider range of users and use cases while maintaining its core strengths.

I was managing organization wide restructuring program where goal was to map all resources with their delivery accounts to keep a track of account’s PnL and manage capability as cost centre. We also intended to design KRA and KPIs for each individual level to make our Performance Assessment data driven and transparent. This was a big change at employee level at professional and emotional level too. It meant changes in their reporting structures, extra reporting and performance management by all managers, clear KPIs alignment and selection.

Planning Level: We identified all the major business account heads, capability and other function head and organized a communication platform to make them aware and comfortable with the changes. We undertook their inputs on pros and cons and some caution to be exercised

Execution Level: We started executing these changes with L0 level employees and moved up to leadership team. Along the way we encountered some risks and outlier conditions to be managed.

Communication Strategy: We worked with all business and functional heads on our communication strategy to reach out to all the employees. Head multiple events and workshops to discuss the changes.

Data Platform changes: Evaluated all the data platform changes required and planned a phased out approach to bring those changes in the system as well.

However, when we were about to reach closure of this program, I realized that I have made a big mistake of readiness of our existing platforms to support all the changes required and existing data integrity. It really took a toll on everyone involved to clear up data accuracy before the changes could be introduced.

My philoshipy to build a high perfomance team is to create a bottoms up culture. By empowring my team members the autonomy of solving the customer problem which they deem fit at scale, they not only grow but also innovate on things if they don't like the status quo.

For e.g. At Auctane, one of my team members was not satisfied with the approach proposed for doing a sync of data from Microservices to monolith. He did a deep dive on how this can be improved, he proposed Kafka as a best fit stack we can use. I encouraged him to do a POC, come up with pros and cons. Then I set up a meeting with my director and did a POC, I talked about potential impact was not just for our team but could be implemented org wide as well. 

We implemented this new technology on the project he was working on, documenting all the learnings he discovred and released to prod. Once we were satisfied that it works for us, I arranged for a show/tell session for other engineeries who had to solve a similar issue, this developer gave a techtalk on how it was implemented, challenges we faced etc. Other teams adopted this tech as well. The result of this was that as an Org. we could save close to 15% of dev cycle by standardizing and implementing a new tech. My employee also took this opportunity to learn and grow at the same time.

I once analyzed a massive dataset of user interactions on a social platform to identify engagement trends. By processing millions of posts and comments, I found that short, visual content posted during evening hours had 30% higher engagement rates. This led to recommendations for optimizing posting schedules and content formats.

MVP for Maintenance module where all maintenance work was tracked for the vessels. While it was lift and shift but challenge was identifying the gaps and prioritizing correct features to provide MVP. For example, I brainstormed certain features like equipment maintenance, work orders, were most important than some reports.. I also realized that some authentications, system preferences were also missing which holds highest importance. There was also a feature where it would automatically tell which maintenance work is upcoming. I developed a report of my findings and came up with high impacted features that were missing. The effort was estimated, and high impact low effort took first seat in the roadmap followed by high effort features. Early Adopter mechanism

Result: There was 80% parity achieved w.r.t. legacy system for high impact features and 30% of targeted adoption was achieved for Maintenance module.