Careers
Work on Certifyi
We build software that compliance teams and their auditors rely on. We look for people who care about getting the detail right and want to understand the work our customers do.
Why here
Many organisations still run compliance and risk work in spreadsheets, email threads and tools that do not connect. Our customers need the software to be right, because auditors look at what it records. The domain is deep, and there is a lot of it to learn.
How we work
Every change to our code passes a multi-stage review that includes security before it reaches a customer. Auditors rely on what our software records, so we check our work before it ships.
We work in small teams with clear ownership. Each team owns its modules from design through to testing, documentation and running them in production. There is no separate QA team to catch what engineering missed.
What we look for
Technical skill is expected. Beyond that, we look for interest in the compliance domain and in the people who use what we build.
- You understand that a compliance officer relying on your software for an audit sets a high bar
- You would rather own a problem than be handed tasks
- You write code that other people can read, change and trust
- You think about the person who will use a feature, not only the requirement that describes it
- You ask questions early instead of building the wrong thing
Open positions
We do not list roles on this page. If you think you could contribute, get in touch and tell us what you would like to work on. We are glad to hear from good people even when we have no role open.
Teams at Certifyi
Small teams, each owning its part of the product.
-
Engineering
Build and maintain the platform modules. Each team owns its modules from database schema to interface to customer documentation.
-
Product
Decide what gets built and why. Work with customers and compliance specialists to choose the problems worth solving.
-
Customer success
Help organisations set up their workspace and prepare for their audits, drawing on GRC knowledge as well as knowledge of the product.
-
Security and compliance
Look after the security of our own platform and keep every security finding in a register until it is fixed.
How we work together
Principles that shape how we build, ship and support the platform.
-
Check before shipping
Every change passes a multi-stage review before it reaches a customer. Fixing a mistake after release costs more than catching it before.
-
Own the outcome
Teams own their modules. If a customer reports a problem, the team that built the feature fixes it.
-
Say what is true today
Our security page says where our own programme stands, including what we do not have yet.
-
Build for the person
A compliance officer running an ISO 27001 audit needs different things from a CISO reviewing risk. We build for the actual person using the screen.
-
Respect the domain
GRC is detailed and regulated. The people who use our platform know it well, and the software should not oversimplify their work.
Questions
Working at Certifyi
What does the hiring process look like?
Usually a first conversation with the hiring team, an exercise related to the role, and a final conversation with the team you would join. We aim to finish within two to three weeks.
Is the company remote-friendly?
Yes. We hire across time zones and work remotely by default. Some roles may have a location preference so that working hours overlap.
How are changes reviewed?
Every change to our code passes a multi-stage review that includes security. The review checks quality, security and completeness as well as whether the code works.
How are teams structured?
Small teams, each owning specific modules. Testing, documentation and support for a module are the module team’s job, not a separate department’s.
I do not see a role that fits. Should I still reach out?
Yes. Send a note through the contact page saying what you would work on and why.
Interested in working with us?
If you want to build software that compliance teams rely on, we would like to hear from you.