If the resume has a good content, the only rule IMHO is it needs to be easy to read. It doesn't matter if you use LaTeX, Rustdoc, MS Word, Libre Office, HTML or

If the resume has a good content, the only rule IMHO is it needs to be easy to read. It doesn't matter if you use LaTeX, Rustdoc, MS Word, Libre Office, HTML or markdown as long as I can quickly get all the information I want. When I dealt with hiring for my team, I've never paid any attention to the formatting. Making formatting stand out from other resumes did not increase the chances for the resume to be picked and moved to the next stage. It did decrease them though, if crazy formatting made it harder to read. Using Rustdoc might be "clever", but I don't find this resume very readable honestly. It took me some time to figure out what modules or structs mean in this context. Don't do this. Recruiters have really little time and they often get hundreds of resumes. If they can't get the essential information quickly enough, they'll just throw it out. What makes an outstanding resume is in the content and how well it matches the job requirements. If I'm looking for a database engine expert and I get 999 resumes which all mention building websites in JS or machine learning models in Python, but one mentions experience on Linux kernel performance work (proven by accepted patches), which one do you think I'd choose?