--- title: Practo Interview Questions & Process (2026) description: Real Practo interview questions and rounds — DSA plus doctor-patient scheduling design under strict health-data privacy constraints — plus how to prepare. url: https://usegreenroom.app/blog/practo-interview-questions last_updated: 2026-07-14 --- ← Back to blog India · Practo # Practo interview questions and process July 14, 2026 · 7 min read ![Practo interview questions — cover from Greenroom, the AI mock interviewer](/assets/blog/practo-interview-questions-hero.webp) A candidate I'll call Neha designed a clean appointment-booking system in her Practo system design round — doctors, time slots, patients, a straightforward booking flow. The interviewer's follow-up: "a patient books a follow-up with a cardiologist and mentions a pre-existing condition in the notes. A completely different doctor at a different clinic, using the same platform, searches for patients with that condition for a research study. Should that second doctor be able to see this patient's note? Walk me through exactly where your design prevents or allows that." Neha's booking system had a notes field. It didn't have an access-control model — and for a healthcare platform where a single leaked note is a real, serious harm, that gap is the whole interview. That's the real shape of **Practo interview questions**: the DSA and machine-coding rounds are familiar if you've prepped for any consumer-scale Indian product company, but the system design round is specifically about doctor-patient scheduling built on top of health data that has to be access-controlled far more strictly than a typical consumer app's data — because the cost of a mistake isn't a bad user experience, it's a real privacy violation. I built Greenroom after freezing in exactly this kind of interview, where the "obvious" scheduling design misses the constraint the whole business is actually built around. This guide covers the real Practo interview process, the questions that come up, and where privacy-constrained scheduling design catches people off guard. ## The Practo interview process Candidates report a loop shaped like this: - **Online assessment** — DSA problems plus a debugging exercise. - **DSA rounds** — arrays, trees, hash maps, judged on working code. - **Machine coding / low-level design round** — a scoped system (appointment booking) built and extended live under a new constraint. - **System design round** — doctor-patient scheduling across clinics, with strict health-data access control. - **Hiring manager + HR** — ownership, project depth, compensation and notice period. Most reported loops run **4 rounds total**. The detail that catches candidates off guard: a scheduling design that's technically correct — no double-booked slots, fast search — can still be disqualifying if it doesn't also enforce who is allowed to see what patient data, since that constraint runs through nearly every feature on the platform, not just a dedicated "privacy" module. ## DSA and coding questions Core data structures and algorithms, with a practical, backend-flavored lean: - **Given a doctor's available time slots and a patient's preferred time range, find the earliest matching slot efficiently.** - **Design a data structure that supports fast conflict detection when booking overlapping appointments across multiple clinics for the same doctor.** - **Given a stream of appointment-booking events, detect and prevent double-booking a doctor for the same time slot.** - **Implement an efficient search that ranks doctors by specialty, location, and availability simultaneously.**
The core truth: DSA at Practo is a gate, not the differentiator — the real test is whether you treat "who is allowed to see this patient's data" as a constraint baked into every query and feature, not a separate access-control layer bolted on afterward.
## Doctor-patient scheduling under privacy constraints — the round every design question leads to This is Practo's signature focus. Expect design prompts and follow-ups that keep circling back to the same underlying question: how do you build a useful, searchable healthcare platform without letting sensitive patient data leak to people who shouldn't see it? - **How would you design access control so a doctor can only see the medical history of patients they've actually treated, not the entire patient database?** - **Design a scheduling system that lets a patient book across multiple clinics and doctors, while keeping each doctor's view scoped to only their own patients.** - **How would you design an audit-logging system that records every access to a patient's health record, in a way that's tamper-resistant?** - **Walk through how you'd handle a patient revoking consent for a doctor to view their history after already sharing it — what actually happens to already-cached or already-viewed data?** Neha's mistake wasn't the booking logic — it was assuming a "notes" field was just data, when a real healthcare platform has to treat every field touching patient information as something requiring an explicit, enforced access policy, checked at query time, not just at the UI layer. Our [system design interview guide](/blog/system-design-interview-guide-india) covers the general framework; Practo's version demands access control as a first-class design element in every answer, not an afterthought. ![Practo interview process — online assessment, DSA rounds, machine coding, system design and HR](/assets/blog/practo-interview-questions-diagram.webp) Scheduling design gets graded against health-data privacy constraints in every round. ## System design questions Beyond the core scheduling-and-privacy questions, expect broader systems questions grounded in Practo's actual domain: - **Design a search system for finding doctors by specialty and location that stays fast as the doctor and clinic database grows into the millions.** - **How would you design a reminder/notification system for upcoming appointments that respects a patient's communication preferences and consent?** - **Design a system that handles a doctor's schedule changing (a clinic closes early) and needs to notify already-booked patients without leaking other patients' booking details.** Work these through the standard skeleton — clarify requirements, propose a data model, pick an access-control and scaling strategy, close with failure modes — but keep the privacy lens active throughout, since that's what Practo's interviewers are actually listening for. ## Behavioral and hiring-manager questions The hiring manager round weighs ownership and precision in reasoning about sensitive-data trade-offs: - **Tell me about a time you had to design something that handled genuinely sensitive user data — what did you do differently because of that?** - **Walk me through a project where you had to balance a useful feature against a real privacy risk.** - **Describe a time you caught or fixed a bug that could have exposed data to someone who shouldn't have seen it.** Our [behavioral interview questions and answers guide](/blog/behavioral-interview-questions-answers-software-engineer) covers structuring these with STAR without sounding rehearsed. ## LeetCode, GeeksforGeeks, ChatGPT — where each fits - **LeetCode** — right for the DSA gate rounds; wrong as the main event, since privacy-constrained scheduling design carries the real weight in this loop. - **GeeksforGeeks interview experiences** — thin for Practo specifically, since healthcare tech is a more specialized category — treat any single report as one data point. - **A healthcare-data or access-control resource** — genuinely necessary here; study role-based and attribute-based access control patterns, consent management, and audit logging specifically, since that's the actual syllabus. - **ChatGPT** — solid for generating practice scheduling-design prompts and sanity-checking a written design; it won't push back on your access-control gap the way a real Practo engineer who's shipped healthcare infrastructure will. - **Greenroom** — the spoken layer. [Ari, the AI interviewer](/), runs a mock system-design round out loud and pushes the "should that other doctor see this note" follow-up Neha got caught on, scoring how rigorously you reason about data access as a first-class constraint. ## How to prepare for the Practo interview - **Week 1:** core DSA — arrays, trees, hash maps — enough to clear the gate round comfortably. - **Week 2:** scheduling system design — conflict-free booking, multi-clinic search, doctor availability — worked through out loud with an access-control lens on every feature. - **Week 3:** privacy-and-consent design — role-based access, audit logging, consent revocation — each explained in under ninety seconds. - **Final week:** one spoken mock where the interviewer pushes a "who's allowed to see this" follow-up on every design choice, plus a sensitive-data-focused behavioral pass. If Practo is one of several consumer-health or scheduling-heavy companies you're targeting, the underlying skill transfers but the constraints shift — our [Urban Company interview questions guide](/blog/urban-company-interview-questions) covers a related two-sided scheduling/matching problem without the health-data privacy layer, and the general [system design interview guide](/blog/system-design-interview-guide-india) covers the framework both loops assume. ## Frequently asked questions ### What questions does Practo ask in a technical interview? Expect DSA and coding fundamentals, a machine-coding round building a scoped system like an appointment-booking system with clean, extensible code, system design questions about doctor-patient scheduling under strict health-data access control (role-based access, consent, audit logging), and behavioral questions about handling sensitive user data. ### How many rounds are in the Practo interview process? Typically an online assessment (DSA plus debugging), DSA rounds, a machine-coding/low-level design round, a system design round, and a hiring manager/HR round — 4 rounds total in most reported cases. ### What makes Practo's system design round different? It's specifically about building a scheduling and search platform on top of sensitive health data, where nearly every feature has to enforce who is allowed to see what. Interviewers want you to design access control, consent, and audit logging as first-class parts of the system, not a bolted-on layer. ### Is the Practo interview process the same for every role? The DSA-plus-machine-coding-plus-privacy-design shape is the default for backend and fullstack roles; frontend roles keep the same DSA and machine-coding structure with JavaScript, framework and performance depth layered on for the design round instead of access-control logic. ### How hard is the Practo interview? It's a consistently high bar rather than a trick-question gauntlet. The part most candidates underprepare for isn't the DSA round — it's realizing that a technically correct scheduling system can still be disqualifying if it doesn't enforce data access as strictly as a healthcare platform requires. ### How is Practo's interview different from other scheduling or marketplace companies? Urban Company's scheduling problem is about matching customers to service professionals with fairness and logistics constraints; Practo's is about scheduling on top of genuinely sensitive health data, where the design has to enforce strict, auditable access control that a typical services marketplace doesn't need to reason about as heavily. Practo's loop is won by treating patient-data access control as a first-class design constraint, not an edge case. Greenroom runs mock system-design interviews with Ari, pushing privacy-specific follow-ups the way a real panel would. Free to start.