4 ms·
> ResMaps lets you to create a sleek web resume that captures where viewers spend the most time looking. What viewers are looking at is not the same as what hi
by minimaxir 12y ago
> ResMaps lets you to create a sleek web resume that captures where viewers spend the most time looking.
What viewers are looking at is not the same as what hiring managers are looking at, which may make the results misleading in a real-world scenario.
- sanmeetkanhere 12y agoThis is true, but usually you can tell who is visiting based on where you have sent your resume and city, network of the visitor.
- minimaxir 12y agoNot what I meant. Ideally a user would submit their resume to test where hiring managers might looks when they submit their own resume to them via the hiring company's own process. In that case, the test vs. actual behavior will differ.
- erickookoo 12y agoPart of the reason we built this is because applying online nowadays is like a black hole and a lot of times you never know the status of your application. With this, at least you'd be able to know when anyone actually looked at it. Based on how much interest they showed, you could probably make an educated guess as to whether they were interested or not. Basically, at least you get some feedback. I actually applied to a couple of jobs to test it and had some interesting results. For example, in one interview there was much more mouse-hovering/interest focused around my front-end development skills as opposed to UX. Similarly, I could see what projects they clicked on and during the interview, they did ask about those. It is reasonably helpful for interview prep. There were some people that just printed out the resume though, so I wasn't able to get any data with them.
- didgeoridoo 12y agoI'm much more skeptical about the "use mouse movements as a proxy for eye gaze" part. For non-interactive elements like text blocks, cursor location has a NEGATIVE correlation with eye gaze (because users will often move the cursor out of the way of what they're reading). I would completely disregard any data that comes out of this. One way to potentially address this problem: dim out most of the page except a 200-300px diameter circle where the cursor is located. Force the user to use the cursor as a "spotlight" so they can read the resume. This allows you to see where they look & what catches/holds their attention. It's a wholly unnatural way to read, but should serve your particular purpose.
- erickookoo 12y agoYou're correct about users not hovering over exactly where they are reading in order not to block their view with the cursor, but studies have shown that people do position their cursor very close to or just below where they are actually reading (there are, however, also other usage patterns such as the scroller who simply leaves his cursor in one place and scrolls down the page). We've allowed users to create links to their projects in order to make would normally be non-interactive text blocks on a resume into something clickable. There is plenty of literature that correlates eye gaze to cursor movement (e.g. http://scholar.google.com/citations?view_op=view_citation&hl=en&user=o8oJ6s4AAAAJ&citation_for_view=o8oJ6s4AAAAJ:HoB7MX3m0LUC http://scholar.google.com/citations?view_op=view_citation&hl...)
- mjhouse 12y agoSomething I thought of coming home from a birthday dinner this afternoon: In order to get a better idea of what the viewer is focusing on, you might consider going to a vertical gradient instead of a pointer heat-map. Most people don't read to the bottom of the page before they start scrolling. Imagine two lines on the screen- the bottom line is the point at which the viewer will begin to scroll. The top line is the point that the viewer wants their reading area to be located. The space in between the lines is your "target" area. As the viewer scrolls down the page, you could average their scrolling speed, and increment the intensity for that area of the heat map only when they slow their scrolling speed drastically, or go back over an area. Just from paying attention to my own scrolling habits, I think the top line would probably be just above the horizontal center of the screen, and the bottom line would probably be about an inch down. You could do some testing to find the average line positions.