Possible sections and their uses.

• Requirements

  Core experience & qualities a candidate should have.

  
  

• Additional

  Optional Nice-To-Have qualities a candidate might have.

  
  

• Technologies

  Names of languages, libraries, frameworks, etc.
  used in the products the candidate will work with.

  
  

• Services

  Names of services the development team uses.

  
  

• Scope

  Description of what / how many projects the
  candidate will be working with, i.e. 8 websites.

  
  

• Salary

  Set amount, range or offer of negotiation.

  
  

• Benefits

  Additional pros the offer gives and aren't a given.

  
  

• Tasks

  Description of the daily activities the job includes.

  
  

• Company

  Description of who the company is and what they do.

  
  

In what order to arrange sections.

• The most important part of a good developer
  facing offer is to place the Requirements first.

  If you are unqualified there is no point
  in continue reading the offer after all.

  
  

  Requirements  ›  Additional  ›  Technologies  ›  Services  ›  Scope

  
  

• Place the Salary & Benefits next so the developer can
  evaluate if they consider the off being worth their time.

  
  

• Next describe the Tasks, they are usually a given not very
  important as the developer already has a picture of the
  situation from the previously placed technical sections.

  
  

• At the very end place information about the Company,
  while you may intent to present it to candidates, there
  usually is no need for it.

  Either a candidate knows the company and is
  taking the offer deliberately or they choose a
  company based on the presented job.

  Thus placing company related information
  first is either redundant or just in the way.