Skip to main

API Technical Specs

Learn how to configure and leverage our services to achieve your toughest recruiting needs.

Sovren Job Order Parser

The Sovren Job Order Parser was designed for use with AI Matching. All other use cases are allowed, but without support from Sovren. Our Job Order Parser was built to output additional calculated information that can be helpful for matching, but look incomplete to the human eye. Our goal with the Job Parser is to continually improve AI Matching and we have found that other use cases directly conflict with this goal.


Job Orders (aka job descriptions, job postings, etc.) are much more difficult to parse than resumes because resumes contain information about one thing (the candidate). On the other hand, job orders often contain information about:

  • The job
  • The ideal candidate
  • The company
  • Corporate culture
  • Benefits
  • Background checking and testing

When you have control over the content of the Job Order, omit as much of the extra information mentioned above. This reduces the amount of work the parser has to do in determining what informaiton is relevant and will reduce false positives. The Sovren Job Order Parser is designed to ignore all of the unecessary information, but simply omitting this information is always the best way to improve parsing accuracy. If you have control over the format of the job order, follow the guidelines in Constructing A Parseable Job Order for the highest parsing accuracy.

Using the Job Order Parser

To use the Job Order Parser, simply pass in your job order document through our API and the parser will extract multiple data points such as employer name, job location, job description, required skills, required degree, start date, etc. (for a full list of fields, please refer to the Job Order Schema). In addition, the job order parser can also output the original document in a variety of formats including HTML, PDF and RTF.

IMPORTANT: If you are parsing Human Resources jobs, you MUST set Configuration.IncludeRecruitingTerms to true in your api request. This setting tells the parser not to ignore all of the typical noise in a job order because it's relevant to this position. More information can be found in our API documentation.

Job Order Parser Output

To see an example of the output, parse one of your job descriptions in the api. We don't provide a sample output because your settings and the source job can impact the fields returned in the API response. For a full list of fields, please refer to the Job Order Schema.

IMPORTANT: Your integration code should be robustly written to handle the case of missing elements. Most of the elements are optional; they are output only if:

1) The data exists in the parsed document, and
2) The parser is able to recognize the data, and
3) Configuration options have enabled parsing of those elements.