QA Engineer

QA Engineer

New York, NY 3 days a week onsite work Traditional QA Engineer. Core Focus Areas:

• Manual Regression Testing:
  Verifying that new code deployments or updates do not break existing financial reporting, reconciliation tools, or trading logic.
• Functional & Integration Testing:
  Validating the end-to-end flow of transactions, trade life cycles, and data processing between front, middle, and back-office systems.
• Negative & Ad-hoc Testing:
  Intentionally inputting invalid data or unexpected user actions to test application resilience and error-handling capabilities.
• User Acceptance Testing (UAT) Support:
  Serving as a "quality catalyst" by collaborating directly with developers, business analysts, and end-users to manage UAT guidelines and verify real-world operational

Technical and Domain Competencies Traditional QA teams handle highly complex enterprise systems and generally require a specific mix of financial and technical skills:

• Database & Data Integrity:
  High proficiency in writing complex SQL queries to manage and validate financial data stores. Traditional and Cloud Databases.
• System Environments:
  Navigating backend servers using Unix/Linux commands and scripting.
• Domain Knowledge:
  Understanding specific financial structures such as Securities Lending, Equity Swaps, FIX protocols, and T+1 clearance mandates.
• Tool Tracking:
  Rigorous defect logging, sprint tracking, and requirement mapping utilizing platforms like Jira and Bitbucket

Traditional QA at Jefferies rarely exists in complete isolation. The firm leverages a hybrid approach where manual test engineering directly establishes the test cases that drive their automated pipelines (using tools like Selenium, Cucumber, and Playwright) to significantly reduce post-release production defects.