The most comprehensive bank Interview Answer Review tooling available online.

As my last semester as a system engineer student, I went above and beyond on time management of the time of the team and mine, this was on my thesis as student. while we where a team of 4 members, one of our members and I had one of our parents fighting cancer, so we needed to do time management to work in the project and have a correct time management of personal and work time. What I did was stated my focus, helped my companion doing the same noticing in what of the project we where helping the most and focus on that on my case the SQL queries & documentation of the project. Propose the solution to the other members, while also covering more and more in the written part of the project, this solution was applied by me, but i also had to cover sometimes my team member, doing what was also his tasks in this case the design of the project processes, most of the UML diagrams, because the situation of his family member worsen and some one needed to pick up the pace of the project and that person was me

At Octane, I had the following three steps. One is, I had a Confluent page wherein I would have the project up-to-date status on the stories, the features we are working and the state of each of the stories along with detailed explanation of where we are at, the risks the project carries, and also any test cases which have been passed. The second point of communication was via weekly status report wherein I would have a detailed status of where the project is trending, what are the risks associated, and identify the stories which was done in the previous week. The third part was, we had a bi-weekly communication wherein I would present the project status to all the stakeholders, including the leadership, to help them understand where the product is at, and are there any risks associated, and if so, how I'm trying to address it, and with whom I'm collaborating to get the risks addressed. By following these three steps and also being open to communicate on Slack, I had all the different channels open for communication with my stakeholders and leadership.

As an EM it is our responsibility to assist my team members so that they can grow. So I want to narate one scenario where I helped team member grow and it provided me an enormous learning. 

At hyperface when we were breaking monolith into micro service , there was a lot of work required at one of the component called integration service, this service was acting as a link between external bank system and hyperface Credit card as a service core engine . As work on this layer was more I moved one of the SDE-1 t that team , this team along with coding required lots of communication with business team as well , at that moment I found that the SDE-1 who was a good performer on core team started struggling in that team . I connected with him on 1:1 t ocheck is it because of he is not liking the work or is he having some personal issues as it was  hard to digest that person who is doing well in solving complex problem is struggling with not as challenging issue , at that moment I found that he is having issues in his communication , he feels underconfident interacting with other team , out of pressure commits what ever other team says. 

At that point fir I told him not to worry he is doing a good work and with him I created a framework to deal with this scenarios like always prepare before the meeting note done the important pointers , if you ae not sure d not commit always say I will get back after  discussing with team , for any communication rather then personal messages include relevant stakeholders as this will provide help . and also told him that improving communication is not an over night job. As a result of which withing one month following this practices his communication improved and it started reflecting in his work.

Learning : to help people grow always try to assign them the different type of tasks so that they will become aware where they are lacking and then help them grow

In my early days as Program Manager, I managed a project for one of our main customers. This project had a very tight schedule and I promised to deliver the first EVT samples in 3 months.

It was my responsibility to ensure everything would be completed on time, and achieve the quality standards defined by the program and inside the budget approved by leadership.

Unfortunately… when I started to deep dive into the project and analyze all the technical details, I realized that it was not possible to get the prototypes ready on time. I missed the deadline by 2 weeks. I felt bad at that time because I failed, so I immediately started to work on a new feasible schedule trying to mitigate the problem. In addition, I arranged a daily opening and closing meeting with the core team to monitor all activities. The root cause of the problem was a delay in some component's delivery and I also ignored one of the Reliability tests defined by Engineering.

So I highlighted the problem to my manager and I shared with him my new plan. I explained the situation to him and I shared the new timeline that I could meet. Then we worked together to commit to the new delivery date. So I learned a lot from that situation, now I’m always adding some buffer to my project schedules and I work more closely with core team members. But the most important learning was, how important is to be honest and raise your hand on time if something goes wrong.

During final stages of testing upgraded version of core banking applications, we encountered a defect which required resolution from development team. After dev deployed the defect, I had very limited time to thoroughly retest and perform regression.

My task was to perform retesting and make sure there are no major defects after the release.

After resolution, based on my prior knowledge of the apps I grouped those testcases that had a potential impact to run automation regression to speed up the testing. While I manually tested the defects with some edge case scenarios. 

I kept the cross functional team updated about the testing progress and the risk involved if testing wasn't completed on time. 

But, I was able to mitigate the risk of not completing the testing on time and major risk of unexpected issues with the help to prior knowledge and proactive communication.

Thus, I learnt from this incident to carefully strategizing the situation and collaborative approach can help to mitigate risks.

As a PL,
- Make a positive impact towards 3 critical business imperatives
- Gain team's and stakeholders trust
- Learn across portfolios to be able to innovate

At my previous role, I was leading a fraud detection AI model deployment for a financial services client. The model aimed to reduce fraudulent transactions by 25% while maintaining a low false positive rate.

I was confident in the model’s performance in the test environment, but when we deployed it in production, we noticed an unexpected spike in false positives. Transactions flagged as fraudulent were legitimate, causing disruptions for customers and increasing manual review work. To resolve this, I:

1. Investigated the issue by comparing training and production data.

2. Identified data drift—the model was trained on historical data, but recent transaction patterns had changed.

3. Worked with data engineers to implement real-time data monitoring.

4. Retrained the model with up-to-date data and adjusted hyperparameters to improve generalization.

This fix reduced false positives by 25%, improved fraud detection accuracy, and ultimately saved $500M in operational savings across multiple initiatives. This experience taught me the importance of continuous model monitoring and proactively accounting for data drift. Now, I always incorporate data validation pipelines and feedback loops into AI deployments to prevent similar issues.

בתקופת התיכון התנדבתי בבית ספר לחינוך מיוחד בשם "אל-נור". בחרתי להתנדב שם בעקבות חוויה אישית עם קרוב משפחה, שלימדה אותי עד כמה חשוב להעניק תשומת לב ותמיכה מתאימה לתלמידים עם צרכים מיוחדים. בנוסף, זהו בית ספר קטן עם צוות מצומצם, כך שראיתי בכך הזדמנות לקחת חלק משמעותי ולהשפיע. הגעתי להתנדבות פעם בשבוע, עזרתי לתלמידים באופן אישי, העברתי תכנים לימודיים דרך משחקים בקבוצות יחד עם המורים, וסייעתי בארגון וסידור הכיתה אחרי שהתלמידים הלכו לישון. לפני שהתחלתי, חששתי שלא אצליח להתחבר לתלמידים או להיות מספיק מעורב. בנוסף, לכל תלמיד היו צרכים שונים, ולכן היה עליי ללמוד מהמורים כיצד לגשת לכל אחד – אם הוא על הספקטרום האוטיסטי, עם תסמונת דאון, או עם צרכים מיוחדים אחרים. בהתחלה צפיתי במורים, התייעצתי איתם ולמדתי איך הם ניגשים לכל תלמיד לפי צרכיו, וזה נתן לי ביטחון להתחיל לפתח קשרים בעצמי לשמחתי, עם הזמן גיליתי שרובם קיבלו אותי בשמחה, למדתי לקרוא סימנים לא מילוליים, להבין מה גורם להם להרגיש בנוח, ולהתאים את הגישה שלי כך שירגישו נתמכים ומובנים. נהניתי מהאינטראקציה איתם, וזכיתי בתחושת סיפוק עמוקה