If I understood your question correctly, in my opinion that would be a bad design.
Instead you should have employee table having the attributes that are not "time specific". Columns like Id, name and so on.
Then you should have a child table which should contain the Type, Status and whatever may be changed over time. This table should have at least one column defining the moment when the status on the row became valid. This way you only add new rows to the table and these new rows logically invalidate older rows for the specified employee.
Something like
EmployeeStatus
--------------
- EmployeeId int
- Type int
- Status int
- ValidFrom datetime