At Johnson & Johnson, a Software Engineer sits at the critical intersection of advanced technology and life-saving healthcare innovation. You are not just writing code; you are building the digital infrastructure that supports medical device development, supply chain optimization, and research-driven solutions. Your work directly impacts the company’s ability to deliver high-quality patient care, necessitating a high degree of technical precision and regulatory awareness. This role is both complex and deeply rewarding. You will likely engage with cross-functional teams, ranging from research scientists to clinical experts, to translate abstract requirements into scalable, compliant software solutions. Whether you are working on cloud environments, embedded systems, or enterprise-level applications, you will be expected to balance rapid innovation with the stringent safety and quality standards that define Johnson & Johnson.
Initial Screening
reportedVerification of basic qualifications and interest, often via a recruiter or an automated platform like HireVue.
What to demonstrate
- Verification of basic qualifications and interest, often via a recruiter or an automated platform like HireVue
- Depth in Spring Boot
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.
Virtual/In-Person Interviews
reportedSeries of interviews with hiring managers and cross-functional team members to evaluate technical skills and cultural fit.
What to demonstrate
- Series of interviews with hiring managers and cross-functional team members to evaluate technical skills and cultural fit
- Depth in Spring Boot
How to prepare
- Answer aloud and timed: What is your experience with microservices architecture and managing transactions in distributed systems?
- Answer aloud and timed: How do you ensure data privacy and security when building cloud-based applications?
Technical Presentations/Case Studies
reportedPotential multi-stage panels that may include technical presentations or case studies.
What to demonstrate
- Potential multi-stage panels that may include technical presentations or case studies
- Depth in Spring Boot
How to prepare
- Answer aloud and timed: Can you walk us through your process for debugging a complex system issue?
- Answer aloud and timed: Why do you want to work for Johnson & Johnson specifically?
Final Panel Interviews
reportedConcluding interviews that assess overall fit and readiness for the role.
What to demonstrate
- Concluding interviews that assess overall fit and readiness for the role
- Depth in Spring Boot
How to prepare
- Answer aloud and timed: Describe a time you had to handle a conflict within your team. How did you resolve it?
- Answer aloud and timed: Can you share an example of a time you had to make an ethical decision at work?
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Johnson Software Engineer interview: two virtual rounds with the decision-maker
I had two virtual interviews, moving directly from the first to the second. The employer or person responsible for the final decision was present in both. Other team members joined the second round, giving it a panel format. We focused on my background and fit. It was a structured conversation with several perspectives. Although the process was short in terms of rounds, I felt they were actively…
Read full experienceJohnson Software Engineer interview: unclear recruiter process
Recruiters contacted me after I applied, but the process was hard to understand from the beginning. Their conversations were direct and gave little detail about what to expect or how long things might take. After the interview, I stopped hearing anything about the role. I could not gauge whether I was progressing or whether another step was coming. It did not feel transparent, and the lack of upd…
Read full experiencePracHub editorial advice for the preparation topics above.
Review Your Projects
Be prepared to present a deep dive into a past project. You should be able to explain the architecture, the challenges, and the specific impact you made.
Ask Strategic Questions
Use the end of your interview to ask about the team’s current technical hurdles or how they balance innovation with compliance.
Master the STAR Method
Keep your answers concise and structured, focusing on the "Result" to show that you are an outcome-oriented engineer.
Be Transparent
If you don't know an answer, communicate your thought process. Interviewers often value how you approach a problem more than the final answer itself.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Can you explain the difference between processes and threads, or multitasking versus multithreading?
Can you explain the difference between processes and threads, or multitasking versus multithreading?
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Collapse a redelivered event batch into per-aggregate high-water marks
You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.
Approach
- One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
- Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
- Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
- If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.
Follow-up
- The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
- How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?
Explain why the owner filter ignores the listing index
The only index on resource is (tenant_id, status, updated_at DESC, resource_id DESC). A new endpoint returns one user's resources across all statuses, newest created first: WHERE tenant_id = $1 AND owner_user_id = $2 ORDER BY created_at DESC LIMIT 20. On a tenant with 2M rows it takes 900 ms and EXPLAIN shows a sort above a large scan. Explain precisely why the existing index cannot serve it, give the index that can, and state which of these the new index still will not help: owner_user_id alone across tenants; the same query ordered by updated_at. PostgreSQL 16.
Approach
- Separate the two jobs an index does. For filtering, a composite btree is seekable only on a left prefix, so with no predicate on status the scan can at best range over tenant_id and test owner_user_id per row; PostgreSQL 16 has no btree skip scan to jump the unconstrained column.
- For ordering, the index is sorted by (status, updated_at) within a tenant and not by created_at, so the LIMIT cannot stop early: every matching row is read and then sorted. That is the 'Sort Method: top-N heapsort' line, and it is why the plan reads 2M rows to answer with 20.
- Derive the replacement from the access path — equality, equality, then the ordering column: CREATE INDEX CONCURRENTLY ON resource (tenant_id, owner_user_id, created_at DESC). The scan seeks to the (tenant, owner) range and walks 20 entries in order, so the Sort node disappears along with the row-read.
- Treat INCLUDE (title, status) as conditional, not free. An index-only scan still visits the heap for any row whose page is not marked all-visible, so on a table taking 1.2k writes/second the win depends on autovacuum keeping the visibility map current, and the wider index costs more on every insert.
Follow-up
- 90% of rows are status='active'. Would a partial index WHERE status = 'active' change your answer, and for which of the three queries?
- A dashboard runs this for 40 owners in one page load. What changes about the design?
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?
How do you approach systems integration and defect tracking in a regulated environment?
How do you approach systems integration and defect tracking in a regulated environment?
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?
What is your experience with microservices architecture and managing transactions in distributed systems?
What is your experience with microservices architecture and managing transactions in distributed systems?
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 data privacy and security when building cloud-based applications?
How do you ensure data privacy and security when building cloud-based applications?
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?
Walk us through a past project—what were the primary technical challenges, and how did you solve them?
Walk us through a past project—what were the primary technical challenges, and how did you solve them?
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 prioritize tasks when faced with competing technical requirements?
How do you prioritize tasks when faced with competing technical 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?
If you were given a legacy system to modernize, where would you start?
If you were given a legacy system to modernize, where would you start?
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 testing and quality assurance—how do you ensure your code is production-ready?
Describe your approach to testing and quality assurance—how do you ensure your code is production-ready?
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?
Can you walk us through your process for debugging a complex system issue?
Can you walk us through your process for debugging a complex system issue?
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 Johnson candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Johnson loop
- Write out the reported sequence: Initial Screening, Virtual/In-Person Interviews, Technical Presentations/Case Studies, Final Panel Interviews.
- 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 Spring Boot
- Spend the session on Spring Boot, which Johnson candidates report being tested on.
- Write one worked example in Spring Boot and time yourself on it.
Deliverable: One timed worked example in Spring Boot.
03Work System Design
- Spend the session on System Design, which Johnson candidates report being tested on.
- Write one worked example in System Design and time yourself on it.
Deliverable: One timed worked example in System Design.
04Work DSA (Data Structures & Algorithms)
- Spend the session on DSA (Data Structures & Algorithms), which Johnson candidates report being tested on.
- Write one worked example in DSA (Data Structures & Algorithms) and time yourself on it.
Deliverable: One timed worked example in DSA (Data Structures & Algorithms).
05Answer out loud: Technical & Domain Knowledge
- Answer aloud, timed: How do you approach systems integration and defect tracking in a regulated environment?
- Answer aloud, timed: Can you explain the difference between processes and threads, or multitasking versus multithreading?
Deliverable: Spoken answers to 2 reported Technical & Domain Knowledge question(s), under time.
06Answer out loud: Behavioral & Values-Based
- Answer aloud, timed: Why do you want to work for Johnson & Johnson specifically?
- Answer aloud, timed: Describe a time you had to handle a conflict within your team. How did you resolve it?
Deliverable: Spoken answers to 2 reported Behavioral & Values-Based question(s), under time.
07Answer out loud: Problem-Solving & Methodology
- Answer aloud, timed: Walk us through a past project—what were the primary technical challenges, and how did you solve them?
- Answer aloud, timed: How do you prioritize tasks when faced with competing technical requirements?
Deliverable: Spoken answers to 2 reported Problem-Solving & Methodology 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.
Why do you want to work for Johnson & Johnson specifically?
Why do you want to work for Johnson & Johnson specifically?
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?
Describe a time you had to handle a conflict within your team. How did you resolve it?
Describe a time you had to handle a conflict within your team. How did you resolve it?
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 share an example of a time you had to make an ethical decision at work?
Can you share an example of a time you had to make an ethical decision at 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?
How do you demonstrate the Credo values (putting patients first) in your daily engineering tasks?
How do you demonstrate the Credo values (putting patients first) in your daily engineering tasks?
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?
Tell us about a project where you had to learn a new technology quickly to meet a deadline.
Tell us about a project where you had to learn a new technology quickly to meet a deadline.
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
Why do you want to work for Johnson & Johnson specifically?
- 02
Describe a time you had to handle a conflict within your team. How did you resolve it?
- 03
Can you share an example of a time you had to make an ethical decision at work?
- 04
How do you demonstrate the Credo values (putting patients first) in your daily engineering tasks?
How long does the hiring process usually take?
It can vary significantly, ranging from a few weeks to several months depending on the team and location. It is common to have a 2–3 week wait between major interview stages.
Johnson Software Engineer candidate reports ↗Are coding challenges common?
Yes, but they often focus on practical application rather than obscure algorithmic puzzles. Be prepared to discuss your code implementation and the logic behind your specific choices.
Johnson Software Engineer candidate reports ↗How important is the Credo?
It is fundamental. Interviewers look for evidence that you are a values-driven engineer who prioritizes quality and ethics in every line of code you write.
Johnson Software Engineer candidate reports ↗Is there a specific dress code or tone for interviews?
Johnson & Johnson is a professional environment. Aim for business casual, and maintain a tone that is respectful, collaborative, and focused on long-term problem solving.
Johnson Software Engineer candidate reports ↗What topics does Johnson test in interviews?
Johnson interviews most often cover Behavioral Interviewing, Machine Learning (core concepts), DSA (Data Structures and Algorithms), Presentation Skills, and Case Study Problem Solving. The exact emphasis depends on the specific role you apply for.
Johnson 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.
- 01Johnson 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.
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.
Confluent Software Engineer Interview Guide
Concurrency exercises for Confluent candidates: check-then-act races, deadlock from inconsistent lock ordering, and why two individually atomic operations do not compose into an atomic update.
Capital One Software Engineer Interview Guide
Code-reading and review practice for Capital One candidates: tracing unfamiliar control flow, finding the invariant a function quietly depends on, and separating a correctness defect from a matter of taste.