// Mentorship Career

Things to know as a new dev

10 min read · Mentorship
Summary 10 min read

Career changers entering tech keep asking the same questions, so we crowdsourced answers from developers across Slack and Twitter: what interviewers look for, how to stay sharp during a months-long job hunt, how to stand out, where to network, whether to apply for stretch roles, and where to start with open source.

I love meeting new devs who are making the transition from a different career into tech. I am mostly excited to see all these minds coming together to give tech a perspective that is rooted in real world experiences that most CS grads don’t go through. Many of them ask me a bunch of questions about what they need to do to make it in the field, and although I enjoy talking to each person individually and giving them my perspective in a personalized matter, I think it’s beneficial to share some of the common questions and answers with a wider community.

Not only that, I shared the list of questions in a bunch of Slack channels and on twitter and collected a few responses from other devs in the field. I think the responses are a great collection of diverse wisdom and I’m excited to share it with you here.

Here are the questions and a summary of the answers:

1. What are the most important skills a new developer should have going into an interview or new job at any company?

As a new developer, the technical expectations aren’t high. If you’ve gone through a 12 week intensive program, there is no way you’ve picked all of the technical knowledge you require to do the job and have become an expert in them. Which is why the things good interviewers will be looking for tend to be the following: critical thinking, communication (writing, speaking), organization, ability to do hard work, humility, strong interpersonal skills, ability to learn/adapt and apply new knowledge, and attention to detail.

Many would argue, myself included, that those skills are not only important for new developers trying to get their first job, but for any person doing any job, regardless of their experience level.

Honorable mentions: having side projects and a public profile help. The ability to explain solutions you’ve implemented or talking through a problem during an interview can give the interviewer some insight into your way of thinking and how you would deal with a situation that might arise at the job.

2. How do I keep “fresh” on material while I job hunt?

This question got some interesting answers, and I believe that the intention behind it might have been misunderstood because of the word “fresh”, which is why I surrounded it by quotation marks here, even though it wasn’t in the original survey.

The original intent of the person who asked this question was not to ask how to learn the “freshest” new framework or language or tool, but actually how to keep the things that were learned during the program without risking losing that knowledge while job hunting. The truth of the matter is that it will take many months for a code school graduate to find a job. Some have gone 6 to 9 months before they were able to land their first job. Many have had to wait longer. Some end up taking jobs in tech but that are not programming jobs. Any knowledge acquired that is not put to practice is at risk of being lost.

Then, to rephrase the question, what are things that can be done to continue practicing the things that were learned in the program, in order to avoid the risk of losing that knowledge?

To that effect, the relevant answers were along the lines of: establish a habit or a routine to do coding exercises on a regular basis. Use sites like www.codewars.com or http://exercism.io to practice. Find a group and meet with them on a regular basis to help each other out, just like a study group in school/college. Join your local meetups, most will probably have a Slack channel that you can join and ask questions on. Subscribe to blogs/screencasts/podcasts or hacker news/reddit (if you have a list of good resources, please share in the comments, I recommend https://www.rubytapas.com). Participate in hackathons, don’t be intimidated to join a random hackathon group to work on a small project, you can look for your local or nearest Hack4Change group and volunteer over a weekend to work an idea for civic change. And I kept this for last because it will shock you how simple yet important this answer is: read a book! Most, if not all technical books have code examples that you can follow along with. Set a schedule for yourself as if you were at an actual 9–5 job, and follow along a book and do the code part yourself. That’s how I personally learned Rails, by following through the Agile Web Development with Rails from PragProg.

Caveat: Don’t try to do everything at once. When it comes to learning, focus is important. Be very disciplined with your learning and don’t try to do too much. Or else you’ll end up doing a lot but not learning much.

3. How do I stand out from the others in an interview or when looking for freelance work?

This one is tough and the answers were very interesting and diverse. Which is why I will copy most answers as is, because unlike the previous questions, there wasn’t one overarching theme to the answers.

  • Build a portfolio of stuff you’ve worked on. Be active in your community (i.e. Contribute to open source if possible, blog, attend and speak at local meetups in your area).
  • Standing out is easy. Standing out in a positive way may prove to be a little harder. Find some unique selling point about yourself that you honestly believe makes you a better choice than other candidates.
  • Realize that you don’t [know] anything, but are eager to learn
  • Knowledge of the company and interest in what they do
  • Specialize in one thing and be familiar with lots of things
  • Be aggressive. A — type personality
  • Show the projects you’ve worked on, talk about your journey to becoming a dev
  • As a small business owner, the people who stand out in interviews are the ones who did other stuff around the interview, they followed up, they asked good questions, they were curious about the work place and our clients. When looking for freelancers, I want some self sufficient, with a go-getter attitude, they’re being depending on to do the job and do it sell.
  • Take the time to craft your cover letter, or the Goal section of your resume, specifically to target each opportunity you interview for. Demonstrate genuine interest in what that company does, or at least something about its industry. It always helps to be able to say in the interview, “I’m really happy to be able to talk to your company specifically because ____”
  • Honestly, I don’t understand how people judge these things.

My 2 cents: Stand out as a person, each one of us is unique, our journey is unique. Share parts of that story if you are comfortable, show the person you’re talking to that they’d want to work with you. Everything else, the technical part, will take care of itself in due time. Especially those of you who are making a transition from a different career path, you’ve got skills and knowledge that will make you stand out, don’t underestimate their relevance. For example, if you are a baker, you understand following precise instructions, and that’s what programming is. We are all walking around with a bag of tricks, figure out which ones are relevant and make them work for your advantage.

4. What is the best way and places to network?

The answer was unanimous: meetups. “80% of success is just showing up” is a quote from one of the answers, which reminded me of something one of the local meetups’ organizers said once:

If you show up to a meetup once, you’re part of the top 80 percentile of the community. If you show up on a regular basis, you’re part of the top 99 percentile.

One thing worth mentioning that was brought up in a couple of the answers is to network in diverse communities, not just tech related ones. You never know who may connect you with the person that will eventually hire you, could be on a hike, at a mountain climbing event, or at a soap making workshop. The key is to put yourself out there and meet as many people as possible.

Austin Bonus: If you are in the Austin area, a few tech related meetups to check out are: Austin on Rails, AustinRB, Refresh Austin, Women Who Code, Girl Develop It, and Cafe Bedouins (although not as active anymore, really all you need is to broadcast to the group that you’d be working out of a cafe at a particular date and time, and people will join you).

5. Should I apply for a job that is above my skill level, or has requirements in programming languages/frameworks that I do not know?

I remember in 2008 seeing job posting that included the following line: “10+ years of experience with Ruby on Rails”. Rails came out in 2005, so not even DHH had 10 years of experience at that time.

This kind of stuff still happens all of the time. So YES, do apply to jobs that might have requirements you don’t meet. But be reasonable. Don’t reach for things you know you can’t do, or learn how to do. If they ask for experience in Angular, but you’ve only done React, you do have the skills needed to make the transition. But if you’ve only worked with JS and the job is asking for a Sr. C developer, that would be a stretch. Challenge yourself, but also make an educated guess. Know the situation, and don’t put yourself in a position to embarrass yourself, but also don’t be afraid to push yourself. As they say: Don’t dress for the job you have, dress for the job you want to have.

6. What are the best sites for open source projects at any level?

I knew that for this question there was going to be one person with THE best written and formulated answer, and the web didn’t disappoint. Which is why I’ll copy it verbatim here:

http://www.firsttimersonly.com is a good place to get started. Another approach is to find a project that you find interesting and write documentation for things that weren’t clear for you in trying to use it, write examples using the project, and write tests for areas that aren’t covered. Then, start with small issues, like logging or error message improvements, before moving on to bigger bug fixes or features. Upgrading minor library dependencies is also a good place to start.

That said, I was waiting for a response from a particular someone. This person has given talks about this issue, and even created a platform to help people contribute to OSS. The person I’m talking about is non other than Richard Schneeman who is behind https://www.codetriage.com. Hey Schneems, got anything you’d like to add to this answer?

I hope this helps anyone who is just starting in tech. One more thing I would add: reach out to someone you admire in the community and ask them if they would be your mentor. If they say no, ask someone else. I guarantee you that you’d get a yes within the first 3 people you ask.

If you’ve got questions you’d like to add, don’t hesitate to post in the comments.

If you’ve got more suggestions to the answers above, please do share!

Bear & Giraffe Advisory

We partner with founders and tech leads to build sustainable Rails architecture, untangle monoliths, and scale pragmatic systems.

Schedule a Strategy Call
ESC

Type to search 38 posts