Releases, changelog and test environments

JobMojito is a cloud service that improves continuously. This article explains how changes reach your account, where to read about them, and how to test your own configuration and integrations before candidates see them.

1. How JobMojito releases changes

• Continuous delivery. Fixes and improvements ship when they're ready, usually several times a week. There are no scheduled maintenance windows. Releases are deployed without downtime.

• Tested before production. The live interview engine and the integrity analysis run in a separate staging environment before every production release. Database and API changes go through automated test suites against a production-like copy of the database.

• Backwards-compatible API. Existing API endpoints, fields and webhook payloads aren't removed or changed in a breaking way. New fields are added alongside. Breaking changes, when unavoidable, are announced in advance through the changelog and by e-mail to technical contacts.

• New features are mostly opt-in. Features that change what candidates experience, or what you're charged for, ship switched off and are enabled per interview, position or account. Examples: SMS/WhatsApp notifications, country restrictions, identity verification, cheating detection. Improvements to the AI models, scoring quality and the user interface apply to all accounts.

2. Changelog and roadmap

You can subscribe to the changelog on the changelog page to get new entries by e-mail. Use it to pick the releases relevant to your process and schedule enablement of the opt-in features with your team.

3. Testing before going live

You test your own configuration (interviews, positions, templates, integrations) on the production platform, kept apart from real candidates. Four tools help.

3.1 Drafts and preview

An interview or position in Draft status can't be found or taken by candidates. Use Preview to go through it yourself as a candidate. Publish only when you're satisfied.

3.2 Environment per interview (for integrations)

Each interview has an Environment: production (default), uat, development or demo. Set it under Interview ▸ Edit ▸ Custom integration ▸ Environment. A result goes only to the webhooks registered for the same environment, so test results reach your test systems and never production. The technical set-up is in Environments and testing.

3.3 Test candidates

Invite yourself or colleagues, or use the API with is_test: true to create a test link that also works on draft interviews. Test results are marked as tests in analytics, and you can delete them like any other candidate. Test interviews use credits like real ones.

3.4 A separate UAT company (recommended for larger rollouts)

For a complete separation, JobMojito can set up a UAT sub-company next to your production company. It has its own users, branding, interviews, API key and webhooks, and none of its data is visible from production. Typical release flow:

1. Build or change the interview, position, templates or integration in the UAT company.

2. Validate it with test candidates and your test systems (ATS sandbox, webhooks).

3. Sign off internally.

4. Copy the configuration to the production company, through the API, the import documents, or with our help, and publish.

Ask your account contact to create a UAT company.

4. Questions and answers

Q: Can we delay a platform release until we've approved it? A: Platform releases apply to all customers at once, so they can't be held back for one account. What you control is when new features are enabled for your interviews, and the content and configuration your candidates see. Both can be validated in UAT first.

Q: Will an update change our existing interviews? A: Your questions, rubrics, templates and settings never change unless you change them. Improvements to the AI models can change the wording of follow-up questions and the scoring explanations. Model changes are benchmarked for quality and consistency before release.

Q: How do we hear about incidents? A: Through status.jobmojito.com, where you can subscribe to updates, and by e-mail from your account contact for incidents that affect your account.

Related: APIs & Webhooks · JobMojito TrustCenter (architecture documents on request)