Skip to content
The Chat Archive
Human-written demonstration (OpenAssistant volunteers)· OpenAssistant (human-written) OpenAssistant Conversations (oasst2)

how to write a good resume

In OpenAssistant data, “assistant” turns were written by human volunteers as demonstrations. They are not model outputs.
  1. User

    how to write a good resume

  2. Assistant

    Writing a good resume is an essential step in landing an ideal job. There are some tips:

    1. Study the target company: It is always good to study the company you are applying for. Check their products, their slogan, company history and recent news. You can identify which parts of your skills the company might be intersted in and expand it in your resume.

    2. Tailor your resume: carefully read the job description and highlight the skills, experiences, and qualifications the employer is looking for. Then, tailor your resume to match those requirements by emphasizing your relevant skills and experiences. Highlight your relevant experience: highlighting accomplishments and skills that are relevant to the job you are applying for.

    3. Use a clear and easy-to-read format: Choose a clean and simple format for your resume, with easy-to-read fonts and clear headings. Use bullet points and short, concise sentences to make your resume easy to skim.

    4. Quantify your achievements: Use numbers, percentages, or other metrics to quantify your accomplishments whenever possible. This can help to demonstrate the impact you had in previous roles and make your resume stand out.

    5. Include education and certifications: If you have relevant education or certifications, be sure to include them on your resume. This can help to demonstrate your qualifications and expertise in the field.

    6. Use keywords: Use relevant keywords throughout your resume, especially in your skills and experience sections. For example, C++, ERP, CRM, Visio may help your resume passing HR's screening.

    7. Proofread your resume: Before submitting your resume, be sure to proofread it carefully for errors and typos. You may also want to ask a friend or mentor to review it for feedback.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.