Apollo 24/7, the digital health arm of Apollo Hospitals, hires software engineers to build a high-traffic platform spanning online consultations, pharmacy, and diagnostics.
The interview loop opens with a DSA and coding round at medium difficulty and progresses into practical engineering: API and database design, low-level design, and system design scaled to a consumer healthcare app. Because the platform touches e-pharmacy orders, lab bookings, and doctor consultations, interviewers probe how you handle concurrency, inventory, order state machines, and data reliability rather than only algorithmic tricks. Expect stack-specific depth for the role you apply to (backend often Java or Node with SQL and NoSQL, frontend on React), plus a hiring-manager round on ownership and how you ship under real deadlines.
About Apollo 24/7
Apollo 24/7 is the digital health platform of Apollo Hospitals, India's largest healthcare group. It offers telemedicine, online pharmacy, diagnostic booking, and AI-powered health records on one app.
Resume screen: projects, internships, and relevant stack experience
Coding or DSA screen: 1-2 medium-difficulty problems, often timed online
Technical rounds: low-level design, system design, and role-specific stack depth
Hiring-manager and HR round: ownership, delivery under deadlines, and culture fit
Coding Screen (60-90 min)
1-2 DSA problems at medium level (arrays, strings, hashmaps, trees, DP). Passing tests plus clean complexity reasoning is expected.
Technical Design (45-60 min, one or two rounds)
low-level and system design for real features like e-pharmacy orders or lab bookings, covering data modelling, concurrency, and order state machines, plus stack-specific questions.
Hiring Manager and HR (30-45 min)
ownership stories, shipping under deadlines, and alignment with Apollo's healthcare mission.
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 Apollo 24/7 recruitment process has 4 stages: Resume screen: projects, internships, and relevant stack experience → Coding or DSA screen: 1-2 medium-difficulty problems, often timed online → Technical rounds: low-level design, system design, and role-specific stack depth → Hiring-manager and HR round: ownership, delivery under deadlines, and culture fit.
Apollo 24/7 typically conducts 3 interview rounds: Coding Screen (60-90 min): 1-2 DSA problems at medium level (arrays, strings, hashmaps, trees, DP). Passing tests plus clean complexity reasoning is expected.; Technical Design (45-60 min, one or two rounds): low-level and system design for real features like e-pharmacy orders or lab bookings, covering data modelling, concurrency, and order state machines, plus stack-specific questions.; Hiring Manager and HR (30-45 min): ownership stories, shipping under deadlines, and alignment with Apollo's healthcare mission..
HireStepX recommends the Requirements-to-Design framework for this type of interview: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases.
To answer this question well, HireStepX recommends the Requirements-to-Design approach: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Requirements-to-Design approach: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Requirements-to-Design approach: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Requirements-to-Design approach: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases. Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Requirements-to-Design approach: Nail functional and non-functional requirements, model the data and APIs, then reason about scale, consistency, and failure cases. Ground your answer in a specific real example from your own experience.