---

An Unexpected Decision in the Slack Channel

During one of our morning discussions in Slack, one of the developers raised the issue of how candidate privacy affects their experience. We began to consider complaints from users who felt unsafe when their data was publicly accessible. This discussion soon led to the decision to make candidates private by default.

Why This Matters

Data privacy is not just a legal issue; it’s a matter of trust. Candidates who post their resumes on the platform expect their information to be protected. We noticed that many users, especially newcomers, were wary of their information being available without their consent. This created a barrier during the registration process and reduced the overall number of resumes uploaded to the system. We understood that this was not only a problem for candidates but also for recruiters looking for active applicants.

Specific Data Access Issues

One striking example illustrating this issue involved a candidate who, after registering on the platform, found that their data was visible to all recruiters publicly. They contacted support requesting the removal of their profile, which negatively impacted our reputation. We realized that urgent changes were necessary. The lack of privacy not only deterred users but also led to a high churn rate.

Initial Attempts to Solve the Problem

Initially, we considered implementing a two-tiered settings system where candidates could manually select the level of visibility for their data. However, this idea was quickly dismissed as we realized that such settings could confuse users, especially those encountering the platform for the first time. We were looking for a simpler and more intuitive solution.

Technical Approach to the Solution

As a result, we decided to change the privacy settings at the system level so that all candidates would be private by default. This required modifications to the API and user interface to reflect the new logic. Here’s a code snippet we added to handle the new settings:

class Candidate(models.Model):
    is_private = models.BooleanField(default=True)

    def __str__(self):
        return f'Candidate: {self.name}, Privacy: {self.is_private}'

This logic allowed us to easily manage candidate privacy and simplified the process for users, who no longer had to worry about their confidentiality.

Product Changes

After implementing the new settings, we noticed that the number of registered candidates increased by 25% within the first month. This change also positively affected interactions with recruiters, as they could be confident that the candidates they were working with had made an informed choice about their privacy. The new logic was detailed on the /for-candidates page, enhancing transparency and trust in our platform.

What We Learned

• A simple interface is more important than numerous settings.
• Data privacy fosters trust among users.
• Changes based on feedback lead to improved metrics.
• Direct interaction with users helps identify weaknesses in the system.
• Incorrect settings can lead to user loss.

What This Means for Candidates

For candidates, this means that their data is now protected by default. They can be assured that their information will not be accessible without their consent, fostering a more comfortable job search. This also allows them to focus on what truly matters — finding suitable job openings and communicating with recruiters.

What This Means for Recruiters

Recruiters can now be confident that their interactions with candidates occur in a secure environment. They can concentrate on finding and attracting suitable professionals without worrying about candidates' data being publicly accessible. This creates a more professional atmosphere and increases trust in the platform.

Next Steps

We continue to monitor how these changes affect user behavior. We will observe how candidates respond to the new settings and are ready to make adjustments if necessary. If we could change anything in this process, we might have implemented the changes even earlier — user feedback indicated that they had long been ready for greater protection of their data. ---