What to ask the interviewer: questions that signal you're senior

Most candidates walk into an interview prepared to answer questions — and then blank when the interviewer flips the table and asks, "Do you have any questions for us?"

Here's the thing: what you ask is as revealing as what you say. At Virtusa, WSO2, or any mid-to-senior hiring loop in Colombo, the best interviewers are explicitly watching how you engage with their organisation — not just whether you can answer a coding question or walk through a case study.

These questions won't just show curiosity. They'll signal that you think strategically, that you've done the work, and that you're evaluating them as much as they're evaluating you.

Questions about the team

Before diving into role-specific questions, understand the environment you'd actually be working in. Try:

• "What does the team look like right now — how many are in similar roles, and what's the experience spread?"
• "How does this team collaborate with engineering, product, or finance — is it formal handoffs or more fluid?"
• "What's the biggest tension the team has navigated in the past six months, and how was it resolved?"

That last one is often avoided because it feels risky. It isn't. A senior hire at IFS or Hemas Holdings needs to know whether they're walking into a team with healthy friction or one where problems get buried.

Questions about the role

Generic questions like "what does a typical day look like?" are fine for fresh graduates. Mid-senior professionals need to go further:

• "What would you need to see from me in the first 90 days to feel confident this hire was the right one?"
• "What's the one thing the person who previously held this role did exceptionally well — and what's the one gap you're hoping I'd address?"
• "Is this role filling a gap, replacing someone, or is it a net-new function?"

The third question might feel intrusive, but it's legitimate and tells you something important. If they're replacing a long-tenured employee at MAS Holdings or John Keells IT, that person's shadow will be long. If it's a new function, expect ambiguity — which may be exactly what you want.

Questions about the organisation's direction

You're not applying for a job that exists in a vacuum. Showing you've connected the company's challenges to the role you'd play signals strategic thinking:

• "With CBSL's Open Banking rollout and the new fintech licensing framework, how is this team positioned to respond, and where does this role fit?"
• "What does success look like for this function over the next two years — and what's currently blocking it?"
• "Who are the internal champions for this work at the leadership level?"

Don't ask about promotions or growth in an early-stage interview. Save those for offer discussions. What you're doing here is demonstrating that you think about business context, not just job description bullets.

Questions about culture and working norms

Remote and hybrid arrangements have reshuffled how teams work across Sri Lanka. These are fair game:

• "How does the team handle disagreement — especially when there's a seniority gap in the room?"
• "What's the communication rhythm — is async work respected, or is everyone expected to be on calls throughout the day?"
• "How does the organisation handle mistakes — does learning get embedded into process, or is it handled case by case?"

The question about mistakes often gets an aspirational answer. Pay attention to how quickly they respond and whether they give a specific example. Let the silence breathe and see if they elaborate.

Questions about the hiring process itself

These are often overlooked, but asking them signals composure and puts you in a peer-to-peer posture:

• "What are the remaining steps in the process, and what's your timeline for a decision?"
• "Is there anything from our conversation today that you'd want me to expand on before we wrap up?"

The second question is underused and highly effective. It surfaces any concerns the interviewer has but hasn't voiced, and gives you a final window to address a weak point before you walk out.

What not to ask

Some questions will instantly age your candidacy:

• "What are the leave entitlements and working hours?" — ask HR, not the hiring manager.
• "Will I get training?" — fine once you have an offer, but too passive at interview stage.
• Anything that begins "I heard that in your company..." based on unverified LinkedIn gossip.

A note on volume

You don't need to fire all of these at once. Across a 45-to-60-minute interview, two or three substantive questions at the end — paired with responses to things raised during the session — is about right. In panel settings at WSO2 or Dialog Axiata, different panellists have different contexts, so direct specific questions to the most relevant person.

The goal isn't to impress. It's to have a real conversation between two parties deciding whether they want to work together. Come in knowing what you actually want to find out — and ask exactly that.