this post was submitted on 28 Oct 2023
93 points (94.3% liked)
Asklemmy
43835 readers
693 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.