Position: Senior Engineer in Test
Company: Evolve Squads
Experience required: 5y
Category: QA Automation
English level: upper
Published: 2021-09-01T00:00:00+03:00

**PROJECT DESCRIPTION:**
We build next-generation Financial software. Our Data and AI-driven solutions help businesses with transparent B2C and B2B banking, credit, and payment solutions.

**PROJECT STACK and TEAM:**
- An engineer in test will do a lot of AUTOMATED testing ONLY. There might be some manual work, but the focus is on lowering manual work to 0% as soon as possible as we are heavily focused on scalability and performance.
- The contractor receives the same benefits as internals.
- The US-based team is in Chicago, IL.
- There is also a large team in Europe, Ukraine (UA team works US hours till 3 pm EST).
- Stand-ups 10-11 am EST, and all hands WED 10-11 am EST (All cadence meetings are before 12pm EST)
- Ruby/RoR + Python + some Java
- Testing is mainly done via Selenium + Cucumber

**Three interview stages:**
1 – Director of an Engineering interview – 30 mins
2 – QA lead meeting – 60 mins deep tech dive
3 – CEO meeting – 20 mins – culture fit

**MAIN REQUIREMENTS:**
We are looking for the first Software Engineer in Test to join our team. Being the first is special because it sets the pattern for future hires in this position.

- 5+ years of professional experience as a backend software engineer for non-trivial web applications
- Experience working with Frontend developers
- Strong communication ability to describe complex problems and solutions
- Experience in an object-oriented programing language such as Ruby, Python, Java, etc.

**JOB RESPONSIBILITIES:**
1) Work closely with DevOps on improving the general execution time of our automated regression system;
2) Build custom Python and Ruby libraries that generate test data, such as product customers approved for a loan in testing;
3) Improve the thImprovety of QA’s automated testing development by designing and implementing better abstractions for the QA team to construct regression tests;
4) Will integrate into various 3rd party test tools to expand the type of testing QA can do;
5) Will build a system to track the long-term QA metrics desired by the VP of Engineering, such as the probability of test failure based on historical unit/regression test runs and code churn.