As a Functional consultant the first thing that we should decide before we can design the solution for a customer is whether the system going to be a Single Business Group or Multi Business Group.
The second main important thing we need to decide is whether the customer is going to use Job or position.
When we put this question to the customer the first expected question for the Customer side would be what is the difference between Job and Position
The content in this blog is more of my own view and the simplistic approach I always like. review the documentation before you can decide on the approach you want to take
To explain it in a very high level
Jobs are Generic Title or Role within a Business Group, independent of any single organization. Required. Usually more specific if positions are not used.
Position are Specific occurrence of one job, fixed within an organization. Not required
If you are in US legislation your job will drive you FLSA and EEO reporting. Personally I feel maintaining the Position is hard in an unstructured organization. Position Hierarchy will suite for the University/college/School and Government Organization
The Maintenance is more in the Position hierarchy than in the Job. If your customer feel they need less maintenance activity then you should recommend Job not the Position