Senior Software Engineer, Span.IO

• Proven experience as a Software Engineer
• Proficiency building reliable and maintainable tools and services in Python
• Proficiency in one of SPAN’s coding language: Python, JavaScript and frameworks such as ReactJS, React Native, Detox (or Appium), and Kotlin
• Strong knowledge of software testing methodologies, test case design and automated testing
• Experience with CI/CD tools and Github (i.e, CircleCI, Docker)
• Effective communication and collaboration skills
• Ability to work independently and as part of a team
• Comfort building and working in greenfield automated testing frameworks and infrastructure

Desirable

• As a Software Engineer you will play a crucial role in ensuring the quality and reliability of our products through a combination of automated and manual testing methodologies
• This is a high impact role that will work closely with SPAN’s internal Software, Device Software, Hardware Engineering, Systems and QA teams
• Develop and maintain automation framework, driver library and consumer facing dashboards
• Supporting DSW with HITL testing, Reliability, QA and Systems testing
• Document defects, issues, and enhancement requests clearly and concisely
• Participating in requirements review and systems engineering planning to determine high-leverage opportunities for automation
• Working with the firmware team to ensure that engineering SDKs to the hardware have required capabilities for automated tests (e.g., structured log capture). Working with the firmware, systems and hardware teams to efficiently triage issues
• Commissioning, standing up, and maintaining a worker pool of hardware test cells (‘device under test’) for DVT and production hardware. Worker pool capacity planning and commissioning of new test cells as usage and wait time increases
• Reliable on-premise workflow scheduling and orchestration of test sequences on hardware, and the integration of these workflows to engineering CI/CD systems
• Machine specification of test scenarios and acceptance criteria, and traceability with external requirements management tools (Jama)
• Storage of raw log data to external object storage (S3), and structured test result data to Postgres (Currently done with Chronos)
• Reporting web dashboards that provide clarity around pass/fail criteria for software releases, as well as other leading, non-deterministic reliability indicators (e.g., ‘crashiness’). Ensuring that these dashboards surface critical failing cases to the engineering team and that underlying issues can be efficiently identified
• Monitoring of both physical test cell and web infrastructure uptime, capacity and reliability
• Identify areas for process improvement and actively contribute to enhancing software development and testing practices pertaining to automation