Pick the service like you pick any other service. Word of mouth from people you trust, reviews, research into the service, common sense, money-back guarantee etc. How do pick how to use any service? How do you pick an important SAAS or library or API to use?
If you are so convinced you wouldn't be able to tell if a service is doing a good job, how do you know that this recruiter you went to "butchered" your resume and didn't improve it?
Sorry if I'm coming across as overly combative, I just feel that IT professionals in particular are really bad at acknowledging their inexperience in other domains. I think this is especially true when it comes to writing. Perhaps it has something to do with documentation traditionally being an afterthought in the FLOSS world.
I can tell ugly and bad resumes. When a bunch of sentences on using Microsoft Office have been added to my resume, I can tell it's a bad resume. This doesn't mean I can tell the difference between the 95th percentile and the 98th percentile resume for a particular employer, where the latter will get me in the door and the former won't.
> but it's probably pointless trying to convince you otherwise.
Hey, thanks man!
[1] Say there are two companies and one has a "don't say anything about hobbies" hiring manager and the other has an "always mention hobbies" hiring manager.
I'm not really sure what else to tell you. When you use any service, there is always a chance that the result is shit. As an adult and a consumer you just have to do your best to mitigate the risk.
If you are already getting lots of callbacks and interviews then it's probably already fine. But if you are getting none, then it's time to swallow your pride and accept that you need help from a professional.
> Hey, thanks man!
I didn't mean to insult you, but if your personal experience with recruiters is only negative, nothing I say will change that perception.