BD's own careers FAQ frames the loop as four stages (Explore, Apply, Interview, Offer) with a recruiter conversation followed by 2 to 4 further interviews with the hiring manager and future teammates, and it explicitly asks candidates to answer using the STARR method (Situation, Task, Action, Result, Reflection). First-hand reports back that up but show two very different flavours by role. India R&D software interns at BD Technology Campus India (Bengaluru) run through a Mettl aptitude test heavy in DSA/OOPs/OS/aptitude with a brutal 150-to-3 cut, then a Teams technical + resume round, then a director-level round that revisits OOPs concepts and resume projects. US commercial and clinical hires (Associate Territory Manager, Territory Manager, Clinical Specialist in the Advanced Patient Monitoring line ex-Edwards) go through a recruiter screen and a Regional Manager conversation, with candidates reporting that BD's RMs treat it like a live sales call and expect the candidate to 'close' at the end of each round and demonstrate consultative, portfolio-level selling knowledge (needleless blood draw, vascular access, distribution channel management) rather than a single-product pitch. Reddit-side coverage of quality, R&D and non-sales corporate loops is thin (mostly pre-interview 'what should I expect' posts) and no first-hand round-by-round manufacturing or QA writeup surfaced during the harvest window.
These 2 writeups cover software engineering, medical sales, clinical & healthcare and other roles, India R&D campus + US commercial. All of them were posted under a pseudonym (Reddit, GeeksforGeeks or forum handles), so we could not verify the authors’ identities.
BD's applicant FAQ lays out a four-stage flow (Explore, Apply, Interview, Offer). After an initial recruiter conversation candidates typically go through 2-4 more interviews with the hiring manager and future teammates, in a mix of phone, video and in-person formats. BD tells candidates it uses behavioural questions and asks them to answer with the STARR method (Situation, Task, Action, Result, Reflection), and that it evaluates collaboration, problem-solving and innovation against BD's values. No specific assessment tool or hard timeline is disclosed.
R&D Software Intern, BD Technology Campus India (Bengaluru)
Internship
Received an offer3 rounds
1
Mettl online assessmentOnline assessment
One-hour Mettl test in six MCQ sections spanning DSA, OOPs, OS, aptitude, cognitive ability and English grammar. The candidate reports the cut was extremely tight: of about 150 students who sat the test, only 3 were shortlisted to the interview rounds.
Covered · Data structures & algorithms, OOP, Operating systems, Aptitude
2
Technical + resume interviewTechnical
30-minute Microsoft Teams call with two interviewers. They walked through the candidate's prior internship and two resume projects (with focus on a machine-learning project), then posed a string-manipulation problem and discussed optimal approaches. They probed language proficiency (Python, C++, Java) and flagged that Python and ML familiarity would matter for the role.
Covered · Resume deep-dive, Past projects, Arrays & strings
3
Director roundHiring manager
30-minute conversation with a director-level interviewer who opened casually, then re-examined the resume and drilled into OOPs (encapsulation and inheritance with examples) and choice of data structures for given conditions, plus what the candidate knew about BD and the intern role. Feedback was that the technicals were solid with mild anxiety on the DS choice question.
Standard talent-acquisition screen before being passed to the hiring team. The candidate does not detail this round but references it as the first of at least two conversations.
Covered · Resume deep-dive, Behavioral
2
Regional Manager interviewHiring manager
In-depth conversation with the Regional Manager. The candidate found it comfortable and felt they did well on content, but did not 'close' the RM by explicitly asking for the next step at the end of the round. A follow-up email went unanswered. Commenters (including a self-identified BD-adjacent hiring manager) framed this as a real gate at BD: sales interviewers explicitly expect the candidate to align, ask for support in moving to the next step, and demonstrate the same closing behaviour they'd want in front of a customer.
What is the interview process like at Becton Dickinson?
BD's own careers FAQ frames the loop as four stages (Explore, Apply, Interview, Offer) with a recruiter conversation followed by 2 to 4 further interviews with the hiring manager and future teammates, and it explicitly asks candidates to answer using the STARR method (Situation, Task, Action, Result, Reflection). First-hand reports back that up but show two very different flavours by role. India R&D software interns at BD Technology Campus India (Bengaluru) run through a Mettl aptitude test heavy in DSA/OOPs/OS/aptitude with a brutal 150-to-3 cut, then a Teams technical + resume round, then a director-level round that revisits OOPs concepts and resume projects. US commercial and clinical hires (Associate Territory Manager, Territory Manager, Clinical Specialist in the Advanced Patient Monitoring line ex-Edwards) go through a recruiter screen and a Regional Manager conversation, with candidates reporting that BD's RMs treat it like a live sales call and expect the candidate to 'close' at the end of each round and demonstrate consultative, portfolio-level selling knowledge (needleless blood draw, vascular access, distribution channel management) rather than a single-product pitch. Reddit-side coverage of quality, R&D and non-sales corporate loops is thin (mostly pre-interview 'what should I expect' posts) and no first-hand round-by-round manufacturing or QA writeup surfaced during the harvest window.
What topics does Becton Dickinson test in interviews?
Commonly reported topics include Data structures & algorithms, OOP, Operating systems, Aptitude, Resume deep-dive, Past projects.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often; treat this as directional prep, not a script.