Unifonic – Program Manager (Delivery Excellence)
Interview Full Script
This document provides the full-length structured answers and STAR stories, designed to be used
as practice scripts for 60–90 second spoken responses.
1. Technical / Delivery-Focused Interview Questions – Full
Answers
Q: How would you standardize the delivery flow across multiple teams?
A: I would start by mapping the existing flows for each team to identify inconsistencies and gaps.
Then, I’d define clear quality gates for each phase — Build, Release, Rollout — so work can’t
progress without meeting readiness criteria. Next, I’d integrate Jira with CI/CD to automate status
updates and enforce these gates. I’d introduce standard dashboards with KPIs like cycle time,
release readiness, and defect leakage. Finally, I’d set up regular retrospectives to refine the
process. In a similar role at CFI, this approach reduced onboarding cycle time by 25% and cut
handover issues by 40%.
Q: How would you measure and track delivery excellence?
A: I’d begin by establishing a baseline of current performance — for example, average lead time,
defect escape rate, release frequency. Then, define clear KPIs aligned with delivery excellence,
such as cycle time, deployment success rate, and SLA adherence. I’d build dashboards in Jira and
BI tools so leadership and teams have real-time visibility. Finally, I’d run weekly reviews to track
trends, identify bottlenecks, and highlight improvements. At ITS, this approach helped us reduce
post-release defects by 30% and improved release predictability significantly.
Q: What steps would you take to reduce stale or incomplete Jira tickets?
A: First, I’d run a backlog audit to find tickets that are stale or missing information. Then, I’d define a
clear Definition of Ready and Definition of Done, so tickets can’t move forward unless they meet
criteria. I’d set up Jira automation to flag or close stale tickets after a period of inactivity.
Dashboards would highlight hygiene issues for each team. Finally, I’d run quick training sessions
with teams to reinforce best practices. This approach worked well at CFI where incomplete tickets
used to block compliance — automating the checks reduced delays by 25%.
Q: How do you handle resistance to new processes?
A: I always start by listening to concerns and involving the team in designing the solution. I run
small pilots with one team, demonstrate measurable improvements, and then scale up.
Communication and quick wins are key. At Softex, when I introduced requirement checklists, there
was pushback from developers. I piloted it with one squad, showed how it reduced rework, and
within two months other teams asked to adopt it. That bottom-up adoption helped embed the
process without heavy resistance.
Q: How would you align cross-functional initiatives (e.g., security/compliance)?
A: I’d map all dependencies across teams, then embed mandatory tasks into the Definition of Done
so they become part of the workflow. I’d track these via program boards and run bi-weekly syncs
with stakeholders. Metrics like compliance task completion rate would give visibility. At ITS, I
applied this to a compliance project, and it helped reduce missed audit requirements to zero across
three releases.
2. STAR Stories – Technical Delivery Excellence (Full Versions)
Delivery Flow Standardization (CFI – Fintech)
At CFI, we had a real issue with onboarding tickets in Jira — sales would push cases to compliance
without the right KYC documents, and it caused a lot of rework and delays. My task was to make
the flow smoother and more predictable. What I did was map the full onboarding process across
Sales, Compliance, and Operations, then I defined quality gates. For example, a ticket couldn’t
move to compliance unless all documents were attached and verified. I also automated Jira
transitions so incomplete tickets were flagged right away, and I set up dashboards to track SLA
compliance. The result was that onboarding cycle time dropped by about 25%, back-and-forth
between teams was cut almost in half, and client satisfaction scores improved because the
onboarding felt smoother and faster.
Release Quality & Automation (ITS – Banking Software)
At ITS, one of the main problems was late-stage defects and unpredictable releases for banking
clients. I was asked to help improve execution quality. I introduced a release checklist that required
unit testing, peer review, and regression testing before a ticket could be marked as release-ready. I
then connected Jira with our Git and CI/CD pipelines, so when builds or tests passed, Jira updated
automatically. On top of that, I set up dashboards that showed release readiness and open defects
in real time. The impact was big — post-release defects went down by 30% in just three months,
90% of releases went live on schedule, and client escalations dropped significantly because they
trusted the process more.
Cross-Functional Alignment (Softex – .NET Projects)
At Softex, the main challenge was that product requirements, development, and client expectations
often drifted apart — leading to scope creep and delays. To fix that, I set up shared Jira dashboards
so all stakeholders could see backlog progress and blockers. I organized bi-weekly syncs between
product managers, engineers, and QA to align on priorities. I also introduced requirement checklists
so every feature had acceptance criteria before development began, and I ran retrospectives to
keep improving. The result was clear: scope creep incidents went down by about 20%, on-time
delivery improved from 70% to 90% in a quarter, and client trust grew because they finally had
transparency and predictable updates.
3. Behavioral Interview Questions – Full STAR Answers
Q: Tell me about a time you dealt with conflict in a team.
A: At CFI, there was tension between Sales and Compliance because Sales pushed incomplete
cases that Compliance had to rework. My task was to resolve the conflict without slowing down
sales. I facilitated a session where both teams mapped the workflow and identified bottlenecks. I
introduced a simple checklist for Sales before submitting, and automated Jira transitions to block
incomplete cases. The result: onboarding was 25% faster, Compliance workload was reduced, and
the friction between teams disappeared because the process itself enforced quality.
Q: Describe a time you had to manage multiple priorities under pressure.
A: At ITS, I was managing two major client releases with overlapping deadlines. My task was to
balance resources without delays. I created a shared dashboard for both projects, clarified critical
path tasks, and negotiated with stakeholders to sequence priorities. I flagged risks early to
leadership and shifted non-critical tasks. The result: both projects went live on schedule, clients
were satisfied, and internally the leadership team appreciated the proactive risk management.
Q: Give me an example of when you introduced a process change that others resisted.
A: At Softex, I introduced requirement checklists before development. Developers pushed back,
saying it slowed them down. I piloted it with one team, collected data showing a 15% reduction in
rework, and shared those results. Within weeks, other teams requested adoption. The result: cycle
times improved, defects dropped, and the checklist became a standard practice.
Q: Tell me about a time you had to work with limited resources.
A: At ITS, we faced a sudden 50% reduction in QA testers before a critical release. My task was to
maintain release quality despite the gap. I expanded automated testing, cross-trained developers to
handle regression tests, and reprioritized test cases by risk. I also aligned with the client on realistic
expectations. The result: we delivered on schedule, with only minor post-release bugs, and
preserved client trust under tough conditions.
Q: Describe a time when you had to influence stakeholders without direct authority.
A: At CFI, incomplete Jira tickets from Sales were slowing compliance. I had no authority over
Sales, but I gathered data showing how much delay was caused. I presented this to the Sales lead,
focusing on how fixing it would improve client experience. With that buy-in, Sales agreed to adopt
the checklist process. Within two weeks, ticket completeness improved by 80%, and onboarding
delays reduced significantly.
Final Practice Notes
- Each STAR story should be delivered in 60–90 seconds, ending with measurable results. - Use
the structure: Situation → Task → Action → Result. - Keep delivery conversational, not memorized.
- The goal is to show problem-solving, leadership, and impact.