Hey, future Test Engineer at Customer.io! We’ve got a nice, cozy spot for you right in between our development and production deployment stages. Yes, you’re sitting *between* two teams, but that doesn’t mean you won’t have the full support of both our engineering and product Amis (people of Customer.io).
You’ll work alongside Joe Purdy, our current test engineer, who rolls with a crew 50% human, 50% animal in Portland, Oregon; and you’ll report into Matthew Newhook, our fixer-in-chief, hailing from St. John’s, Newfoundland.
Let us be more specific. You’re going to own the test phase of Customer.io’s software development lifecycle. You’ll implement manual tests/processes for exploratory fuzz testing, as well as automated integration testing. You’re the go-to advocate for test planning during our product cycles, ensuring new feature development receives ample testing before shipping.
We think you’ll be successful doing all of that here if you’re comfortable with:
- At least one scripting language (like Ruby or Python)
- Linux/Command line applications
- Developing software test plans
- Continuous integration tools (we use Travis-CI)
- API testing
- Acceptance test frameworks (ex. Capybara, Cucumber, Robot Framework, Jasmine)
Bonus points for:
(You should still apply even if this isn’t applicable to your experience)
- Building test frameworks from scratch
- Golang experience
Communication and collaboration are the foundations of this role. We want to talk to you about getting to know a complex product with an existing codebase, and how you would level-up our test processes to improve quality in features and fixes.
Customer.io is growing; if you’re looking for a work environment where processes are set in stone, you won’t find it here. But we’d want you to contribute to that also, to help us define the processes which help us build a great product.