Background: I'm involved in hiring graduate and intern computer scientists and software engineers in a mid-size organization in the US. Our HR dept do the first pass on resumes before forwarding applications to us. The HR filter is for obviously inappropriate applications, too many spelling and grammar errors, the obviously unqualified, time-wasters and morons (you might be surprised how many this disqualifies). I might then get to filter the remainder for a given position we might have open. In practice, this means I have an hour or so to review maybe 30 - 40 applications.
I'll do a first pass of each resume spending no more than 5-10 seconds on each. I need clear and immediate answers to two questions: What can you do (qualifications and skills) and what have you done (experience). The answers need to be brief and targeted to the open position. Qualifications are only valued in a minimum barrier to entry sense. Lists of skills even less so (e.g. everyone puts "Javascript" under skills, very few are truly skilled with it). Experience is given much more weight, and it certainly doesn't have to be professional, just relevant - paid employment, college projects, open source contributions, even personal projects all count (a link to a personal github repo is a definite plus). Those applicants passing that filter are no more than a handful, but will have our attention.
So, to answer your question, fancy resume formatting is a waste of everyone's time. Use a conventional layout, conventional fonts, conventional headings. This is a case where boring and conventional is good and trying to be 'cute' and 'different' can cost you. The faster grumpy and impatient people like me find out what we want to know the more a good first impression is made.
Obviously, different organizations have different cultures and processes, but for graduate recruitment from a large application pool in larger STEM-oriented organizations, the above will do you no harm.