A Software Engineer at BD operates at the critical intersection of advanced medical technology and complex software systems. In this role, you are not merely writing code; you are building the digital infrastructure that powers life-saving medical devices and diagnostic platforms. Your work directly impacts the reliability, precision, and efficiency of systems that healthcare professionals rely on every single day to improve patient outcomes. This position demands a unique blend of technical rigor and a deep understanding of regulated environments. You will navigate the complexities of software development within a global health organization, where quality, safety, and compliance are as vital as functionality. Whether you are working on biosciences instrumentation or integrated systems, your contributions ensure that BD maintains its position as a leader in medical technology, making this a challenging and highly rewarding career path for engineers who value purpose-driven development. 02 · Compensation
Initial Screening
reportedGauge your technical background and interest in the company.
What to demonstrate
- Gauge your technical background and interest in the company
- Depth in Software Engineering
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.
Deeper-Dive Interviews
reportedAssess your core engineering capabilities and team culture fit.
What to demonstrate
- Assess your core engineering capabilities and team culture fit
- Depth in Software Engineering
How to prepare
- Answer aloud and timed: What is your process for ensuring code quality and compliance in a regulated environment?
- Answer aloud and timed: How do you handle data integrity when designing interfaces for medical instrumentation?
Engagement with Peers
reportedInteract with technical peers and engineering leadership.
What to demonstrate
- Interact with technical peers and engineering leadership
- Depth in Software Engineering
How to prepare
- Answer aloud and timed: Explain the difference between synchronous and asynchronous communication in embedded systems.
- Answer aloud and timed: How would you design a software update mechanism that minimizes downtime for a critical medical device?
3 candidate reports. Individual accounts describe a particular role and hiring cycle.
BD Software Engineer interview: resume, fit, and technical conversations
After I applied, recruiting moved quickly into a phone screen about my background, why I wanted the role, and standard behavioral questions. From there, the process mixed manager conversations with technical evaluation, sometimes with senior engineering input. The interviews kept returning to my resume and projects, along with questions about struggles, failures, and overcoming obstacles. Manager…
Read full experienceBD Software Engineer interview with easy assessment and in-person logistics
I had a simple process that still felt somewhat inefficient. It began with a fairly easy online assessment, mostly made up of research-and-knowledge questions, followed by an in-person interview. The stages were clear, and it did not feel like a heavy technical gauntlet. In a similar part of the process, I had two interviews: a phone screen followed by an in-person meeting with different people,…
Read full experienceBD Software Engineer Interview Experience: delayed panels and no follow-through
I started the process with good intentions, but the lack of coordination became frustrating. I arrived early and waited in the security area while the scheduled interview failed to happen. A text eventually said the hiring manager was on medical leave. Instead of a clear reschedule, another manager interviewed me after a long wait. I followed up expecting at least an acknowledgment, but I receive…
Read full experiencePracHub editorial advice for the preparation topics above.
Prioritize Quality
In every technical answer, emphasize how you ensure code reliability and safety. This is the cornerstone of the BD engineering culture.
Be Transparent About Trade-offs
When discussing past designs, do not shy away from the limitations of your approach. Explaining why you made specific trade-offs demonstrates senior-level thinking.
Understand the Domain
Take time to research the specific product lines or bioscience tools related to the team you are interviewing with. Being able to discuss the specific application of your software makes a strong impression.
Do not rush into a solution during a technical problem
Always clarify constraints and edge cases with the interviewer first to demonstrate a systematic approach.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Explain the difference between synchronous and asynchronous communication in embedded systems.
Explain the difference between synchronous and asynchronous communication in embedded systems.
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?
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?
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?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
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?
What is your process for ensuring code quality and compliance in a regulated environment?
What is your process for ensuring code quality and compliance in a regulated environment?
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 software update mechanism that minimizes downtime for a critical medical device?
How would you design a software update mechanism that minimizes downtime for a critical medical device?
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 challenging technical problem you solved; what was the trade-off you had to make?
Describe a challenging technical problem you solved; what was the trade-off you had to make?
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 prioritize technical debt against the need for rapid feature delivery?
How do you prioritize technical debt against the need for rapid feature delivery?
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 approach debugging a system where hardware and software interfaces interact.
Explain how you approach debugging a system where hardware and software interfaces interact.
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?
Walk me through your approach to identifying the root cause of a system failure in a production environment.
Walk me through your approach to identifying the root cause of a system failure 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 BD candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the BD loop
- Write out the reported sequence: Initial Screening, Deeper-Dive Interviews, Engagement with Peers.
- 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 3 reported rounds, with the weakest marked.
02Work Software Engineering
- Spend the session on Software Engineering, which BD candidates report being tested on.
- Write one worked example in Software Engineering and time yourself on it.
Deliverable: One timed worked example in Software Engineering.
03Work Systems Engineering
- Spend the session on Systems Engineering, which BD candidates report being tested on.
- Write one worked example in Systems Engineering and time yourself on it.
Deliverable: One timed worked example in Systems Engineering.
04Work Field Service Engineering
- Spend the session on Field Service Engineering, which BD candidates report being tested on.
- Write one worked example in Field Service Engineering and time yourself on it.
Deliverable: One timed worked example in Field Service Engineering.
05Answer out loud: Technical Competency and Domain Knowledge
- Answer aloud, timed: Explain how you approach debugging a system where hardware and software interfaces interact.
- Answer aloud, timed: Describe a time you had to optimize software performance for a resource-constrained device.
Deliverable: Spoken answers to 2 reported Technical Competency and Domain Knowledge question(s), under time.
06Answer out loud: Problem-Solving and System Design
- Answer aloud, timed: How would you design a software update mechanism that minimizes downtime for a critical medical device?
- Answer aloud, timed: Describe a challenging technical problem you solved; what was the trade-off you had to make?
Deliverable: Spoken answers to 2 reported Problem-Solving and System Design question(s), under time.
07Answer out loud: Behavioral and Collaborative Leadership
- Answer aloud, timed: Tell me about a time you had to collaborate with a cross-functional team (e.g., hardware engineers or product managers) to resolve a conflict.
- Answer aloud, timed: How do you ensure your work aligns with the safety and quality standards of the organization?
Deliverable: Spoken answers to 2 reported Behavioral and Collaborative 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.
Describe a time you had to optimize software performance for a resource-constrained device.
Describe a time you had to optimize software performance for a resource-constrained device.
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 data integrity when designing interfaces for medical instrumentation?
How do you handle data integrity when designing interfaces for medical instrumentation?
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 had to collaborate with a cross-functional team (e.g., hardware engineers or product
Tell me about a time you had to collaborate with a cross-functional team (e.g., hardware engineers or product managers) to resolve a conflict.
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 ensure your work aligns with the safety and quality standards of the organization?
How do you ensure your work aligns with the safety and quality standards of the organization?
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 advocate for a specific technical direction despite pushback.
Describe a situation where you had to advocate for a specific technical direction despite pushback.
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
Describe a time you had to optimize software performance for a resource-constrained device.
- 02
How do you handle data integrity when designing interfaces for medical instrumentation?
- 03
Tell me about a time you had to collaborate with a cross-functional team (e.g., hardware engineers or product managers) to resolve a conflict.
- 04
How do you ensure your work aligns with the safety and quality standards of the organization?
How much time should I dedicate to preparing for the technical interviews?
Dedicate at least 2–3 weeks to review your core technical fundamentals, focusing on systems architecture and debugging scenarios. Practicing how you articulate your past project experiences is just as important as reviewing technical concepts.
BD Software Engineer candidate reports ↗Is the interview process mostly coding or system design?
Expect a mix. While you will be tested on your ability to write clean code, there is a heavy emphasis on your ability to design systems that are robust, safe, and maintainable.
BD Software Engineer candidate reports ↗What is the most important trait for a successful candidate at BD?
A combination of technical rigor and a "quality-first" mindset. You must show that you understand the impact of your code on the end-user and that you take the responsibility of building medical-grade software seriously.
BD Software Engineer candidate reports ↗How can I stand out during the interview?
Show that you understand the "why" behind your technical decisions. When discussing past projects, clearly explain the constraints you faced and how you balanced performance, cost, and safety.
BD Software Engineer candidate reports ↗What topics does BD test in interviews?
BD interviews most often cover Behavioral Interviewing, Communication Skills, Stakeholder Management, Problem Solving, and Conflict Resolution. The exact emphasis depends on the specific role you apply for.
BD 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.
- 01BD 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.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
Zebra Technologies Software Engineer Interview Guide
What Zebra Technologies asks Software Engineer candidates, from reported rounds and questions.
Viasat Software Engineer Interview Guide
What Viasat asks Software Engineer candidates, from reported rounds and questions.
Verily Software Engineer Interview Guide
What Verily asks Software Engineer candidates, from reported rounds and questions.