The most comprehensive bank Interview Answer Review tooling available online.

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.

l, I initially built automation scripts for trade reconciliations and reporting using standalone Python and UNIX-based cron jobs. These worked well for smaller data volumes, but as our operations scaled across global teams in London, Hong Kong, and the Bahamas, performance and maintainability became a bottleneck.

I realized I needed to adapt my workflow to better support large-scale, distributed processes. So, I changed how I worked by migrating critical pipelines from PostgreSQL and flat scripts into a more robust ETL framework using Databricks and Delta Lake. I restructured batch processes into streaming jobs and modularized the Python code to be production-grade. I also started using Kafka and Kubernetes to improve system reliability and orchestration.

In the first company I worked as tech lead, even though my performance rating was good, I received a 360 degree feedback on my interpersonal skills as well. One of them said that I sounded a bit rude in couple of discussions. When I asked for the instances, I got examples where I got the feedback from and not whom. So I had to explain my manager that it was not intentional and the aggressive demanding nature of mine could have been perceived as rude. But I considered the feedback and identified, corrected myself, toned down the way I speak in certain instances which made a set of teams in my org ex: production support teams reach out to me more often now for guidance. So this helped me gain valuable experience and unlock a totally different perspective in terms of collaboration with other squads in the company.

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