The Convergence Foundation Technical Program Manager Interview: Questions & Prep (2026)

The Convergence Foundation is one of India's leading public policy think tanks, working at the intersection of technology, economics, and governance. Their programs cover AI policy, economic development, health systems, and more. The Technical Program Manager role here is not a typical software TPM job. You will be expected to coordinate multi-stakeholder research programs, manage relationships with government bodies, academic institutions, and industry, and drive projects from ideation to published output or policy recommendation.

As of July 2026, The Convergence Foundation has 29 open roles, signaling a phase of active expansion. TPM candidates who combine structured execution skills with genuine curiosity about policy and social impact tend to stand out. The interview process typically involves a screening call, a take-home case study, and one or more rounds of conversations with senior team members, though candidates report variations in structure and timing.

Across India, 313 TPM roles were listed on knok jobradar as of July 2026, with Bangalore leading at 41 openings, followed by Delhi (14), Pune (13), and Hyderabad (12). TCF roles tend to be based in Delhi, reflecting the organization's proximity to policy corridors.

These questions come up frequently in TCF TPM interviews, based on the nature of the organization and the skills the role demands. Prepare a specific example for each.

1. How would you manage a program that involves academics, government officials, and private sector partners, each with very different working styles and timelines?

1. Walk us through how you have tracked deliverables across a multi-team project where you had no direct authority over contributors.

1. TCF works on topics like AI governance and economic policy. How do you get up to speed quickly on a technical or policy domain you are not an expert in?

1. Describe a time when a program you were managing faced a significant scope change mid-way. How did you respond, and what was the outcome?

1. How would you build a program status update that works for both technical researchers and senior leadership who have very different information needs?

1. Tell us about a situation where a key stakeholder was consistently not delivering on their commitment. What steps did you take?

1. How do you prioritize across multiple active programs when resources (people, budget, time) are limited and competing?

1. TCF often engages with government bodies and regulators. How do you manage relationships with stakeholders who have unpredictable availability or long response cycles?

1. Describe how you would plan a large policy consultation or roundtable involving participants from many different sectors.

1. How do you define 'done' for a research or policy program, compared to a software development project?

1. Tell us about a time you had to communicate bad news, such as a delay or a scope reduction, to senior leadership. How did you frame it?

1. What program management tools and methods have you used, and how would you adapt them for a policy research environment rather than a product or engineering team?

Use the STAR format (Situation, Task, Action, Result) for behavioral questions. Here are three worked examples tailored to TCF-style interviews.

Q: Tell us about a time you managed a program with stakeholders who had very different working styles and timelines.

*Situation:* At my previous organization, I was leading a research program on financial inclusion that involved a university research team, two government ministry contacts, and a fintech company.

*Task:* My role was to keep all three parties aligned on milestones and ensure the final report was ready for a policy event with a fixed date.

*Action:* I set up separate communication rhythms for each group. The academic team got a weekly check-in with detailed milestone tracking in a shared document. The government contacts got a fortnightly briefing note, kept to one page, focused only on what they needed to review or decide. The fintech partner was looped in via a monthly update call. I created a single master tracker visible to everyone but tailored the summary views for each audience.

*Result:* The report was delivered on time, all three parties contributed their sections, and the government ministry formally cited the research in a consultation paper published the following quarter.

---

Q: Describe a time a program you were managing faced a major scope change mid-way.

*Situation:* I was several weeks into managing a policy research sprint when our primary funder requested that we add a comparative analysis of additional countries to the scope, without extending the deadline.

*Task:* I needed to assess the impact honestly, communicate it clearly, and find a workable path forward.

*Action:* I mapped out the original workplan against the new request, identified which components could be parallelized and which could not, and presented the leadership team with three options: extend the deadline, reduce the depth of the original analysis to accommodate the new scope, or add a short supplementary report delivered after the main publication. I recommended the third option with my reasoning laid out clearly.

*Result:* Leadership chose the supplementary report route. The main report came out on the original date, and the supplementary note followed a few weeks later. The funder was satisfied, and the approach became a template for handling similar mid-program requests.

---

Q: How have you communicated bad news to senior leadership?

*Situation:* I was managing a multi-partner program when one external contributor informed us just before a milestone that their data collection had hit regulatory delays and they could not deliver their chapter.

*Task:* I had to inform the Executive Director, who was personally involved in the program, and propose a credible recovery plan.

*Action:* I did not wait for the weekly update meeting. I sent a brief written note the same day covering the problem, my preliminary options, and the tradeoffs of each. I then requested a short call. In the call, I was direct about what we did not yet know and gave a clear timeline for when I would have more certainty.

*Result:* The ED appreciated the early flag. We ended up using internal researchers to fill the gap, which actually improved the chapter. The program delivered with a short delay, and I received feedback that the way I handled the escalation built trust with senior leadership.

For 'how would you' or planning questions, use a three-part structure: clarify the goal and constraints first, then outline your approach in steps, then name how you would measure success. This shows structured thinking without sounding robotic.

For stakeholder management questions, use a RACI lens (Responsible, Accountable, Consulted, Informed) as a thinking tool even if you do not name it explicitly. Interviewers at TCF want to see that you distinguish between people who need to decide, people who need to be informed, and people who need to do the work.

For prioritization questions, name the criteria you would use (urgency, strategic importance, dependency on other work, resource availability) before giving your answer. Showing your reasoning matters as much as the conclusion you land on.

For 'tell me about a time' questions, keep STAR tight. Spend no more than a sentence or two on Situation and Task combined. The Action section should take up roughly half your answer. Result should be specific and, where possible, mention the broader impact beyond the immediate deliverable.

For domain knowledge gap questions (for example, 'you are not an AI policy expert, how would you manage this program?'), be honest and structured. Name the first things you would do: read the foundational literature, speak to the subject matter experts on the team, and identify which decisions require domain expertise versus which are pure program management.

TCF is a mission-driven organization. Interviewers are looking for signals across several areas.

Mission alignment. This does not mean you need a policy background, but you should be able to articulate why the intersection of technology, governance, and public impact matters to you. Generic answers about 'making a difference' will not land. Reference specific areas of TCF's work that you find compelling.

Structured execution without bureaucracy. TCF moves fast and works with limited resources. They want TPMs who can bring clarity and process without adding overhead. Show that your instinct is to simplify and unblock, not to build process for its own sake.

Comfort with ambiguity and indirect authority. Most of the people you coordinate at TCF, from visiting fellows to government contacts, are not in your reporting line. Interviewers will probe how you get things done through influence, relationship-building, and clear communication rather than hierarchy.

Communication range. You may need to write a one-page brief for a minister and a detailed milestone tracker for a researcher in the same week. Interviewers want to see that you can shift your tone and level of detail for different audiences without losing precision.

Intellectual curiosity. A repeated theme in TCF hiring is whether candidates are genuinely curious about ideas. Be prepared to discuss a policy or technology topic you have been following recently, with your own perspective, not just a summary.

Know the organization deeply (start here). Read TCF's published reports, blogs, and policy briefs. Identify two or three programs that interest you. Know their current focus areas: AI and emerging technology, economic policy, health systems. Be ready to reference specific work, not just the mission statement.

Map your STAR stories. Write out six to eight stories from your career covering: managing without authority, handling scope changes, communicating bad news, coordinating multi-stakeholder programs, and working across sectors or organizations. Practice delivering each in under two minutes.

Sharpen the TPM craft angle. Review how program management principles apply outside software: research pipelines, publication cycles, policy consultation timelines. Think about how you would adapt tools like roadmaps, RACI charts, or status reports for a think tank context.

Prepare your own questions. Candidates who ask sharp questions about program structure, team size, decision rights, and what success looks like in the first six months make a strong impression. Avoid questions whose answers are already on the website.

Keep your applications moving in parallel. If you are actively job-searching while preparing, knok checks 150+ job sites nightly, applies to jobs matching your resume, and messages HR for you, so deep interview prep and active applications do not have to compete for your time.

Treating it like a Big Tech TPM interview. TCF is not a product company. Answers heavy on sprint ceremonies, OKR tooling, or engineering velocity metrics will not land well. Translate your experience into outcomes and stakeholder impact instead.

Showing up without reading their work. Interviewers at policy organizations notice immediately when candidates have not read any publications. At minimum, read one recent TCF report relevant to the program area you are interviewing for.

Vague mission alignment. Saying 'I want to work in the social sector' is not enough. Connect your specific skills and past work to what TCF actually does. Name the program area or policy question you want to contribute to.

Over-indexing on tools. Listing project management software in your answer to a process question signals that you think the tool is the answer. TCF interviewers want to see the thinking behind your approach, not the names of the apps you use.

Underplaying soft power skills. In a think tank, getting a government official to respond to your emails on time is a real program management challenge. Do not skip over the relationship-building and communication work that made your past programs succeed.

Not asking about the role's scope. With 29 open roles, TCF is in growth mode. Some TPM positions may be newly created with undefined scope. Candidates who do not probe this risk joining a role that looks different on day one than it did in the interview.