Here is some advice that works for writing a resume, but can be applied to anything.
1) Put yourself in the shoes of the one reviewing your resume. What does he want do read? What doesn't he want to read? What is he looking for? How does he select candidates based on all the resumes he gets?
2) See how your education and experience can help the company that reviews your resume. Don't think about yourself, think about the value that you can offer, and make it clear.
I once had experience in both Java and C++, about equal. I had 2 resumes, both correct. But on one the Java part was more obvious, and on the other the C++ part. So it depended on what the company was looking for whether I would send the one or the other.
That's a good idea, different resume's tailored to different types of jobs.
And the empathy piece of putting yourself in someone else's shoes. I'm finding it challenging to do that. I know tech leads as friends, but this is the first technical job I'm going after, so what does that person want?
1) Put yourself in the shoes of the one reviewing your resume. What does he want do read? What doesn't he want to read? What is he looking for? How does he select candidates based on all the resumes he gets?
2) See how your education and experience can help the company that reviews your resume. Don't think about yourself, think about the value that you can offer, and make it clear.
I once had experience in both Java and C++, about equal. I had 2 resumes, both correct. But on one the Java part was more obvious, and on the other the C++ part. So it depended on what the company was looking for whether I would send the one or the other.