Kx Quality Assurance Lead - Toronto, Canada - FD Technologies

FD Technologies

Verified Company

Toronto, Canada

2 weeks ago

Posted by:

Sophia Lee

beBee Recruiter

Description

Quality Assurance Lead
KX Ontario, Canada (Remote)

SaveApply

**Lead Quality Assurance Engineer
**Description

This is an excellent opportunity for an experienced Lead Quality Assurance Engineer to join the KX R&D team, working on the world's leading time series database ecosystem.

KX products are built on top of the kdb+ database, which is the world's fastest time series database, written in the q programming language.

The KX Insights Platform is our new microservices cloud native product, with plans to make it a SaaS offering.

Ease of deployment (Kubernetes, Helm charts), ease of use (no-q / low-q), and ease of interoperability (SQL, Python interfaces, Java SDK, C SDK) are key features of KX Insights.

We work with all the major cloud providers.

The agile development teams have excellent quality focus, developing automated CI test cases as they go.

The QA team complements this by developing and executing test frameworks to System Test the KX Insights Platform at scale.

Some QA team members are also embedded in scrum teams.

Our R&D teams are based in Dublin, Belfast, Newry, Budapest, London, New York, Ontario, and Ottawa as well as individual contributors in other locations.

You'll be reporting directly to the VP of QA, who is based in Dublin.

Role

You will be a QA technical lead tasked with improving the quality of our customers' experience in any way you can.
You need to be able to understand complex distributed systems quickly and thoroughly.
You need to be customer focused.
You need to be collaborative, working with the scrum teams and product managers to determine priorities and requirements.
Your primary focus will be the design and development of automated test frameworks, preferably in Python, leveraging available FOSS or 3rd party tools where possible in the areas of:

a. Scalability testing and performance at scale.

i. KX products deal with enormous data flows, which can exceed 150TB a day.

ii.

Different vertical markets have different database schemas, from trivial 3-4 column schemas in some industrial automation or IoT settings, to 1,000-1,500 column schemas in some Telco environments.

We need to be able to test them all. Automated, of course.

b

Resiliency testing:
chaos engineering, fault injection, HA failover, DR.

i. Some vertical markets are 24x7 with requirements for zero downtime.

ii. KX Insights leverages Kubernetes, Helm Charts, Raft, etc., so experience with these technologies is advantageous.

c. Functional Regression

i.

Automated functional regression test framework which is more extensive than the regular CI pipeline such as "nightly" and end-of-sprint tests.

d. Interoperability.

e. Security.

i. Using standard pen test and fuzzing tools.

ii. Static code analyzers, Valgrind, etc. are already used in the CI pipelines.

Work with the various R&D teams and Product Managers to:

a. Gain an understanding of products and components, and specifically any gaps in testing.

b. Be aware of upcoming features and releases, and plan testing efforts accordingly.

c. Review requirements for new features to help identify edge conditions and gaps.

d. Provide "shift left" feedback from QA to dev on any areas of concern.

i. For example, a particular microservice that needs improved resiliency.

i i. Ensure critical issues reported by QA are addressed in a timely manner.

e. Determine how best to automate regression tests for existing products to improve release agility.

f. Resiliency test existing products.

Execute the automated test frameworks, analyze failures, and file good quality JIRA bug reports to facilitate efficient bug fixing.

a) Maintain quality metrics.

Keep abreast of emerging QA tools and best practice.
Work with Customer Success (Support) and Product Managers to understand what issues customers are reporting and plug any gaps in our test coverage.

a. This is "shift left" feedback from Support (customers) to QA.

b.

A KPI for the QA team is the ratio of bugs caught prior to release versus bugs missed by QA and found by customers.

i. We want to make that ratio as high as possible through continuous improvement.

c. Work with Customer Success project teams to identify areas of concern.

i. For example, ease of use, ease of integration with customer apps.

**Qualifications

Computer science degree or equivalent.
8+ years' experience in software test development, with excellent knowledge of Python.
Experience designing and implementing automated test frameworks for complex systems.
System test experience around testing performance at scale, resiliency testing (chaos engineering, fault injection), in cloud native distributed systems and related tools and frameworks.
Experience being a QA technical lead, able to start from scratch and collaborating with colleagues.
Experience debugging complex issues in distributed systems.
Experience reporting out quality metrics and issues of concern to stakeholders.