As a Software Engineer at Included Health, you will play a pivotal role in shaping innovative solutions that enhance the healthcare experience for users. This position is central to our mission of making healthcare more accessible and effective, ensuring that our products cater to the diverse needs of our users. You will contribute to a wide range of projects, from developing robust software applications to optimizing existing systems, all while collaborating with cross-functional teams to deliver impactful results. The work of a Software Engineer at Included Health not only involves technical expertise but also strategic thinking. You will engage with complex problem spaces where scalability and user experience are paramount. By leveraging modern technologies and methodologies, you will help design and implement systems that are not only efficient but also aligned with our overarching goal of improving health outcomes. As part of a dynamic team, you can expect to tackle challenging problems, drive innovative solutions, and witness the direct impact of your contributions on users' lives.
Initial Screening
reportedCandidates undergo an initial screening to assess basic qualifications and fit for the role.
What to demonstrate
- Candidates undergo an initial screening to assess basic qualifications and fit for the role
- Depth in Event Counter / Time-Series Aggregation
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Assessment
reportedTechnical interviews focusing on coding challenges and system design scenarios are conducted.
What to demonstrate
- Technical interviews focusing on coding challenges and system design scenarios are conducted
- Depth in Event Counter / Time-Series Aggregation
How to prepare
- Answer aloud and timed: How do you ensure code quality and maintainability in a project?
- Answer aloud and timed: Describe a challenging bug you encountered and how you resolved it.
Behavioral Interview
reportedInterviews assess interpersonal skills, cultural fit, and alignment with company values.
What to demonstrate
- Interviews assess interpersonal skills, cultural fit, and alignment with company values
- Depth in Event Counter / Time-Series Aggregation
How to prepare
- Prepare three examples from your own work, each with a decision you made and an outcome you can quantify.
- Re-read the description of the behavioral interview above and write down what you would ask to confirm before it.
Multiple Rounds
reportedCandidates may experience multiple rounds with different team members to evaluate various competencies.
What to demonstrate
- Candidates may experience multiple rounds with different team members to evaluate various competencies
- Depth in Event Counter / Time-Series Aggregation
How to prepare
- Answer aloud and timed: Explain how you would structure a microservices architecture for a healthcare application.
- Answer aloud and timed: What factors do you consider when designing a database schema?
PracHub editorial advice for the preparation topics above.
Prepare for coding challenges
Focus on your problem-solving approach and be ready to think aloud during coding interviews.
Practice behavioral questions
Reflect on past experiences that highlight your teamwork, leadership, and conflict resolution skills.
Know the company mission
Familiarize yourself with Included Health's goals and values to articulate your alignment with their mission during interviews.
Ask questions
Show your interest by asking thoughtful questions about the company culture, team dynamics, and project challenges.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to find the longest substring without repeating characters.
Write a function to find the longest substring without repeating characters.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
How would you implement a binary search algorithm?
How would you implement a binary search algorithm?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Explain the time and space complexity of your solution.
Explain the time and space complexity of your solution.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Can you solve this problem using different data structures?
Can you solve this problem using different data structures?
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
What factors do you consider when designing a database schema?
What factors do you consider when designing a database schema?
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- Handle the rows that do not match: that is usually the actual question.
Follow-up
- How does the query change if that join becomes one-to-many?
- What happens to this when the table is ten times larger?
Find version gaps and relay lag with window functions
outbox_event holds event_id, aggregate_type, aggregate_id, aggregate_version, event_type, payload, status ('pending','published','dead'), attempts, created_at, published_at. A projection is missing rows and you must decide whether the relay skipped events or the consumer dropped them. Write three queries over the last seven days: one listing every aggregate_id whose published aggregate_version sequence has a hole, one giving per-day counts with a running total, and one returning the newest published event per aggregate. For each, say where the window function is evaluated relative to WHERE and LIMIT. PostgreSQL 16.
Approach
- Gaps: compute lead(aggregate_version) OVER (PARTITION BY aggregate_id ORDER BY aggregate_version) in a subquery, then filter next_version <> aggregate_version + 1 in the outer query. Window functions are evaluated after WHERE, GROUP BY and HAVING and before the outer ORDER BY and LIMIT, so the predicate cannot sit in the same WHERE clause and PostgreSQL 16 has no QUALIFY.
- Say what the seven-day filter does to the answer: it truncates every partition, so the first row per aggregate has no predecessor inside the window and a hole spanning the boundary is invisible. Widen the window, or join to resource.version as the authority for the true maximum.
- Running total: SELECT date_trunc('day', created_at) AS d, count() AS n, sum(count()) OVER (ORDER BY date_trunc('day', created_at) ROWS UNBOUNDED PRECEDING). An aggregate inside a window call is legal because grouping runs before windowing. The grouping key is unique per row here so ROWS and RANGE agree, but write the frame anyway — over ungrouped rows with tied timestamps the default RANGE frame pulls in every peer row and the total jumps.
- Newest per aggregate: DISTINCT ON (aggregate_id) ... ORDER BY aggregate_id, aggregate_version DESC is the cheap PostgreSQL-only form when an index matches that order; row_number() OVER (PARTITION BY aggregate_id ORDER BY aggregate_version DESC) = 1 is the portable form and needs a subquery for the same evaluation-order reason as the gap query.
Follow-up
- Relay failover redelivers events. Does a duplicate break the gap query, and how would you detect one from this table alone?
- Turn the gap check into a continuous monitor rather than a query someone runs after an incident. What does it watch?
What are the key differences between REST and GraphQL?
What are the key differences between REST and GraphQL?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
Explain the MVC architecture and its components.
Explain the MVC architecture and its components.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
How do you ensure code quality and maintainability in a project?
How do you ensure code quality and maintainability in a project?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a challenging bug you encountered and how you resolved it.
Describe a challenging bug you encountered and how you resolved it.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you design a URL shortening service?
How would you design a URL shortening service?
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Explain how you would structure a microservices architecture for a healthcare application.
Explain how you would structure a microservices architecture for a healthcare application.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Discuss how you would handle data consistency in a distributed system.
Discuss how you would handle data consistency in a distributed system.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Describe a system you've designed in the past and the trade-offs you considered.
Describe a system you've designed in the past and the trade-offs you considered.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Walk us through your thought process in solving a complex problem.
Walk us through your thought process in solving a complex problem.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How would you approach a project with incomplete requirements?
How would you approach a project with incomplete requirements?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
What steps would you take to optimize the performance of an application?
What steps would you take to optimize the performance of an application?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe a scenario where you had to make a decision with limited information.
Describe a scenario where you had to make a decision with limited information.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
How do you approach learning new technologies or languages?
How do you approach learning new technologies or languages?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Describe your approach to debugging code.
Describe your approach to debugging code.
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- Separate the trigger from the cause; the deploy is rarely the bug.
Follow-up
- What would you look at first, and what would it rule out?
- How would you tell a cause from a coincidence here?
Built from the rounds and topics Included Health candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Included Health loop
- Write out the reported sequence: Initial Screening, Technical Assessment, Behavioral Interview, Multiple Rounds.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work Event Counter / Time-Series Aggregation
- Spend the session on Event Counter / Time-Series Aggregation, which Included Health candidates report being tested on.
- Write one worked example in Event Counter / Time-Series Aggregation and time yourself on it.
Deliverable: One timed worked example in Event Counter / Time-Series Aggregation.
03Work Systems Design
- Spend the session on Systems Design, which Included Health candidates report being tested on.
- Write one worked example in Systems Design and time yourself on it.
Deliverable: One timed worked example in Systems Design.
04Work Problem Solving (Logic-Based)
- Spend the session on Problem Solving (Logic-Based), which Included Health candidates report being tested on.
- Write one worked example in Problem Solving (Logic-Based) and time yourself on it.
Deliverable: One timed worked example in Problem Solving (Logic-Based).
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: What are the key differences between REST and GraphQL?
- Answer aloud, timed: Explain the MVC architecture and its components.
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: System Design / Architecture
- Answer aloud, timed: How would you design a URL shortening service?
- Answer aloud, timed: Explain how you would structure a microservices architecture for a healthcare application.
Deliverable: Spoken answers to 2 reported System Design / Architecture question(s), under time.
07Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Can you describe a time when you had to navigate a conflict within a team?
- Answer aloud, timed: How do you handle failure or setbacks in projects?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
What is your experience with cloud services such as AWS or Azure?
What is your experience with cloud services such as AWS or Azure?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Can you describe a time when you had to navigate a conflict within a team?
Can you describe a time when you had to navigate a conflict within a team?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you handle failure or setbacks in projects?
How do you handle failure or setbacks in projects?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
What motivates you to do your best work?
What motivates you to do your best work?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Discuss an instance where you took the initiative on a project.
Discuss an instance where you took the initiative on a project.
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
How do you prioritize tasks when working on multiple projects?
How do you prioritize tasks when working on multiple projects?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
What is your experience with cloud services such as AWS or Azure?
- 02
Can you describe a time when you had to navigate a conflict within a team?
- 03
How do you handle failure or setbacks in projects?
- 04
What motivates you to do your best work?
How difficult are the interviews, and how much preparation time is typical?
The interviews at Included Health can vary in difficulty, with a mix of technical and behavioral questions. Candidates typically spend 2-4 weeks preparing, focusing on technical skills and understanding the company's values.
Included Health Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates demonstrate a strong technical foundation, excellent problem-solving skills, and the ability to communicate effectively. They also align their values with those of Included Health, showcasing a commitment to improving healthcare.
Included Health Software Engineer candidate reports ↗What is the culture and working style at Included Health?
The culture at Included Health emphasizes collaboration, inclusivity, and a shared mission of improving healthcare access. Employees are encouraged to contribute ideas and work as part of a cohesive team.
Included Health Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can range from a few weeks to a couple of months, depending on the number of candidates and interview rounds. Candidates should be prepared for multiple interviews and potential follow-up discussions.
Included Health Software Engineer candidate reports ↗Are there remote work or hybrid expectations?
Included Health offers flexible work arrangements, including remote and hybrid options, to accommodate employees' needs and promote work-life balance.
Included Health Software Engineer candidate reports ↗What topics does Included Health test in interviews?
Included Health interviews most often cover Stakeholder Management, System Design, Problem Solving, Leadership, and Data Analysis. The exact emphasis depends on the specific role you apply for.
Included Health Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Included Health Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Together Ai Software Engineer Interview Guide
Failure-handling practice for Together Ai software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Lambda Software Engineer Interview Guide
Failure-handling practice for Lambda software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.