Software Test Engineer

Software Test Engineer

Osirium are looking to a brilliant test engineers for their dev team

About Us

Osirium protects privileged accounts in the hybrid-cloud world by ensuring the right people get least privileged access to the right devices and at the right time. We automate and delegate tasks to reduce costs and record sessions for compliance and accountability. Essentially, Osirium is a password vault on steroids - it not only keeps track of your passwords across a network but also automatically changes them and provides single sign on to your devices and applications. We call this Enterprise Class Password Life Cycle Management, and as you might imagine it needs some serious security engineering.

One of the tricky parts is our session recording, it takes a screen feed from just the session that the SysAdmin is having rather than the whole desktop.

We’re a small and very fast growing cyber-security company. We care about our customers and we care about security, and we care about getting things done. The company is a fun place to work and sometimes feels more like a lab than an office, given all the devices we work with.

We run Scrum, we keep meetings outside of sprint meetings to a minimum, and we score 9 on the Joel test.

About the Role

We're looking for a test engineer that really understands software testing, from unit to integration and on to systems testing. An engineer who can examine a product and know just where to stress it, someone who can create tests that mimic the real world. In short we need someone to make a major contribution to software quality.

Requirements

  • Code you can show us, preferably an active Github profile
  • Experience with testing web based applications
  • Competence with Linux and Git
  • At least some interest in security - you don’t need to be an expert but you do need to care
  • A never stop testing attitude

Nice to Haves

  • A few years of professional software testing experience
  • Experience with network protocols
  • Some lower level understanding, ideally including a bit of Wireshark