You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/why.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Publishing a job on **multiple portals** often means to *copy/paste* data and **
28
28
29
29
It is **not obvious to find the criteria** to decide on which portal they have the best chances to find a candidate.
30
30
31
-
We think, this is rediculous unneccessary: As an employer we want to publish the job on**one location** and **spread** the info.
31
+
We find this unnecessary and impractical: as employers, we want to advertise the position in**one place** and **distribute** the information.
32
32
33
33
We think, our solution might be the missing piece to make it work.
34
34
@@ -40,4 +40,4 @@ While there has been some attempts to address this using a job posting schema fo
40
40
41
41
We propose a much simpler approach, **inspired by conventions** like robots.txt or sitemap.xml. Companies would place all their job listings in a structured file at a single, well-known URL.
42
42
43
-
Job search engines and aggregators would only need to check this one location to get all the data they need. This would make discovering and indexing job postings vastly more efficient for everyone.
43
+
Job search engines and aggregators would only need to check this one location to get all the data they need. This would make discovering and indexing job postings vastly more efficient for everyone.
0 commit comments