IT QA / BA Engineer (BDD Engineer)

Assurant Omaha, NE
Imagine coming to work every day in a casual environment where your opinions matter and your voice is heard! This could be you if you begin a career with American Title, Inc, an Assurant Company. ATI was voted Omaha's 2011 and 2014 BEST PLACES TO WORK because we value our employees as much as our clients. Join our fun and challenging work place by applying today!

The BDD Engineer is responsible in describing the business requirements in a narrative using Gherkin language to create scenarios-driven acceptance criteria. These scenarios double as the test cases and provides guidance to the development staff on WHAT to develop. These stories become discussions for the team as the WHAT should describe all the happy path scenarios, failing scenarios, error handling scenarios and any other implementation of business rules unique to clients and or products.

The BDD Engineers will assist the Product Owner in performing manual acceptance tests against the stories that Development has marked as complete. The manual tests should be a direct reflection of the Acceptance Criteria, since all the scenarios were uncovered during the initial definition of stories and backlog grooming step. The acceptance testing will include client specific and product specific testing of business rules. Any new requirements found in this step will result in a new story as they requirement is out of scope of the agreed upon User Story. If one of the scenarios fail, then deliver the story back to Development to work in their normal cadence.

Basic Qualifications:

* 3+ years of experience as a Quality Assurance Tester in an Agile environment

* 2+ years of experience with SQL and API testing

Other Skills:

* Strong knowledge of AGILE practices and AGILE team roles

* Experience with any of the following tools: VSTS,, Selenium, etc.

* Experience working in a Microsoft technologies environment (i.e., .NET, C#, Azure, SQL Server)

* Ability to capture business requirements from the Product Owner. Documenting the details of what the Business Owners are requesting

* Ability to create user story narrative from business requirements. Generate functional scenarios based off business requirements

* Ability to express the story narrative in a manner that describes when I do something then I expect something

* A strong understanding of the Gherkin language defines how we write acceptance criteria

* Ability to describe functional scenarios that are beyond the expected requirements, including explicit error handling scenarios, failing scenarios and unique client-driven requirements

* Strong attention to detail. Clearly define scenarios and requirements to the minutest detail

* Strong documentation skills. Must be able document initial story business requirements and scenarios but must also account for discussions that could generate changes throughout the workflow. Grammar and spelling must be accurate when describing requirements in stories

* Strong communication skills. Communicate changes to the AGILE team given the team requires clarity of existing requirements. Able to gather information from business teams in order to resolve questions from the AGILE team