That's very helpful! Have you read the Fundamentals link I provide in my signature? It will give you the basic understanding of how the table structure should be developed and it's something that every MVP will have expected you to have read before starting this project.
By articulating what you want, you have already begun the design process. You have Employees, Evaluations, Training, Training that Employees have taken, perhaps you also need Training that employees NEED to take...this information will help you decide what TABLES you need (these are technically called entities). Now you need to identify the data that you want to store about these entities, these are the attributes. For Employees, you may want to have such information as FirstName, LastName, Address, StartDate, TerminationDate, Position. These will become the fields in the table.
After you complete the remaining steps outlined in the Fundamentals document and believe that your table structure is in 3NF, come back and show us what you came up with and examples of the types of data you are planning on storing and we'll critique and help you improve upon it until it works for you.
HTH
Leslie
Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual
Essential reading for anyone working with databases:
The Fundamentals of Relational Database Design
Understanding SQL Joi