That's a harder question. It gets to programming methodology, best practices, local practices, and finally, how the optimizer works. As a general concept, think of views as a masking mechanism. They hide stuff for security or for complexity. But, never forget that it's just a query. What happens is that people start thinking of views as tables (and they are absolutely not) and then JOIN one view to another or nest a view inside a view inside a view. Then, you're shooting the optimizer in the head and people are frequently surprised at how bad performance gets. So, in answer to your question, it depends.

As to putting SQL or T-SQL on your resume, Gail might flog you for it, but I wouldn't see it as that big a deal if you had both. Although, honestly, you could just put SQL and SQL Server and most people would just infer T-SQL. For the fundamentals, SELECT FROM WHERE UPDATE INSERT DELETE, the differences between T-SQL and ANSI SQL are minimal. I realize we're trying to match our CVs to what search engines return, but I suspect that's impossible. Especially when people post job requirements that mean you have to be a DBA, a SAN Admin, a developer, a hardware expert, SharePoint guru, network architect and sub-atomic physicist with a top secret clearance, 2 years of experience and they're willing to pay $50k. In short, no one meets the requirements because anyone with all that knowledge and skill has a LOT more than 2 years experience and expects to make MUCH more than $50k.

Instead, I'd focus on honesty and clarity on your CV. Let me know what you've done and what you know. Lies and exaggerations will burn you.