What should a UX designer know about CSS (for a job interview)?

There is not the requirement on my team to actually use CSS/HTML at all. We just make PowerPoint storyboards to explain the details of the feature we want to add to the application. HOWEVER, I find that the designers who DO know CSS have a better grasp of how the application will be built. It is a degree of technical knowledge that makes one a better designer. It's not that they need to do CSS. It's more of a background thing. If they know CSS, they understand the browser and the web better.

If you haven't got any HTML / CSS skills definitely be honest. If it's something you'd like to learn make sure you state that. Back this up with a little bit of research. found a local / online course to get you up to speed http://www.uxbootcamp.org/debriefing-prototyping-in-code-bootcamp-july-2011/ Maybe you've watched some of the videos on http://membership.thinkvitamin.com/library/html-css and show you're proactive about improving your skills in this area, if this is the job you want. It's great to be able to test out your ideas and designs in prototypes with representative users. You might need some help from a developers at first, but you can start off simple using image maps to make click throughs of your sketches / wireframes and then gradually add things like drop downs, radio buttons, and other more advanced Jquery type interactions as you learn. It's nice to be able to try these things out yourself without having to be reliant on developer resources being available. You want to remove as many barriers as you can to getting ideas in front of people so that you can get feedback as quickly as possible.

I'm a web programmer, and I can tell you that it is extremely frustrating when I had to work on a web project with a graphic/UX designer who knows nothing about HTML/CSS. The reason is twofold, designers who don't know about HTML/CSS usually fail in two points: make designs that doesn't conform to best practices since they don't know the full capability of HTML/CSS and thought a modern, best practice design will be too difficult to implement. make designs that is gorgeous but nearly impossible to implement without a lot of custom Javascript, again, since they don't know that HTML/CSS aren't able to do everything as easily. Things that are easy to do in a mockuping tool can be difficult to do in HTML/CSS, while other things that are impossible in mockuping tool is trivial in HTML/CSS. One example is adaptive layout. Given proper considerations to the initial design, it is possible to create a layout that will adapt to the user's browser (i.e. screen size, mouse or touch screen, aural/braille device, etc); this sort of thing is impossible to express in a mockup and designer who knows nea about HTML/CSS usually create a static layout doesn't fully exploit the capabilities offered by HTML/CSS; or they design too much interactions that would require a lot of custom Javascript work and causes a time/cost overrun. While I do not expect a designer to be able to churn out HTML or CSS codes, I would expect them to design a web application with web technologies in mind. I would expect them to know what is possible/easy and what is impossible/hard to do in CSS. Given these sort of expectation, I don't think it is possible to learn about these without ever getting your hands dirty with writing HTML/CSS from scratch.

This brings up a problem with the title 'UX Designer'. By adding designer into the title rather than, say, UX Architect, there is an expectation by many, that a person can implement final interfaces. That is what they want in this case. Previously UX fell under Usability and Information Architecture titles and there where designers and coders. Now I see UX roles that are NOT UX but are effectively Interaction Design roles - that is Visual Design + Front End Coding + UI + Some knowledge of basic UX. In short, in this case, they want a coder and designer who also has a mastery of UX. This is becoming increasingly typical but people who can do all three well are very very rare. The term UX Unicorns has been invented for these mythical creatures. Those who think they are unicorns are often talented web designers who know a few bits about UX, so not real unicorns and also limited to only the Web (UX is about much more than Websites). In my view it means that more projects will get delivered faster but with a much worse User Experience as, if you code, you will be limited by what is easiest to implement. For my views on this see my article on the http://uxstew.tumblr.com/post/59762423961/ux-and-the-engineering-mindset-evidence-based-design

I am not sure what questions might be asked, how big knowledge should UX guy have. What I can share is what I, as a web developer, think is important about CSS. Definitely the most important thing is good understanding of block elements (like divs, p, table) vs inline elements (like a, span). You should know how to build layout on divs, without tables (by using float property). You should know, when float blocks element does not take any space (for example, if in DIV1 you have only float elements, and DIV1 does not have specified overflow: hidden, then it will not reserve any space). You should know which statements works in which browsers (or more precise: which statements does not work in Internet Explorer X ;-) ). This is tricky and needs experience, so probably you will find out in practice, while spending X amount of hours trying to figure out why IE displays web site differently. If you want to know something interesting about efficiency, then you should know that CSS is parsing expression from RIGHT to LEFT. It means, that if you write #divId a{ ... } then what will happen is that for EACH link on the site a comparison will be made, whether one of its parrent is #divId. Hence it is inefficient way of writing CSS, even tohugh the intuition says, that it should be. You should be aware of following CSS expressions (and be aware that 1 and 2 are the most efficient) find element by id - #divId{...} find element by class - .classId{...} you can join conditions, for example find element that has BOTH class1 and class2: .class1.class2{ ... } you can take several elements at once by separating them with coma: class1, class2 { ... } you can take all elements of given type: div { ... } you can take certain element (for example P) only if his brother is other element (for example H2): H2 + P { ... } (this will match < h2 >< p >... but will not match <h2> <any other element than p > <p> you can take element that has certain attribute: a[href]{ ... } you can specify what should be value of attribute: input[type=text]{ ... } you can use pseudo classes, for example: a:hover{ ... } this obviously does not cover the whole topic, but gives you impression what you might want to google if you feel that you need to I hope you will gain (even a little) benefit out of this answer, otherwise please just ignore it : )

I've an interview on Friday for the role of a UX designer. The job description says 'require HTML & CSS skills'. While I know the basics of HTML& CSS, I have not done coding. Can you share some of the potential interview questions? If you're not very familiar with the coding and want a refresh, checking out w3schools css tutorial doesn't hurt: http://www.w3schools.com/css/ Like the post above me says, It's good to know how a page is layed out in HTML with divs and styled with CSS. I'd also recommend going over some JQuery, as it adds a lot of the magic to the UI of a site. It may be a good idea to know the new trends with HTML5 and CSS3. Check out this site: http://webdesignledger.com/tips/html5-css3-take-your-design-to-another-level for a quick crash course on what's new! A lot of job postings require HTML and CSS skills so that you can speak the same language with front end developers and know the limitations of implementing a design, how long it would take, whats most feasible, etc. Browser compatibility may be important, in general, not just about html and css skills. I'd recommend googling what features browsers don't support. Also, typically how much coding does the role of a UX designer require? It depends on the role, sometimes there's no coding at all, sometimes you might want/need to show actual mockups / prototypes in a browser, sometimes you might design and code! PS: I see that some questions related to CSS have been closed. Can you please guide me to the right forum to post the question if this is not the right one. http://stackoverflow.com/questions/tagged/css there's a link to stack overflow tagged with CSS questions asked, it may help to go over them quickly? Good luck in your interview Tara!