Dorsata · Feb 9th 2021
Employer's note: Location is East Coast-ish. More in the posting below.
We're looking for a new team member to help fill the space around the development process, including both QA and driving the release management process behind our small-and-mighty engineering team. More details about us and about the things we need below, but to shorten it to a few bullet points:
1. Someone needs to test things manually. This is probably 2 days of the sprint (maybe 3 until you get familiar).
2. Someone needs to write automated tests so we don't have to test things manually as much. In other words, automate #1. Also, be the driving force behind getting everyone to write good tests.
3. Do release management. Make sure CI/CD is all set, GitHub merges are happening, merge conflicts are resolved, and probably be the one to hit the sparkly DEPLOY button. (Sorry. There is no sparkly button. Sorry. That seems like a process improvement you can make. See #4.)
4. Improve the release process. We have some Jira-GitHub automation, but it could be better. We have a love/hate (well, tolerate/hate) relationship with our CI platform. Make #3 easier on yourself and the team.
The longer description
We believe that our ability to ship software quickly is a key competitive advantage, and as-such are continually driving ourselves towards a fully realized continuous delivery process. In this role, you will be expected to be a leader towards accelerating this effort, which entails overseeing the full delivery lifecycle - planning the release process as features are being designed / developed, aiding the engineering team's build out of functional & automated testing efforts, assessing the quality criteria of what is shippable, and communicating the timeline and expectations to stakeholders. Furthermore, you’ll be responsible for driving a company culture of fast, reliable software delivery by researching the state of the space, prioritizing areas of investment, and partnering with others to move us forward. This all means that you'll be helping our with the actual testing of the code and driving improvements to how we test. Should we change how we're using our tools to make this better? Drive that discussion. Yes, we're looking for a combination of all of these things! Oh, and if you have an interest ability towards the DevOps world, or you want to wade into the world of data/data management/analysis, or if you want to actually write some application code on the side because it makes you happy, we're small and nimble and have plenty of work to do; the focus is on the getting code out the door, but there's plenty of other things too.
*** _Update on 'Location' : So, while we do have the 'remote' flag on, we're *ideally* looking for someone in the Richmond, VA area-ish (think: 2 hour train ride, so DC to Raleigh to Charlottesville); however, you could live with the NE corridor-ish (think: