The most comprehensive bank Interview Answer Review tooling available online.

I once led a restructuring initiative aimed at aligning resources with delivery accounts and redesigning KPIs. While the planning and communication strategy were solid, I overlooked whether our data platforms could support the new changes. Just before rollout, I discovered serious data integrity issues. This setback required a major clean-up effort across teams, but we corrected course by prioritizing platform readiness and enhancing our validation processes for future initiatives.

I was working on a high stake project with very high visibility from my senior management.

Me and my manager were thinking of can we leverage the quality of the development using help from QA team. He wanted to keep the QA team separate. His point of view was that a separate team would keep clear focus for the team and they would focus on finding more customer facing bugs. I thought that we should have QA embedded in the scrum team as that would help in easier collaboration and quicker bug fixes plus this is a more efficient way. Though I understood his point of view I always believed that in QA embedded inside the scrum team. I went back had a thought to measure the merits and demerits of the proposals. I put down in a slide the merits and demerits of each. Merit from having a separate team, clear focus and better filtering of quality, demerits less collaboration with development team. I then proposed that the QA engineers attend the calls of dev teams but keep a separate QA board for their tasks. This will give clarity of what bugs they find, what test scenarios they create and finally the metrics to measure the bugs reported per development. My boss and I both agreed as it solved the problems of each proposals

Situation:
While working on the CloudGate (CASB) program at Oracle, I had to collaborate closely with a lead engineer who was highly technical but often resistant to input from non-engineering stakeholders, including program managers like myself.

Task:
Our shared goal was to integrate CloudGate’s policy engine with a third-party SaaS provider under tight deadlines for a compliance milestone. Coordination was critical, but communication friction risked delaying delivery.

Action:
I focused on building mutual respect by first acknowledging his technical expertise and then shifting our interactions to be data- and goal-driven. Instead of pushing process, I came to discussions with clear risk/impact scenarios and timelines tied directly to customer and audit deadlines. I also adapted my style—fewer meetings, more async updates with technical clarity—which matched his preference. Gradually, we established a working rhythm built on outcomes, not personalities.

Result:
We delivered the integration on time, passed the compliance audit, and by the end of the project, had built enough trust that he started proactively surfacing risks to me before I had to ask. The experience reinforced for me that adapting communication style and focusing on shared goals is often more effective than trying to change personalities.

It would be at my thesis, of predicting SEPSIS with AI using multiple models, and the challenge was with time management, since we had 2 problems, the first problem was that we didn't had access to the data base until half of the second semester, since the process to get access to a hospital database was a rigorous process, so we weren't able to go quick with our application. The second one was that a team mate and I had a family member with cancer, so we needed to manage our work load in a manner that we could be present as family and team members, we needed to fulfil our duties on the project, so I planted a prioritization process in witch we focused on our best attributes I on sql queries and documentation, mostly but the situation with the family member of my companion worsen, so needed someone to help with his work load, so I also assisted him with his main tasks as the main designer of the project, mainly on the uml diagrams, so that we could end our thesis 

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

Situation:

I was laid off from my first job just four months after joining due to budget constraints. This was a major setback for me as I had just started my career. Around the same time, my father suffered a heart attack, which required me to stay at home and take care of him while he was on bed rest for several months. The combination of losing my job and dealing with a family emergency left me feeling devastated, and I struggled to apply for new roles.

Action:

Despite these challenges, I remained determined to grow in my career. While caring for my father, I focused on upskilling myself:

• I attended mentor sessions on ADPList to gain industry insights.

• I reached out to experienced designers on LinkedIn for portfolio reviews and feedback.

• I enrolled in courses through Interaction Design Foundation (IxDF) to expand my knowledge.

• I continuously improved my portfolio and resume, incorporating the feedback I received.

I also actively networked with professionals, which helped me regain confidence and visibility in the industry.

Result:

My persistence paid off. Where I once struggled to pass resume screenings, I started receiving recruiter calls consistently. In fact, this very interview happened because I proactively connected with a senior designer, shared my portfolio, and received a referral for this role. This experience not only strengthened my portfolio and skills but also taught me the power of perseverance, networking, and continuous learning.