Agreed. I'm not sure how 'Source Code Version Control' and 'Build Automation' is anywhere near the words 'Software Engineering'. And 'Automated Testing' isn't a given at a lot of shops.
Professionally, I've never set up version control. It's there when I start the job, it'll be there when I leave. I've branched and merged but a lot of times this is handled by a build manager. Build automation I have never expressly done - a shop that needs continuous integration is typically one where it is already set up.
Seriously, unless the job is 'Build Manager' then the question should be just used to gauge what you might have to teach them. 'Have you used source/version control software? Which ones?' 'Do you have experience with build automation tools?'.
> I'm not sure how 'Source Code Version Control' and 'Build Automation' is anywhere near the words 'Software Engineering'.
I'm not sure how they couldn't be. True, they are not a part of computer science, but both are very helpful to be able to build software efficiently (i.e. software engineering). The places I've worked tend to not have build managers (and the one time there was one, the person wasn't technical and needed 'help' from engineering, to have sane policies and organization). Both skills are also important if you want to launch something -- either a personal project (open source or otherwise), or on a small team at a startup.
Let me get this straight, you do not know how to set up version control, therefore knowing how to set up version control is useless?
What I said:
Professionally, I've never set up version control.
I also never said it was useless. In fact, I use it at work AND at home on my own projects religiously.
However, I don't feel a need to ask about it in an interview. If you haven't used one you will be soon and if you know how to manage one it's just gravy. I might not even ask it's so inconsequential. Continuous integration is the same.
And no matter how you spin it, it's not software engineering. Not in the ballpark, not even the same game.
It wouldn't be useless but it could be unnecessary. I don't anticipate ever needing to set up version control, unless it's my own business. Any place I work will almost certain already have it set up, and if not, someone else will be tasked to set it up.
Meh.