QA/TestingAround since 2006
BDD
Also written as Behavior-Driven Development, Cucumber, Gherkin
A testing approach that writes test scenarios in structured, plain-English-like sentences (Given/When/Then) so non-engineers (like product or QA) can read and help write them.
Think of it like
Like writing a recipe in plain instructions anyone in the kitchen can follow, instead of a chef's private shorthand notes.
Junior or senior?
Junior sounds like
Writes BDD-style scenarios alone, with no non-engineer input despite the format's intent.
Senior sounds like
Can say honestly whether product or QA actually contributed to them.
Ask them
“Did anyone outside engineering actually write or review your BDD scenarios, or did they end up being engineer-only in practice?”