As a Software Engineer at Becton Dickinson (BD), you are at the intersection of advanced technology and global healthcare. You are not just writing code; you are building the digital infrastructure that powers medical devices, diagnostic systems, and manufacturing operations that doctors and patients rely on every day. Your work directly contributes to improving patient outcomes and streamlining clinical workflows. The role is both challenging and intellectually rewarding because it requires a blend of high-level software craftsmanship and a deep respect for regulatory rigor. Whether you are working on embedded systems for medical hardware, cloud-based data analytics for diagnostics, or internal manufacturing automation, your contributions are critical to BD’s mission. Expect to work in a collaborative environment where cross-functional communication—bridging the gap between software, hardware, and clinical teams—is as important as your technical proficiency.
Screening Calls
reportedInitial calls to assess high-level fit and resume history.
What to demonstrate
- Initial calls to assess high-level fit and resume history
- Depth in Interview communication skills
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 Deep Dives
reportedIn-depth technical interviews focusing on specific skills and challenges.
What to demonstrate
- In-depth technical interviews focusing on specific skills and challenges
- Depth in Interview communication skills
How to prepare
- Answer aloud and timed: Explain the difference between [Technology A] and [Technology B] and why you would choose one for this role.
- Answer aloud and timed: How do you ensure your code meets quality and regulatory standards?
Behavioral Evaluations
reportedAssessing cultural fit and behavioral competencies through targeted questions.
What to demonstrate
- Assessing cultural fit and behavioral competencies through targeted questions
- Depth in Interview communication skills
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 evaluations above and write down what you would ask to confirm before it.
Final Panel Interviews
reportedPotential final interviews with multiple team members to evaluate overall fit.
What to demonstrate
- Potential final interviews with multiple team members to evaluate overall fit
- Depth in Interview communication skills
How to prepare
- Answer aloud and timed: Tell me about a time you failed to meet a deadline. What did you learn?
- Answer aloud and timed: How do you prioritize tasks when you have multiple competing deadlines?
PracHub editorial advice for the preparation topics above.
Research the specific business unit
BD has many segments. Knowing whether you are interviewing for a diagnostic, surgical, or interventional unit will help you tailor your answers.
Clarify the scope
If a question seems vague, ask for clarification. It demonstrates that you value precision and understand the importance of requirements.
Be ready for panel interviews
You may speak to multiple people in one day. Ensure your narrative regarding your career history is consistent across all interviewers.
Prepare for the "Why BD?" question
Have a thoughtful answer regarding why you want to apply your engineering skills to the healthcare space specifically.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Given a requirement for [specific feature], how would you design the data model?
Given a requirement for [specific feature], how would you design the data model?
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?
Describe your process for unit testing and ensuring high code coverage.
Describe your process for unit testing and ensuring high code coverage.
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 is your approach to legacy code refactoring while maintaining system stability?
What is your approach to legacy code refactoring while maintaining system stability?
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?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Describe the architecture of your most recent project and the technical challenges you faced.
Describe the architecture of your most recent project and the technical challenges you faced.
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 the difference between [Technology A] and [Technology B] and why you would choose one for this role.
Explain the difference between [Technology A] and [Technology B] and why you would choose one for this role.
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 ensure your code meets quality and regulatory standards?
How do you ensure your code meets quality and regulatory standards?
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 me through the steps you would take to design a system that handles [specific data flow].
Walk me through the steps you would take to design a system that handles [specific data flow].
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 approach debugging a complex issue in a production environment?
How do you approach debugging a complex issue in a production environment?
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 Becton Dickinson candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Becton Dickinson loop
- Write out the reported sequence: Screening Calls, Technical Deep Dives, Behavioral Evaluations, 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 Interview communication skills
- Spend the session on Interview communication skills, which Becton Dickinson candidates report being tested on.
- Write one worked example in Interview communication skills and time yourself on it.
Deliverable: One timed worked example in Interview communication skills.
03Work Technical screening / phone screen
- Spend the session on Technical screening / phone screen, which Becton Dickinson candidates report being tested on.
- Write one worked example in Technical screening / phone screen and time yourself on it.
Deliverable: One timed worked example in Technical screening / phone screen.
04Work Managerial interview / hiring manager discussion
- Spend the session on Managerial interview / hiring manager discussion, which Becton Dickinson candidates report being tested on.
- Write one worked example in Managerial interview / hiring manager discussion and time yourself on it.
Deliverable: One timed worked example in Managerial interview / hiring manager discussion.
05Answer out loud: Technical & Domain Expertise
- Answer aloud, timed: Describe the architecture of your most recent project and the technical challenges you faced.
- Answer aloud, timed: How do you approach debugging a complex issue in a production environment?
Deliverable: Spoken answers to 2 reported Technical & Domain Expertise question(s), under time.
06Answer out loud: Behavioral & Leadership
- Answer aloud, timed: Describe a time you had a conflict with a teammate or stakeholder. How did you resolve it?
- Answer aloud, timed: Tell me about a time you failed to meet a deadline. What did you learn?
Deliverable: Spoken answers to 2 reported Behavioral & Leadership question(s), under time.
07Answer out loud: Problem-Solving & Coding
- Answer aloud, timed: Walk me through the steps you would take to design a system that handles [specific data flow].
- Answer aloud, timed: Given a requirement for [specific feature], how would you design the data model?
Deliverable: Spoken answers to 2 reported Problem-Solving & Coding 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.
Can you walk me through a time you had to optimize a piece of software for performance or memory constraints?
Can you walk me through a time you had to optimize a piece of software for performance or memory constraints?
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 a conflict with a teammate or stakeholder. How did you resolve it?
Describe a time you had a conflict with a teammate or stakeholder. 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?
Tell me about a time you failed to meet a deadline. What did you learn?
Tell me about a time you failed to meet a deadline. What did you learn?
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 you have multiple competing deadlines?
How do you prioritize tasks when you have multiple competing deadlines?
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?
Give an example of how you have mentored a junior engineer or contributed to team growth.
Give an example of how you have mentored a junior engineer or contributed to team growth.
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 situation where you had to explain a complex technical concept to a non-technical stakeholder.
Describe a situation where you had to explain a complex technical concept to a non-technical stakeholder.
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 edge cases when designing user-facing applications?
How do you handle edge cases when designing user-facing applications?
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
Can you walk me through a time you had to optimize a piece of software for performance or memory constraints?
- 02
Describe a time you had a conflict with a teammate or stakeholder. How did you resolve it?
- 03
Tell me about a time you failed to meet a deadline. What did you learn?
- 04
How do you prioritize tasks when you have multiple competing deadlines?
How difficult are the technical interviews?
The difficulty varies by team, but generally, expect questions that focus on practical application and system design rather than obscure algorithm puzzles. Be prepared to talk deeply about your resume.
Becton Dickinson Software Engineer candidate reports ↗What is the typical timeline for the hiring process?
While some processes are quick, others can take 1–2 months. We recommend maintaining a steady pace of preparation and keeping other opportunities active during this time.
Becton Dickinson Software Engineer candidate reports ↗How can I stand out as a candidate?
Show genuine interest in Becton Dickinson’s mission. Candidates who can connect their technical skills to the impact on patient care tend to perform better in behavioral and cultural fit rounds.
Becton Dickinson Software Engineer candidate reports ↗Is the interview process mostly remote or onsite?
BD frequently utilizes a hybrid approach, often starting with phone or video screens via Microsoft Teams before moving to in-person or virtual panel interviews.
Becton Dickinson Software Engineer candidate reports ↗What topics does Becton Dickinson test in interviews?
Becton Dickinson interviews most often cover Behavioral Interviewing, Requirements Gathering, Stakeholder Communication, Stakeholder Management, and Problem Solving. The exact emphasis depends on the specific role you apply for.
Becton Dickinson 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.
- 01Becton Dickinson 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.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
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.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.