Pravin Premdas | QuantumLoopAI Interview Preparation QuantumLoopAI Business Analyst – Interview Preparation 1. Tell me about yourself Hi, I am Pravin Premdas. I have over six years of experience working on SaaS, eCommerce, ERP, and OMS projects. In my previous roles, I worked with enterprise clients and supported requirements gathering, project coordination, stakeholder communication, UAT, risk tracking, and go-live activities. I also worked on eCommerce migration projects, coordinating between clients, business teams, and technical teams. One of my strengths is understanding technical topics and explaining them clearly to business users. I am now looking to move into a Business Analyst/Project Coordinator role where I can use my experience in requirements, delivery coordination, and client communication while continuing to grow in product and healthcare technology. 2. Why this role and QuantumLoopAI? I am interested in this role because it combines business analysis, project coordination, product delivery, and client communication, which are areas I have already worked in. I am also interested in QuantumLoopAI because EMMA addresses a clear operational problem in NHS primary care: high call volumes and pressure on GP reception teams. The product combines AI, workflow automation, and patient access, which makes the role especially interesting to me. My experience with SaaS implementations, eCommerce, UAT, and go-live activities would help me contribute to client onboarding and delivery. I also like the fast-moving environment because it gives me the opportunity to take ownership and learn new things. 3. How do you approach requirements from discovery through delivery? I normally start by understanding the business problem rather than immediately discussing a solution. I try to understand the users, process owners, teams involved, and systems affected. I use discussions, process walkthroughs, existing documents, and examples of current problems. I ask about the current process, desired outcome, business rules, exceptions, data, dependencies, and success measures. Once I understand the requirement, I document it with clear acceptance criteria and review it with the business, product, technical, and QA teams. I then track the requirement through development and UAT and follow up on open questions until it is agreed and delivered.

Pravin Premdas | QuantumLoopAI Interview Preparation 4. Tell me about a real project where you gathered requirements and handled stakeholder disagreement One example was an eCommerce migration project where we were moving a customer from a legacy platform to our SaaS platform. During the project, the client also wanted additional features before go-live, while the engineering team was concerned about the timeline and delivery risk. I first understood the client’s business needs and separated the critical requirements from future improvements. Then I discussed the effort, dependencies, testing, and risks with the engineering team. I presented options to the client, including delivering the critical items first and moving the less important features to a later phase. We agreed on a phased approach. I documented the decision, updated the plan, and continued tracking the requirements through UAT. As a result, we protected the go-live scope, addressed the important business needs, and avoided uncontrolled scope. 5. How do you handle changing requirements and prioritize them? When a requirement changes, I first understand why the change is needed and what business problem it solves. Then I look at business value, urgency, customer impact, technical effort, dependencies, and the effect on the timeline. I discuss the impact with the relevant teams and look at the available options. We might replace a lower-priority item, move the change to a later release, extend the timeline, or deliver it in phases. Once a decision is made, I update the backlog, project plan, risks, dependencies, and stakeholder communication. My main focus is to make the trade-offs clear so everyone understands the impact before making a decision. 6. How do you write and validate a good requirement or user story? I make sure the requirement clearly explains who the user is, what they need to do, and why they need it. For a user story, I normally use: “As a user, I want to do something, so that I can achieve a specific outcome.” I then add acceptance criteria, business rules, assumptions, dependencies, and relevant examples. I review the requirement with the business and technical teams to make sure it is clear, realistic, measurable, and testable. I also check edge cases and dependencies. Finally, I connect the requirement to UAT scenarios so there is a clear link from the business need through delivery and testing. 7. How do you manage UAT, risks, and blockers? For UAT, I first confirm the scope, test scenarios, users, and acceptance criteria. During testing, I track defects and enhancement requests separately, make sure each issue has an owner, and coordinate retesting.

Pravin Premdas | QuantumLoopAI Interview Preparation For risks, I try to identify them early by looking at scope, dependencies, resources, integrations, timelines, and stakeholder availability. I record the impact, owner, mitigation, and target date. When there is a blocker, I understand its impact, identify the right owner, agree on the next action, and communicate any effect on the timeline. If it cannot be resolved at the working level, I escalate it with the context and possible options. 8. How do you manage multiple projects, priorities, and deadlines? I keep important information visible in a central tracker, including milestones, dependencies, risks, owners, and next actions. When I have several priorities, I look at customer impact, deadlines, business value, risk, and blockers. I use regular check-ins and status updates to identify where decisions or follow-ups are needed. I also make sure important actions and decisions are documented rather than relying on memory or informal messages. If priorities conflict, I make the trade-off clear and get alignment on what should come first. 9. How do you communicate and manage stakeholders? I adjust the level of detail depending on who I am speaking to. With business stakeholders, I focus on outcomes, customer impact, timelines, risks, and decisions. With technical teams, I provide more detail around requirements, data, integrations, dependencies, acceptance criteria, and edge cases. If a stakeholder is not responding, I make my request clear, explain exactly what I need, provide the deadline and impact of a delay, and use another channel if needed. I escalate respectfully when the delay affects delivery. After important discussions, I send a short summary of decisions, actions, owners, and dates so everyone has the same reference point. 10. How do you use data in your work? I use data to understand what is happening, check assumptions, and support decisions. For example, I have used project trackers to compare planned and actual progress across requirements, defects, and UAT activities. This can help identify whether a delay is caused by development effort, pending client decisions, dependencies, or unresolved defects. I use spreadsheets to compare progress, identify overdue actions, and look for trends. If a project repeatedly slows down in one area, I investigate ownership, approvals, dependencies, and defect patterns before recommending a change.

Pravin Premdas | QuantumLoopAI Interview Preparation 11. How would you approach onboarding a new client? I would start by understanding the client’s goals, scope, stakeholders, timeline, technical environment, and success criteria. Then I would understand the current process and identify what needs to be configured, integrated, tested, or explained. I would create an onboarding plan covering requirements, setup, configuration, training, UAT, go-live, and post- launch support. I would track risks and dependencies and keep regular communication with the client. Before go-live, I would confirm that UAT is complete, users are ready, open risks are understood, contingency steps are clear, and ownership after launch is agreed. 12. How would you work on an AI product used in healthcare? I would treat safety and patient impact as priorities. I would make sure the requirements clearly distinguish administrative requests from situations requiring clinical review or human escalation. I would also consider privacy, auditability, access control, failure handling, and clear messaging when the AI is uncertain. During testing, I would include normal scenarios, edge cases, different ways patients may describe the same issue, and situations involving vulnerable users. I would work closely with product, engineering, operations, client teams, and relevant healthcare safety and compliance stakeholders before release. 13. What are your strengths and what are you improving? My main strengths are communication, coordination, and taking ownership. I am comfortable taking a broad requirement, breaking it into clear actions, and working with technical teams until delivery is complete. I am also good at identifying risks and dependencies early. One area I have improved is documentation. Earlier in my career, I sometimes spent too much time trying to make a document perfect before sharing it. I learned that early feedback is more useful, so now I share a clear first version, highlight assumptions or open questions, and get feedback early while still maintaining accuracy. 14. Why should we hire you, and why are you applying for a junior role? I bring a combination of business analysis, project coordination, technical delivery, and client-facing experience. I can contribute from the beginning through requirements gathering, documentation, UAT, project tracking, stakeholder communication, and implementation support. Although I have experience in several areas of delivery, I am interested in this role because it gives me the opportunity to focus more deeply on business analysis, product workflows, and client outcomes. I am keen to learn the company’s product, healthcare domain, and internal processes.

Pravin Premdas | QuantumLoopAI Interview Preparation I am more focused on the responsibilities, impact, and opportunity to grow than on the job title. 15. What tools have you used? I have worked in Agile delivery environments and have mainly used Jira for sprint planning, backlog tracking, issue management, and delivery reporting. I have also used Google Sheets and similar tracking tools for milestones, risks, dependencies, and status reporting. I would be honest about the tools I have and have not used, but the underlying processes—requirements, work tracking, status reporting, and stakeholder communication—are things I am already comfortable with. I can learn the specific tools and templates used by the team. 16. What are your salary expectations? My last CTC was ₹10.56 LPA. Based on the responsibilities, remote setup, UK business-hour alignment, and my experience in SaaS delivery, requirements, client coordination, and go-live management, I would be looking at around ₹17 LPA. I am open to discussing the complete compensation package, responsibilities, benefits, and growth opportunity. 17. Do you have any questions for us? Yes. I would like to understand what success would look like for this role in the first 90 days. I would also like to know whether the role is focused more on internal business analysis, client onboarding, implementation delivery, or a combination of these areas. How are responsibilities divided between Business Analysis, Product, Engineering, and Client Success? How does the team capture and prioritize feedback from GP surgeries and healthcare users? Finally, what tools and templates does the team currently use for requirements, project tracking, and client onboarding? Final preparation reminders Speak naturally and use real examples where possible. Add measurable results when you can, such as project duration, number of users, integrations, defects reduced, or whether the project went live on time. Be honest about tools and experience. For healthcare AI questions, keep patient safety, privacy, auditability, uncertainty, and human escalation central.