The table that "commands" there is that of employee, this is something concrete. If the person is an employee, that's where it should be registered.
The decision is only where to put the data that depends on the position that the employee is occupying at that moment.
The simplest solution is to place all the specific columns of all positions in this same employee table, and do not mind that several of them are always null. There will be a column indicating the position held and the application will know which columns are of interest to that position. I do not like this much, but it's more feasible than people usually imagine.
The solution that seems most conceptually correct is to have a set of auxiliary tables, one for each job with only the required specific columns. The employee table will also have a column indicating the position. Performance tends to be slightly smaller, but quite acceptable.
Note that these tables are not the job title (this describes the job itself, generally for everyone), it is one that lists the job data for each employee, so if you have 20 agents working in the company, it will have 20 lines.
So I understand you will keep the current tables by removing only the columns that are common to every employee and these columns will go to the new employee table that will always be related to the charges table.
