I know CRUD is good for RESTful.
Wrong, CRUD is very far from REST; typically separated at least by 2-3 layers of abstraction.
The point is: REST doesn't deal with database records, it handles resource representations.
Now, what's a resource? is it a database record? no, it's not. It's a more extensive, abstract concept. Resources in a system can be User profiles, activities, documents, statistics, etc.
In your example, you have an employee resource, I guess there's also a division resource, which can list the related employees. Maybe also an enterprise resource, which contains divisions. But there could also be a middle managers resource, with employees from all divisions.
Any of these "grouping" resources should have a link to the list of "contained" resources, and also some other attributes, like full name, a longer description, maybe an address, etc. Also there could be links to other "complementary" resources, like a webpage, a document repository, etc. Among those, there could be a "statistics" resource, with all the aggregations you want, either as prespecified fields, or via some specifications in the URI.