Big Assets Infra Engineering Manager Interview: Questions, Experience & Prep (2026)
Big Assets Infra Engineering Manager interview experience and prep for 2026: the most-asked questions, sample STAR answers, the hiring process, and how to get
See which of these jobs match your resume →Overview
Big Assets Infra currently has 13 open Engineering Manager positions, making it one of the more active hirers in this space right now. Across India, the knok jobradar tracks 975 Engineering Manager openings as of July 2026. Bangalore leads all cities at 182 listings, followed by Delhi at 53, Pune and Chennai at 20 each, Hyderabad at 16, and Mumbai at 12.
Salary data from knok jobradar for this track:
| Level | Salary Range (LPA) |
|---|---|
| Manager | 35-60 |
| Senior Manager | 55-90 |
| Director | 90-150+ |
The interview process at Big Assets Infra typically spans multiple rounds. Candidates report a mix of behavioral questions, system design discussions, and people management scenarios, with a strong emphasis on large-scale infrastructure, reliability, and cross-team coordination. The company's infrastructure focus means interviewers tend to look for EMs who can bridge technical depth with business outcomes.
Most Asked Questions
These questions come up most often, based on what candidates report from Big Assets Infra Engineering Manager interviews. Prepare a concrete personal story for each one before you walk in.
- How have you built or restructured an engineering team to meet a fast-changing product roadmap?
- Describe a time you delivered a critical infrastructure project under tight constraints. What trade-offs did you make?
- How do you handle a team member who is consistently missing deadlines despite coaching and support?
- Big Assets Infra operates large-scale infrastructure. How do you ensure reliability commitments are met across distributed teams?
- How do you manage the tension between shipping fast and maintaining code quality?
- Walk us through how you set and measure engineering KPIs for your team.
- Describe a situation where two senior engineers disagreed on a technical approach. How did you resolve it?
- How do you approach capacity planning when business requirements keep shifting?
- Tell us about a time you influenced a product or business decision without direct authority.
- How do you retain and grow engineers who work primarily on infrastructure and platform components rather than on customer-facing features?
- Describe your experience managing vendor or partner relationships on large infrastructure or asset-heavy projects.
- How do you communicate technical risks and potential delays to non-technical stakeholders?
Sample Answers (STAR Format)
Use these as a starting point. Replace the details with your own real experience.
---
Q: How have you built or restructured an engineering team to meet a fast-changing roadmap?
*Situation:* Our product team had just committed to three major features for a quarter, but my team was structured around a legacy codebase that made parallel delivery nearly impossible.
*Task:* I needed to reorganise the team into smaller, autonomous squads without disrupting an ongoing release cycle.
*Action:* I mapped each feature to a clear owner, ran one-on-ones with every engineer to understand their strengths and preferences, and reorganised into three squads with a shared platform pod for common services. I also negotiated a two-week stabilisation window with the product head before the new structure went live.
*Result:* We shipped two of the three features on time and the third one week late, which the business accepted given the scale of the change. Team satisfaction improved noticeably in our next quarterly survey.
---
Q: Tell us about a time you influenced a product decision without direct authority.
*Situation:* The product team wanted to launch a new data ingestion pipeline in six weeks. My infrastructure team flagged that the proposed approach would create serious reliability risks at scale.
*Task:* I needed to convince a product director and two business stakeholders to adjust the approach, without having any formal authority over the product roadmap.
*Action:* I prepared a short document comparing the two approaches on reliability, maintenance cost, and incident risk, drawing on past incident data from our own systems. I requested a thirty-minute review session, kept it factual, and proposed a phased rollout as a middle ground that kept the business timeline mostly intact.
*Result:* Stakeholders agreed to the phased approach. The first phase launched on the original date and the full rollout followed three weeks later with no major incidents.
---
Q: How do you handle a team member who is consistently missing deadlines?
*Situation:* A senior engineer on my team had been missing sprint commitments for two consecutive quarters. The rest of the team was quietly picking up the slack and resentment was building.
*Task:* I needed to address the performance issue directly while understanding the root cause, and make a clear call if things did not improve.
*Action:* I started with a candid one-on-one to understand what was going on. It turned out the engineer was struggling with unclear requirements and felt reluctant to raise blockers early. I introduced a structured daily async check-in, worked with the PM to sharpen ticket definitions, and set written expectations after each conversation.
*Result:* Over the next six weeks, the engineer's delivery improved significantly. The team dynamic also improved once people saw the issue being handled rather than ignored.
Answer Frameworks
STAR: the foundation for every behavioral question
Every 'tell me about a time' question deserves a Situation, Task, Action, Result structure. Keep the Situation and Task brief, two to three sentences combined. Spend the most time on Action, since that is what the interviewer is actually evaluating. End with a concrete Result, even if it is qualitative rather than numeric.
Influence without authority
For questions about cross-functional decisions or stakeholder management, structure your answer around four points: what was at stake, who had the actual decision-making authority, what data or argument you used to make your case, and how you handled pushback. Big Assets Infra interviewers typically probe for whether you can move things forward without relying on hierarchy.
Tech-to-business translation
When asked how you communicate technical risks, use a three-part structure: what the risk is in plain terms, what the business impact looks like (delay, cost, or reliability), and what options exist with their trade-offs. Avoid jargon. Practice your answer out loud and aim to finish it in under two minutes.
Reliability and scale frame (infrastructure-specific)
For questions about large-scale systems or infrastructure reliability, structure around: what the system requirements were, how your team defined and tracked reliability targets, what the biggest failure mode was, and how you mitigated it. Candidates who speak concretely to on-call processes, post-incident reviews, and SLA ownership typically perform well at companies like Big Assets Infra.
What Interviewers Want
Technical credibility without being a bottleneck
Big Assets Infra interviewers typically look for managers who understand infrastructure and engineering at meaningful depth, but who delegate technical decisions to their teams rather than making every call themselves. Come with specific examples of times you shaped technical direction without owning every design choice.
A real track record of growing people
Expect at least one question on how you helped a struggling engineer improve, or how you helped a strong engineer get promoted. Have two concrete people-development stories ready, one for each direction.
Cross-functional ownership
Candidates report that Big Assets Infra values EMs who treat product, design, and business goals as their own responsibility, not as someone else's problem. Your stories should show you engaging proactively with stakeholders, not just executing what lands in your sprint.
Comfort with ambiguity at scale
Infrastructure work often comes with unclear requirements and shifting priorities. Interviewers typically want to see that you have a process for making decisions under uncertainty: how you gather information, how you document trade-offs, and how you keep the team moving without waiting for perfect clarity.
Data-driven thinking
Be ready to talk about how you measure team health, engineering velocity, and quality. You do not need to cite specific tools, but you should be able to describe what you track, why you track it, and what you do when the numbers move in the wrong direction.
Preparation Plan
Step 1: Build your story bank
Write down several real situations from your career that cover: team restructuring, a major delivery under pressure, a people issue you resolved, a time you influenced without authority, and a reliability or infrastructure challenge. For each story, note the Situation, Task, Action, and Result in bullet points. Do not memorise scripts. Just know the facts cold so you can tell the story naturally.
Step 2: Build infrastructure context
Big Assets Infra focuses on large-scale infrastructure. If you have not worked directly in infra, get comfortable with core concepts: SLAs, incident management, capacity planning, and on-call culture. You do not need to be a systems architect, but you should be able to hold a fluent conversation about these topics without going blank.
Step 3: Practise stakeholder and communication answers
Practise answering 'how would you explain X to a non-technical stakeholder' questions out loud. Record yourself if possible. Most candidates underestimate how important clear verbal communication is in EM interviews, and reading your answers silently does not reveal the gaps.
The day before
Review Big Assets Infra's publicly available information: their products, engineering blog if one exists, and any recent news. Prepare a few thoughtful questions for the interviewers. Good areas to ask about: how engineering and product teams collaborate day to day, what the biggest infrastructure challenge is right now, and how success is measured for a new EM in the first six months.
On the day
For each behavioral question, pause a few seconds before answering. Pick one focused story rather than trying to cover everything. If a question is unclear, ask for clarification before you start your answer.
Common Mistakes
Staying too high-level on the Action step
The most common mistake candidates make in EM interviews is spending too much time on context and too little on what they actually did. Get to your specific actions quickly. Interviewers do not need three minutes of background before you explain your role.
Saying 'we' instead of 'I'
Team credit is admirable, but interviewers are evaluating you. When you say 'we delivered' without explaining your specific role, the interviewer has no data to assess your contribution. Use 'I' for your decisions and actions, and 'my team' for execution.
Treating technical questions as beneath an EM
Some candidates deflect technical questions by saying 'I leave that to my engineers.' This reads as not knowing the answer. At Big Assets Infra, where infrastructure expertise matters, you should be able to engage technically while also showing good judgment about when to defer to specialists.
No concrete results
Every story needs an outcome. 'Things improved' is not a result. 'The team shipped on time and satisfaction improved in the next survey cycle' is a result. Even qualitative outcomes are better than a vague, trailing ending.
Not asking good questions
Candidates who ask no questions, or ask generic questions like 'what does a typical day look like,' miss an opportunity to show genuine interest and strategic thinking. Prepare specific, informed questions based on what you know about Big Assets Infra's business and infrastructure focus.
Question lists and frameworks are curated by knok's career research team from public interview loops at Indian startups and MNCs, hiring-manager debriefs, and candidate reports. Reviewed 2026-10-08. Company-specific loops vary, use as preparation structure, not guarantees.
- Public interview guides (Exponent, company blogs)
- STAR/CIRCLES frameworks, standard PM/eng practice
- India-specific hiring patterns from recruiter interviews
Frequently asked
How many rounds does the Big Assets Infra Engineering Manager interview typically have?
Candidates report that the process typically involves several rounds covering different dimensions. These usually include an initial recruiter screen, behavioral rounds with senior managers or directors, a technical or system design discussion, and sometimes a final round with a VP or cross-functional leader. Round structures can vary by team, so confirm the format with your recruiter before you start preparing.
What salary can I expect for an Engineering Manager role at Big Assets Infra?
Based on knok jobradar data, Manager-level roles in India sit at 35-60 LPA, Senior Manager roles at 55-90 LPA, and Director-track roles at 90-150+ LPA. Actual offers depend on your experience, the specific team, and how you negotiate. For community-reported data points at specific companies, Glassdoor and levels.fyi are good places to cross-check.
Is there a coding round for Engineering Manager interviews at Big Assets Infra?
Candidates report that full coding rounds are uncommon for EM roles, but some teams include a light technical discussion or a system design question to assess engineering depth. You may be asked to review a design document or discuss architecture trade-offs rather than write code. Confirm with your recruiter exactly what to expect for your specific team.
How important is infrastructure domain experience for this role?
Big Assets Infra's core business is large-scale infrastructure, so domain familiarity is a real advantage. Candidates report that interviewers appreciate managers who can speak credibly about reliability, capacity planning, and incident management even if they are not deep infrastructure specialists. If your background is in product engineering, prepare examples that show you have worked closely with infra teams or managed infra-adjacent projects.
How should I prepare if I have not managed a large team before?
Focus on the quality and depth of your management experience rather than team size. Interviewers at this level care more about how you handled a difficult people situation, how you influenced stakeholders, and how you set direction under ambiguity. Be honest about your team size and compensate with specific, well-structured stories that show clear judgment and a willingness to learn.
How can I track and apply to the open Engineering Manager roles at Big Assets Infra?
You can search directly on Big Assets Infra's careers page or on major job portals. If you want a faster approach, knok checks 150+ job sites nightly, applies to jobs that match your resume, and messages HR on your behalf, so you do not miss openings even when you are busy with your current job.
The hard part is getting the interview. knok gets you more.
Upload your resume once. knok searches 150+ job sites every night, applies where you have a real chance, and messages HR for you, so your time goes into interviews, not application forms.