This tells you that Employease has thought very carefully about granularity, and has exposed services based on whether they deliver complete results that will be useful to customers.
I don’t consider having separate services for “AddFoo” and “ChangeFoo” (where Foo = “CorpGroup”, “JobTitle”, etc..) to be a best practice. What about encapsulation? These two services will necessarily be tied at the hip because they use the same data, so why not make a single service out of them?
BTW, did you notice how their documentation uses links? This might help explain their inability to appreciate how the Web can be used to improve their SOA;
<a href="" onClick="window.open('documentation/AddCorpGroup.html', [...]</a>