In the term "VBA", "A" is the main focus point, meaning Application with VB development environment built-in, which is CLOSELY tied to the application (MS Word, Excel, Outlook, or AutoCAD). One cannot separate VBA from its host application. The minor exception with AutoCAD VBA is that the latest AutoCAD version does not install its VBA by default, one needs to install it separately. But it by no means AutoCAD VBA exists by itself, but because VBA in AutoCAD was going dead and only revived later, but with seviours usability issue due to the fact of lack of support to 64-bit VBA/COM technology.
If you have never done AutoCAD VBA, but have experiece with other VBA (Excel/Word/Outlook/Access), you may be able to quickly pick up your AutoCAD VBA skill, depending on how good your understanding/knowledge to AutoCAD. If you have AutoCAD LISP experince, it would be helpful. Still, it might still be days or weeks away to be able to develop a reasonable VBA program in AutoCAD.
IMO, at this stage of AutoCAD (with VBA has been fading out for quite a while), if a company needs some that can do AutoCAD VBA, it is likely it looks for someone can provide quick solutions, or fix exisitng VBA programs. It is definitely not worth starting to develop new, advanced CAD solution with AutoCAD VBA.
If you are confident that you can pick up the AutoCAD-specific VBA skill, say 3 - 5 days, and have AutoCAD available, you may want to try to find out what the job is expect to do, and come up with some sample code that you can give a short demo (this would be what I'd ask applicant for this kind of job to do).