Multiple QA Automation Role - need only Ex Fidelity Investments
Praveen Jonnalagadda
QA Automation Lead / Architect (1 resource) – 10+ years of experience
Senior Automation Engineers (2 resources)- 7 to 9 years of experience
Automation Engineers / SDET (3 resources)- 5 to 7 years of experience
Location: Boston, MA
This is working on extensive backlog of testing that they have specifically relating to a lot of Post trade systems. Experience with OMS systems and Trading.
These are ALL Cloud based systems. Candidates MUST have strong AWS or its a no go regardless of former Fidelity background. Although you will see Mainframe in here that is a VERY small piece of the work. This is extensively testing Microservices and
API's
Business workflows automation
The critical business workflows that need to be automated include order entry and submission across channels, order lifecycle processing (routing, execution, status updates, amendments, cancellations, corrections), trade processing and validation, and cross-platform interactions between legacy and modern OMS. The exact number of workflows expected to be automated is not specified.
QA automation tools and languages
The existing tools and technologies used for QA automation include a Java-based automation framework, Cucumber for behavior-driven development (BDD), and Selenium for UI automation. While these are the current tools, there is openness to recommendations for enhancements or alternative tools that offer stability, reliability, ease of maintenance, and integration with the existing ecosystem.
CI/CD integration and test migration
Automated tests should be integrated into the CI/CD pipelines to enable automated regression execution and on-demand testing. This integration will involve incorporating the automation framework into build and deployment pipelines, ensuring that test execution is automated and results are reported effectively. While the context does not explicitly state the need to migrate existing automated tests, it suggests reviewing and assessing existing test suites, which may imply that some existing tests could be integrated or migrated to align with the new framework and strategy.
Regression testing challenges and coverage
The current challenges in regression testing cycles include a lack of comprehensive, well-documented regression test coverage across both legacy and modern platforms, and the absence of end-to-end automation that spans these systems. The current level of test coverage is insufficient to support the modernization efforts effectively. The target level is to establish end-to-end regression coverage across key Order Management System (OMS) workflows, ensuring a unified automation framework that supports both legacy and modern OMS, integrated with CI/CD pipelines.
Reliability improvements
The automation framework is expected to improve reliability by reducing regression testing cycle times, enhancing test coverage across critical workflows, and improving the stability and reliability of automated tests. It aims to reduce defect leakage to production, ensure low test flakiness, and provide consistent execution results. Additionally, robust test data management and minimal dependency on static datasets are key aspects of the reliability improvements.
Documentation standards
The QA automation framework requires comprehensive documentation standards, including framework design documentation, runbooks, operational guides, maintenance and extensibility guidelines, and a complete documentation package covering architecture, codebase, and execution processes. Additionally, structured knowledge transfer sessions and transition support to internal teams are essential to ensure the sustainability and extensibility of the automation capabilities.
Compliance and security considerations
The automation framework for the Order Management System modernization must adhere to compliance and regulatory requirements typical for financial systems. This includes ensuring data protection, secure data handling, and maintaining audit trails to comply with financial regulations and security best practices.
Post-implementation support
Post-implementation support is expected to focus on enabling internal teams to sustain and extend the automation capabilities. This includes conducting structured training sessions on framework usage, test development standards, execution, and reporting. Comprehensive documentation will be provided, covering architecture, codebase, and runbooks, to ensure a smooth transition and handover to the internal QA team.
Thanks,
Praveen
Technical Recruiter
IMR Soft LLC
4525 Rt 27 • Princeton, New Jersey 08540
This email and any attachments may contain confidential or proprietary information intended only for the individual or entity to whom it is addressed. If you are not the intended recipient, please notify the sender immediately and delete this message from your system. Any unauthorized review, use, disclosure, copying, or distribution of this communication is strictly prohibited and may violate applicable law. While reasonable efforts are made to ensure the accuracy of the information contained in this email, IMR Soft LLC is not responsible for any inaccuracies or omissions. Any personal remarks or opinions expressed in this email are those of the author and do not necessarily reflect the views or policies of IMR Soft LLC. IMR Soft LLC is an equal opportunity employer and does not discriminate on the basis of race, color, religion, sex, gender identity or expression, sexual orientation, national origin, genetics, disability, age, veteran status, or any other status protected by applicable law.