About the Role

Remediant is looking for an Integration Developer to join our engineering team. We help secure access to critical systems in industries ranging from defense contractors to pharmaceutical companies. Our flagship product, SecureONE, enables our customers to deploy a “just-in-time-administration” stance that prevents attackers from gaining a foothold in their networks.

We are looking for people who have a track record of taking a pragmatic approach to solving technical problems. You will join a team working on maintaining and adding features to SecureONE alongside teammates with previous experience in IT, security, system log analysis, payments, digital imaging, and pharmaceuticals.

You do not need to have any previous experience in information security — and this is a great job for those looking to learn more about infosec.

This role will be focused on integrating our product, SecureONE, with the APIs of other products. These integrations will make the lives of our customers easier, simplifying their business processes and increasing their security. We are big believers in SecureONE being a good citizen in the enterprise ecosystems of our customers; that means consuming data from other existing systems and providing data from SecureONE to other systems.

About You

  • You love APIs. You love reading API documentation, you love writing APIs and writing code that calls APIs written by others. You can REST with your eyes closed… or open.
  • You think Javascript is tops, and
  • Native-level English skills… the API documentation for the products we want to integrate with is often difficult to parse, and we also want to make sure the API documentation for SecureONE is easy to read and understand

Ideally, candidates will have experience with several of the these technical skills (but no candidate is expected to be savvy in all of them):

  • creating, maintaining and testing RESTful APIs
  • Experience creating integrations using node.js
  • accessing data from no-SQL database like MongoDB

The ideal teammate

  • has a strong desire to pick up new skills and knowledge. We are a small and growing team and we all take on multiple roles. We value “Show me how” over “That’s not my job.”
  • communicates well. We feel updating all team members, local and remote, is key to team success.
  • enjoys building their own tools and sharing those with the team. We believe in investing time to make our workflow more efficient and pleasant.
  • has a passion for building readable and maintainable code. We believe refactoring and writing tests are important to a maintainable codebase.
  • is pragmatic and is able to understand the tradeoffs in the business and technical aspects of every decision. We believe our work should deliver impact and value to our customers.


  • Flexible hours
  • Remote work friendly
  • Unlimited paid vacation policy
  • Free bags of Popcorners (while supplies last)

A day at Remediant:

  • It’s time for the Monday morning team meeting. You dial in via Zoom. After a round of updates, you propose the team should use a code linter. The team agrees and you create a new issue for the work.
  • You start a new git branch for the code linter issue and move it into “in-progress” on your Zenhub board. After a couple hours of work and testing, you are satisfied with the changes and push them up to Github and open a pull-request for review.
  • You spin up a Docker stack to work on a feature that requires a Python and a Node.js service to communicate via a message broker. You hop on a video call with another team member to discuss changes required in the message format. Afterwards you update the documentation and tests to reflect the changes before continuing on the format changes.
  • A fellow team member has requested your feedback on a pull-request. You propose a couple naming changes and well as some additional test cases. After the changes are made, the pull-request is merged and the automated tests start running.
  • Someone on the team has a question on Slack about how to write a particular MongoDB query. You worked on a similar issue last week, so you are able to point them to examples in your code. 👍

The last bit:

  • If you don’t meet all the requirements listed above but think you could be good for the job, apply anyway!
  • Remediant is committed to equal pay