Practo, the Bengaluru-based digital healthcare platform, runs a software engineering loop that starts with a DSA-heavy coding screen and moves into practical problem solving and system design.
Expect the online or first technical round to focus on data structures and algorithms at LeetCode medium level: arrays, strings, hashmaps, trees, and dynamic programming show up often. Later rounds go deeper on how you build real systems: API design, database modelling, and low-level design for features like appointment booking, doctor discovery, or consultation flows. Because Practo handles sensitive health data at consumer scale, interviewers care about correctness, edge cases, and reliability, not just a passing solution. Behavioural and hiring-manager rounds probe ownership and how you reason about trade-offs under real constraints.
About Practo
Practo is a Bengaluru health-tech platform with doctor discovery, online consultations, clinic management SaaS (for doctors), and pharmacy delivery across India and Southeast Asia.
Resume screen: relevant projects, internships, and coding fundamentals
Online or first-round coding test: 1-2 DSA problems at medium difficulty
Technical interviews: DSA plus low-level or system design over one or two rounds
Hiring-manager and HR round: ownership, trade-off reasoning, and culture fit
Coding Screen (60-90 min)
1-2 DSA problems (arrays, strings, hashmaps, trees, DP) at LeetCode medium level. Correctness and complexity analysis are the filter.
Technical Deep Dive (45-60 min, one or two rounds)
live problem solving plus low-level or system design for a real feature like appointment booking or doctor discovery, with API and database modelling.
Hiring Manager and HR (30-45 min)
ownership stories, how you handle trade-offs and edge cases, and fit with Practo's mission and team.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical Practo recruitment process has 4 stages: Resume screen: relevant projects, internships, and coding fundamentals → Online or first-round coding test: 1-2 DSA problems at medium difficulty → Technical interviews: DSA plus low-level or system design over one or two rounds → Hiring-manager and HR round: ownership, trade-off reasoning, and culture fit.
Practo typically conducts 3 interview rounds: Coding Screen (60-90 min): 1-2 DSA problems (arrays, strings, hashmaps, trees, DP) at LeetCode medium level. Correctness and complexity analysis are the filter.; Technical Deep Dive (45-60 min, one or two rounds): live problem solving plus low-level or system design for a real feature like appointment booking or doctor discovery, with API and database modelling.; Hiring Manager and HR (30-45 min): ownership stories, how you handle trade-offs and edge cases, and fit with Practo's mission and team..
HireStepX recommends the Clarify-Design-Test framework for this type of interview: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding.
To answer this question well, HireStepX recommends the Clarify-Design-Test approach: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clarify-Design-Test approach: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clarify-Design-Test approach: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clarify-Design-Test approach: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Clarify-Design-Test approach: Clarify requirements and edge cases, design the data structures and API, then walk through complexity and test cases before coding. Ground your answer in a specific real example from your own experience.