The level of your technical skills is entirely up to you.
The difference between BA in CS vs. BS in EECS (there is no BS in CS!) is that BA CS is more grounded in mathematics, algorithms, logic etc... BS EECS is more grounded in hardware/engineering. Nonetheless, all have to take courses in algorithms, computer architecture, machine structures, etc... The rest is up to you. You can do a BA with somewhat of a hardware focus, or a BS with a software focus. You can take whatever classes you'd like on top of that.
Otherwise, there's no difference. As for getting a job, getting a good internship matters far more than what your degree and where you went to school. A good school will help you find a good internship. Just for $deity's sake, do something technical over the summer vacations (instead of doing nothing or working at the mall).
For what it's worth, interview questions also tend to be more focused on discrete mathematics and algorithms than they are on systems and hardware, so a BA might actually prepare you better.
Finally, the education is for your own sake, not for the sake of your employer.
(They give you an MA for free later, but that's a weird historical accident; I have a proper Masters' and a PhD as well.)
> I had a BA because every first degree at my alma mater
> BA. I guarantee you it's at least the equal of any
> science course anywhere in the world.
I assume it's a bit different for European universities. In general, the BA/BSc distinction tends to be a meaningful one in the US. > (They give you an MA for free later, but that's a weird
> historical accident; I have a proper Masters' and a PhD
> as well.)
Weird? Try cool. They're seriously considering abolishing that particular quirk, though.