Enjoy content similar to this post on Arit, Developer!
Subscribe to Arit's Newsletter to receive quasi-monthly emails whenever she publishes a new story.
I am 10 months into my first professional role as a developer, and it has been one of the most rewarding experiences of my life. Recently, someone asked me: What has contributed most to your success? Bar none, mentoring was crucial to my transition into a tech career. In coding bootcamp, I was assigned to Jeremy, whom I would meet with once a week by video chat for 6 months. I was so overwhelmed and frustrated during the first few lessons, but Jeremy's patient instruction and unwavering support convinced me that I could really do this software development thing!
Since then, I have enjoyed the priviledge of mentoring several aspiring devs at various stages: some just starting coding bootcamp, others ready for the job-hunt. Through these relationships, I have identified certain characteristics that I believe can make a mentoring relationship more useful and rewarding for those involved.
No one person can meet all our mentoring needs. I have gained more from mentoring relationships that I defined specifically, than from those which were more general and nebulous in nature. Spending time to define the particular outcomes I seek from being mentored allows my mentor to be more focused and intentional with what they bring to our relationship. This definition also allows me to enjoy mentoring from several people, without feeling like these relationships are overextended or redundant.
Additionally, in my opinion, it is up to us - the mentees - to communicate when a mentoring relationship has run its course, or is no longer useful. Most mentors want to be kind and sensitive, even if they've sensed that they are no longer contributing much to our growth. We can sidestep that akwardness by graciously thanking them for their input, and sharing our desire to move on beyond them. A mature mentor will welcome this level of honesty, and not see it as a rejection.
Here are some questions to consider as you seek a mentor:
What types of support do you need? Technical (e.g. pair-programming, problem solving) or Process (e.g. study strategies, job-hunt approach)? If you choose several kinds, it may be helpful to quantify them (e.g. 40% technical, 60% process).
How often would you like to meet, and in what way? Weekly phone call? Video chat every 2 weeks? Whatsapp conversations? Only when you have questions?
Is there a time-limit on the mentoring relationship? For example: "Until I land a job" or "For up to 1 year". Personally, I am more comfortable with mentoring relationships that have a defined end-point, as it helps to focus our meetings. Note that ending a mentoring relationship does not mean that mentor is out of your life for good; they certianly remain in your professional network.
I hope these suggestions help you get the most out of your mentoring relationships, both as the mentor and the mentee. Thanks for reading!
Enjoy content similar to this post on Arit, Developer!
Subscribe to Arit's Newsletter to receive quasi-monthly emails whenever she publishes a new story.
Top comments (4)
Thanks for sharing. As I read through your post I felt like this is just the introductions, as now I just have more questions :)
My biggest issue is that I don't know where to look for a mentor. Although I've been working as a professional developer for quite some time now, I felt like I need a mentor for quite a while now. Yet, I have no idea where to look.
The type of mentor I'm looking for is a bit more ambiguous, I think. As I'm trying to get into open source, I feel like this black box is terrible to deal with alone. Some guidance (mostly technical) would be just the Kickstart I'd need.
Yet, I can't stop asking myself who would provide me with such an "experience" we call mentoring,for free?
I always thought that getting into Open Source is just to find right project and start tackling down issues one by one.
"If you use, i.e. RawRabbit, then go read reported issues.
You have no idea how to start? No problem. Talk to others. Tell them that you would like to help. They'll help you!"
That is what I was told.
Yeah, getting into Open Source is hard the first time. Even if you are a experienced Developer.
Wow..love this