It's a basic question, but it reveals how the applicant would start from a zero state and their awareness of the standard pitfalls that can occur, while also measuring their familiarity with current trends and practices. I suppose they would begin by laying out their time, starting from Sprint NEGATIVE ONE for research, so by the time they hit the first Sprint, they'll already be two steps ahead of Development. Being two steps ahead will allow for running adjustment to be made if something is discovered. By Sprint ZERO you'll already have gathered all your research and started wire framing UX work flows for usability testing. Between usability testing sessions, start putting together the UI Style guide. This requires a current understanding of basic UI behaviour. By the time your usability testing is done, you'll have a solid base of reference to back your design decisions. By Sprint ONE you'll have a low fidelity multidevice mockup for the Dev Team to reference. It will be an MVP 1.0. As tempting as it might be to change the first draft, save any revisions for MVP 1.1. Incremental improvements are better than retarding the team to make adjustments. Be sure to have good documentation and a solid CMS methodology to keep the team on track and in communication. Exercise good heuristics with a dash of Pizazz to resonate with the primary user base. There are other things to be said, like influences and advantageous skills in coding, but these vary and aren't always necessary. So long as a UX Designer is able to answer and ask hard questions that find efficiencies in the design, they're golden.