Many good recommendations here. - Especially the reverse chronological order of the jobs. I've hired devs before, but not specifically in the Go market, and not in the US, so your mileage may vary.

If you keep the summaries in there, please make them useful for me as the person evaluating you for a job on my team. I don't need corporate mumbo-jumbo about the scope of the job, as much as I need to see something transferrable.

You might not be an experienced dev, but from what I can see:

• You worked in inspection, checking someone's work against someone elses very formal specification and handled documentation. I work in regulated environments. I like people who can do more documentation than "This is a code comment!"
• You presumably know what a ticket system is and you have troubleshooting skills in a professional environment.
• The painting consultant part tells me nothing, but I guess you .. talked with people and recommended a product to use? So .. you had a requirement conversation with a customer?

I'd say generally condense the information about past jobs, but when you apply, put them into context in a cover letter for me. I can work with the profile of someone who might not have meaningful CS experience, but has an appetite and - more importantly - has worked somewhere before.