Competency-Based Interview Questions in English

[Situation + Task]
"At my previous company, our product team was restructured mid-year, and I was asked to lead a newly formed team of six people — most of whom had never worked together before — with a critical client delivery in eight weeks."

[Action]
"I started by running individual 1-on-1 meetings in the first week to understand each person's strengths and concerns. Then I created a clear roles document so there was no ambiguity about ownership. I established a daily 15-minute standup and a transparent shared tracker so everyone could see progress and blockers in real time. When conflict arose between two team members over a design decision, I facilitated a structured discussion where both presented their case with data, and we reached a consensus decision in under an hour."

[Result]
"We delivered the project on time. The client gave us a satisfaction score of 9.2 out of 10, the highest they had given any vendor that year. Three of the six team members later cited the project as one of their best professional experiences in their performance reviews."

[Situation + Task]
"Our platform was experiencing intermittent performance degradation that was affecting approximately 20% of users at peak times, but only on mobile. The engineering team had investigated for two weeks without finding the root cause."

[Action]
"I took a systematic approach. I first mapped every scenario where the issue occurred — device type, network, time of day, user journey — and noticed it correlated only with users on 4G networks, not WiFi. I then examined our CDN configuration and discovered we had a misconfigured edge rule that was routing mobile 4G traffic through a geographically suboptimal server cluster. I verified this hypothesis by replicating the issue in a test environment, then proposed a configuration change to route this traffic correctly."

[Result]
"After the fix was deployed, mobile performance complaints dropped by 94% within 48 hours. The root cause had been present for 3 months — my structured diagnostic approach found it in 4 days."

[Situation + Task]
"I was co-leading a project with a colleague who had a very different working style — she preferred to discuss every decision in meetings; I preferred async written communication. This was creating friction and slowing our delivery."

[Action]
"Rather than letting the tension persist, I suggested we have a direct conversation about how we each worked best. I shared my preference for async with clear documentation; she explained that she needed verbal discussion to process complex decisions. We agreed on a hybrid approach: I would prepare written summaries before meetings, which gave her the discussion context she needed without requiring me to attend meetings for every small decision. I also made a point to be more available during her preferred hours for high-stakes decisions."

[Result]
"We completed the project two weeks ahead of schedule — our fastest delivery in that quarter. We also continued working together successfully on two subsequent projects. The approach we developed became an informal team norm."

[Situation + Task]
"Our legal team needed to approve a new data processing architecture, but none of the lawyers had a technical background. The technical documentation was 40 pages — unreadable for them — and the decision was time-sensitive."

[Action]
"I created a 2-page visual summary using an analogy: I compared our data pipeline to a post office — data packages being collected, sorted, verified, and delivered. I mapped each technical component to this analogy and highlighted only the two points that had legal implications. I then presented this in a 20-minute meeting and invited them to ask any question without worrying about being 'technical enough.'"

[Result]
"Legal approved the architecture in that meeting — a process that typically takes 2–3 weeks was completed in under one hour. The General Counsel later told my manager it was the clearest technical presentation they had received from the engineering team."

[Situation + Task]
"Three weeks before our product launch, a key integration partner announced they were changing their API completely — which would break a core feature of our product that we had spent four months building."

[Action]
"I immediately assessed two options: delay the launch or redesign the feature. I spent 48 hours evaluating the API documentation, prototyped a workaround, and confirmed it was viable. I then presented leadership with a revised plan: we could launch on time with a slightly simplified version of the feature, then deliver the full version in the next sprint. I personally managed the communication to the partner, our engineering team, and the client — keeping everyone aligned during a high-stress period."

[Result]
"We launched on schedule. The client did not notice the temporary simplification. The full feature was delivered 3 weeks later. The partner relationship was actually strengthened by how professionally we handled the crisis."