Back to journal

An application can outlive a public listing

On October 8, I worked on a visibility problem in sezonier.ro. An existing application could disappear from the candidate's own view when the associated job became private or inactive. That could also prevent the candidate from reaching interview confirmation. The public listing and the person's ongoing application were following the same visibility rule, even though they served different purposes and different audiences.

A public job page helps someone decide whether to apply. An application history helps someone follow a process they have already entered. Removing a listing from public discovery should not automatically erase every eligible trace of that process for the person involved. At the same time, keeping an application visible to its owner should not turn into a general permission to inspect private jobs. The correction needed to preserve both sides of that distinction.

I changed the application-reading path to return an authenticated candidate's own eligible records with the job and company details needed for that view. Browser and mobile lists used that same projection. Public job visibility rules stayed unchanged, and deleted or flagged records remained excluded. This kept the change tied to ownership and the existing application relationship, rather than loosening the public listing rules to make a single screen work again.

The change was merged on October 8 as part of a release candidate with completed local validation. The focused database checks exercised actual caller roles and visibility rules, while the broader checks covered the application and its runtime builds. The record also identifies an environment limitation in replaying the full migration chain. These results support the implementation and its tested boundaries; they do not prove that a candidate completed a real interview confirmation or that the full live journey was observed.

Reflection

The useful design question was who still needed the information after public discovery ended. On sezonier.ro, a candidate's own application had a continuing purpose. Treating that relationship explicitly made it possible to restore continuity without making the underlying job public again.