If this a first interview, then most likely it will focus on you, specifically your personality, ie 'Can I work with this person?'. The subtext is whether you are a fit for the dept or not.
If you passed the first, the second interview will be more technically focused. Whatever software are involved with the position, you will be asked about them. Today, PC proficiency is a given, so of course they are going to assume you know how to use the keyboard/mouse. So whatever software are in daily usage, you will be assessed on them. Just as they presumed that you know how to start up a PC and login, they will expect you to know how to start those software, open files, manipulate data, etc...etc...As with any task that involves skills, they will start probing to see if you know tips, shortcuts, or even some arcane features that users with about five yrs experience would know.
For example...
When I interview prospective Production candidates for our Engineering Techs group, essentially an in-house promotion, Linux experience is 'highly recommended' as a skill. Whenever a skill is 'highly recommended' it mean required so watch for this. We do not expect the candidate to know Linux but at least we want to know if the candidate is willing to take on unknown knowledge/skill. That is important and something you want to convey -- the willingness to learn new skills. Your current technical skills of whatever software are highly indicative of that drive. Also, do not sweat it if you do not know some tips, shortcuts, or arcane features that just about all software have. I use Excel for yrs but someone out of Excel training would put me to waste.
Be on the alert for a 'BS' question, meaning a question that most likely you do not know the answer and they want to see if you would 'BS' them, so answer all questions honestly and be prepared to put forth that you are not deterred by the unknown, and if in your history you have a situation where you learned a new skill and made changes, bring it up and details matter. In my case, many yrs ago I changed a hardware qualification process from 1.5 shift down to 1.5 hrs, then I convinced the dept to move the new process down to Production and made the Engineering group advisory, and I explained what happened in my interview. The process was eventually obsoleted but at that time, it improved wafer out per shift. So if you have anything similar, bring it. If you made a change, it mean you recognized a need, seen a few flaws, and came up with a solution. Everyone want to see that.
Good luck...