Howdy folks! Sloan, DEV Moderator and mascot, coming back at ya with another question submitted by a DEV community member. 🦥
For those unfamiliar with the series, this is another installment of Sloan's Inbox. You all send in your questions, I ask them on your behalf anonymously, and the community leaves comments to offer advice. Whether it's career development, office politics, industry trends, or improving technical skills, we cover all sorts of topics here. If you want to send in a question or talking point to be shared anonymously via Sloan, that'd be great; just scroll down to the bottom of the post for details on how.
Let's see what's on the docket for this week...
Today's question is:
How would you go about preparing to be hired as a newbie dev? Aside from improving my resume and searching around the web for a position that is open to first-career devs, I'm not entirely sure what to do. Does anybody have any guidance or specific steps to suggest?
Share your thoughts and let's help a fellow DEV member out! Remember to keep kind and stay classy. 💚
Want to submit a question for discussion or ask for advice? Visit Sloan's Inbox! You can choose to remain anonymous.
Top comments (4)
0) resumes are mostly useless. Have one but don't count on it.
1) start a portfolio now. It could be a notion page, github repo, website whatever that will later be your portfolio. Companies don't expect you to be productive for a while when they hire you, but they do some kind of resinsurance that you have some level of competency at building simple stuff. The best way to give that reinsurance is to show what you have already done.
2) connect with people in real life (LinkedIn connections doesn't count) that looks like possible colleagues, prepare a list of open questions, invite them for coffee, real café or virtual, and ask for guidance.
I find that networking with people in the field to be a big plus. You can network by attending tech events around you. Posting useful content online and joining online communities.
Do not immediately aim for a full-time job if it's too hard to get one. It's easier to gain experience through part-time commissions. It's better to take a small job and earn $500 in a month than just apply for years to no effect.
I would say to learn (and apply in portfolio projects) some underrated skills that are not difficult for a beginner to learn, Accessibility and Performance for a FrontEnd Dev for example.
Some comments may only be visible to logged-in visitors. Sign in to view all comments.