The most comprehensive bank Interview Answer Review tooling available online.

I was working with 5 customers at once, and had to focus on those activities where I could make a difference, make the most impact, that I could not delegate, and where I could balance with other priorities - in order to do that, I measured the priority of the tasks by the cost of delay, in other words, the impact of not doing them at that time. Then, with more clarity about the priorities, I thought which ones I could delegate to other team members, and if that made sense, with the required support and guidance from my side. Working as a team and not trying to get everything done yourself is key in the long term with multiple, competing priorities. Then, organizing my time well in short, focused timeslots for the most important tasks, made a difference.

I graduated in May 2024 and recently wrapped up my role at Bright Mind Enrichment. It was a great experience, and I stayed through my agreed-upon commitment.  At this point, I’m looking for a full-time opportunity that offers deeper ownership, long-term growth, and technical mentorship—especially in a full-stack environment like Atlassian’s.

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.

So i can take one 2:1 multiplexer and 2:1 mux have 2 inputs, one output and one select line so i can connect one of the variable to select line and another will connect to input 1 and input zero is grounded