Title.

I have a lot of skills I use in my hobbies and helping others out, I study tech shit, physical\digital art and other languages, but my current employment is so basic it doesn’t need any of these things. And I have no in-paper proof I know them.

While writing my CV, I feel pretty lost. My position doesn’t say anything at all, and I don’t know how to show I have experience editing photoes, sound and video in Adobe, coding shit in different languages when it’s needed.

Do you have some guides to write a good CV? Or how to write in your occasional works in unrelated fields?

upd: One fucking doctor in my field asked me why I’m still there with all things I did they know about. I didn’t know what to answer.

upd2: Thank you Lemmers, you rock.

  • @stealth_cookies@lemmy.ca
    link
    fedilink
    98 months ago

    Write in accomplishment statements. There are plenty of guides online about how to do that. I straight up have a categorised list of skills at the top of my resume and then below they have an accompanying accomplishment statement that explains how I have used that skill. This gives an easy way for the interviewer to ask you about something you can talk to.

    Attach a portfolio of work when appropriate, visual examples are great to show what you know.

    • I agree with this but really appreciate when people say if they did it with a team and what their role is.

      I see resumes from people a year out “school” saying they did stuff in three months that takes a team of senior devs that long. I’m looking for honest team members. That experience is valuable and it’s ok to be the person who played a supporting role.

      • @stealth_cookies@lemmy.ca
        link
        fedilink
        48 months ago

        Yeah, don’t lie about it, just make it clear what you can do. At least when I interview people I will ask questions about your work experience that will show how well you know your stuff. I also appreciate when they show that they are good team players, both as someone working as a member, and if they are more experienced, both leading others and under others.

        • My technique is an initial conversation, then a soft skills interview, then a technical interview where I get a senior Dev to sit in. Long process but has excellent outcomes.