Not an ideal design. You are using the DAO for fine-grained, field level operations. DAOs are more stable when they deal more with coarse-grained, domain object level operations. See my example of a PersonDao in this
thread:
https://coderanch.com/t/604205/java/java/Refactoring-Method
Stability in a DAO API is highly desirable since it is an API between your domain/service layers and your persistence mechanism. The more stable you can make the API, the less disruptive changes to the implementations on either side of it will be to the other. If you design the DAO to deal with field-level values, your API and anything that depends on it will have to be changed much more often than if you made it deal with domain objects only. This is the benefit of encapsulation and abstraction.
BTW,
you should settle on one spelling of 'employee' and stick to it. There are a number of instances in your code where you use 'employe'. Ideally, you would choose the correct spelling rather than try to save yourself a keystroke. Attention to these kind of small details is the mark of a good developer.