Summary and recommendation
hackajob, the tech talent recruitment marketplace, does not support SCIM provisioning at all. The platform has no native SCIM API, no integration in the Okta Integration Network, and no presence in Microsoft Entra's gallery. This forces IT teams to manually manage user accounts for hiring managers, recruiters, and talent acquisition teams across what is often a fast-changing roster of users in HR departments.
The absence of any automated provisioning creates significant operational overhead. HR teams frequently onboard new recruiters, hiring managers rotate between projects, and contractors come and go—all requiring manual account creation, permission updates, and deprovisioning. Without automated lifecycle management, IT teams risk orphaned accounts when employees leave, especially problematic given hackajob's access to sensitive candidate data and hiring pipeline information.
The strategic alternative
hackajob has no native SCIM. That leaves a workflow gap in offboarding, access reviews, and license cleanup unless your team handles the app another way. Stitchflow builds and maintains the IT workflows your team still runs manually, across every app, including the ones without APIs.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No hackajob integration found in Okta Integration Network. |
| Microsoft Entra ID | Via third-party | ❌ | No hackajob integration found in Microsoft Entra gallery. |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages hackajob accounts manually. Here's what that costs:
The hackajob pricing problem
hackajob gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Custom | Quote-based (240-unlimited qualified candidates/year) |
Pricing structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Custom | Quote-based (240-unlimited qualified candidates/year) |
Key pricing details
What this means in practice
hackajob's recruitment marketplace model creates several provisioning challenges:
No standard user management: The platform operates on a project-based recruitment model rather than traditional user seat management, making automated provisioning architecturally misaligned with the service.
Manual account coordination: IT teams must manually coordinate access for hiring managers and recruiters involved in specific recruitment projects, with no automated sync to your identity provider.
Limited integration ecosystem: No presence in major identity provider galleries (Okta OIN, Entra ID) means custom integration work would be required even for basic SSO functionality.
Additional constraints
Summary of challenges
- hackajob does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What hackajob actually offers for identity
hackajob provides no native identity management capabilities. The platform operates as a tech talent recruitment marketplace without any SSO or user provisioning features.
No SSO Support
hackajob does not offer:
| Feature | Supported? |
|---|---|
| SAML SSO | ❌ No |
| OIDC SSO | ❌ No |
| Password vaulting | ❌ No |
| Identity provider integration | ❌ No |
No IdP Integrations
Neither major identity provider supports hackajob:
| Platform | Integration Status |
|---|---|
| Okta Integration Network | ❌ Not available |
| Microsoft Entra Gallery | ❌ Not available |
| Google Workspace | ❌ Not available |
Manual Account Management Only
All user management in hackajob requires manual processes:
Bottom line: hackajob's focus on recruitment marketplace functionality means zero investment in enterprise identity features. IT teams managing hackajob access must handle everything manually, creating security gaps and administrative overhead as your recruiting team scales.
What IT admins are saying
hackajob's complete lack of identity management features creates significant administrative overhead for IT teams:
- Manual user provisioning required for all employees accessing the recruitment platform
- No automated deprovisioning when employees leave or change roles
- IT teams must maintain separate user databases outside their core identity infrastructure
- Zero integration options with major identity providers like Okta or Entra ID
We have to manually onboard every hiring manager and recruiter into hackajob. There's no way to sync our Active Directory or automate the process.
When someone leaves, we have to remember to deactivate their hackajob account separately. It's just another system we have to track manually.
The recurring theme
hackajob operates as a completely siloed system with no identity management capabilities, forcing IT teams to handle all user lifecycle management manually while maintaining separate credentials outside their centralized identity infrastructure.
The decision
| Your Situation | Recommendation |
|---|---|
| Small recruiting team (<10 users) | Manual management is acceptable for now |
| Growing talent acquisition team (10+ users) | Use Stitchflow: automation prevents admin bottlenecks |
| Enterprise with multiple hiring managers | Use Stitchflow: automation essential for scale |
| Companies with strict offboarding requirements | Use Stitchflow: immediate deprovisioning critical for candidate data security |
| Organizations using hackajob across multiple departments | Use Stitchflow: centralized provisioning prevents access sprawl |
The bottom line
hackajob has no native SCIM. That means one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Close the hackajob workflow gap
hackajob is one gap in a broader workflow. Stitchflow builds and maintains the offboarding, access review, or license workflow across every app in your environment.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No native SCIM provisioning support found
- No Okta OIN integration available
- No Entra ID gallery integration available
- Platform focused on tech talent recruitment marketplace
Documentation not available.
Close the workflow gap in
hackajob
hackajob has no native SCIM. That leaves one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Start with the free gap diagnostic


