<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dan Telljohann on Medium]]></title>
        <description><![CDATA[Stories by Dan Telljohann on Medium]]></description>
        <link>https://medium.com/@dan.telljohann?source=rss-8cc912d65b34------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KbMS0Ad4wBf5qkGqge0LHA.png</url>
            <title>Stories by Dan Telljohann on Medium</title>
            <link>https://medium.com/@dan.telljohann?source=rss-8cc912d65b34------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:56:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dan.telljohann/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Inception of an Engineering Mentorship Program]]></title>
            <link>https://medium.com/vouch-engineering/the-inception-of-an-engineering-mentorship-program-10522a621566?source=rss-8cc912d65b34------2</link>
            <guid isPermaLink="false">https://medium.com/p/10522a621566</guid>
            <dc:creator><![CDATA[Dan Telljohann]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 20:33:58 GMT</pubDate>
            <atom:updated>2022-12-08T20:33:58.723Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Dan Telljohann </strong>| Engineering Manager, Platform</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YGItVC3PPXha_GFUFHiRcQ.png" /><figcaption>Vouch Team Members</figcaption></figure><p>A question I commonly get asked by Software Engineers is “How did you get to your current position?”</p><p>Today, I am an engineering manager, but I started my career at IBM as an entry level engineer. After working there for four years, I decided to make a change and try out a startup. I joined Root Insurance as a mid level engineer and learned as much as possible at a fast paced company. Along with engineering, my passion is people, so becoming an engineering manager was always the goal for me. I wanted the opportunity to lead a team and mentor people, which are both things a good engineering manager does for their team. Fortunately, Root provided me with that opportunity, and I was an engineering manager there for a couple years before moving to the same role at Vouch, where I am today.</p><p>Back to the original question. “How did you get to your current position?” There are many factors that helped get me to where I am today. Family. School. Great teachers. Interesting projects. Personal learning. But the one thing that stands out above them all is the mentors I have had in my career. Whether helping me learn a new technology, how to manage my career, or just be someone to bounce ideas off of, my mentors are the main reason I am where I am today.</p><p>When I got to Vouch in June of 2022 I was excited to find areas where I could make an impact, both in my engineering work, but also in terms of team development. At my previous job my mentor had taken on the task of starting an Engineering Mentorship Program. This program had a positive impact because it connected me with a talented mentor that helped me transition to management and grow in my career. I was excited to take what I learned at my previous company and spin up a similar mentorship program at Vouch.</p><p>There were a number of important steps to getting this program off the ground. First, I needed to solicit help. Everyone is busy, so finding a fellow manager to bounce ideas off was key. Second, I needed to convince the CTO. This was the easy part. I explained my history with mentorship programs and what I was looking to create. I got the green light and was off to the races.</p><p>Next up, I reached out to my previous mentor to ask him for any resources, tips or advice he’d be willing to share to help get my program going. Lucky for me, he had given a presentation at a conference on this exact topic and after watching his presentation, I was able to get started on my own program overview for the Vouch team.</p><p>Working with some teammates at Vouch, we started by laying out the program goals:</p><ul><li>Promote career growth amongst mentees</li><li>Provide mentees with a less formal space to learn and ask questions</li><li>Provide mentors an opportunity to improve communication and mentoring skills</li><li>Increase cross-team relationships and collaboration across Vouch’s engineering teams</li></ul><p>Each of these goals represented an idea I had heard or observed from the engineers across our organization.</p><p>When we spoke with our CTO, one key aspect we agreed on was that relationships should be driven by the mentee. This would mean setting the expectation that mentees would organize the meetings with their mentors, set agendas, and focus the relationship around their goals.</p><p>To help make the program feel less formal, we wanted it to have very few rules or boundaries. For example, people would be free to come and go in and out of the program as they like. A mentor/mentee relationship might take place over a couple of lunches or meetings, or it might last several months or longer. The goal is that both the mentor and the mentee always feel the relationship is providing value.</p><p>With the overview set, we had to decide what information we needed to effectively match up mentors and mentees. To do this, we created a series of questions that every mentor and mentee answered when they signed up for the program:</p><ul><li>Level/Title [Mentor/Mentee]</li><li>Years at Vouch [Mentor/Mentee]</li><li>Years of experience in engineering [Mentor/Mentee]</li><li>Have you been a mentor/mentee before [Mentor/Mentee]</li><li>List of topics to be mentored in/to mentor. Preset list + ability to add custom topic [Mentor/Mentee]</li></ul><p>This small set of questions allowed us to pair mentors to mentees without overwhelming them. We knew the first pass at pairing wouldn’t be perfect, but we tried to make sure the mentor was at least one level above the mentee, had as many overlapping topics as possible, and was on a different engineering team.</p><p>The last (and most exciting) step was to kick off the program. We hosted a meeting to go over the program goals, discuss the matches, and go over suggested practices and strategies. Those practices and strategies included:</p><ul><li>Mentees setting up meetings on a 2 week cadence to start</li><li>Mentees sharing their list of topics with their mentor</li><li>Mentors thinking about articles, blog posts, documentation, books, etc that can be helpful to guide discussions.</li></ul><p>With that, the program had begun. Once a month we meet with the mentors to share successful strategies, address concerns, and find other mentors in the group that might be able to help a mentee that is looking for a topic outside of their mentor’s expertise.</p><p>Two months in we also sent out a survey to the mentors and mentees to get feedback. The major takeaways and resulting actions were:</p><p><strong>Feedback: More guidance for mentors as to what resources and tools they could use.</strong></p><ul><li><strong>Action: </strong><em>We set up a shared page where mentors could share helpful resources (blog posts, books, coding problems, online tutorials, etc) they had used.</em></li></ul><p><strong>Feedback: Suggested topics for mentees to bring up.</strong></p><ul><li><strong>Action: </strong><em>We set up a shared page with conversation topics for the popular interest areas of the mentees.</em></li></ul><p><strong>Feedback: Formal mentor training. Some mentors had never been a formal mentor before and were looking for training.</strong></p><ul><li><strong>Action</strong>: <em>We are working with our HR Business Partner to set up a formal mentor training for the mentors in the program.</em></li></ul><p>The Vouch mentorship program is in its early stages, but overall we have been successful in creating a program that helps our engineering team grow and reach their own career goals. The program is expected to be a living, breathing entity, and we continue to make adjustments and improvements based on people’s feedback. An engineer’s most powerful resource is the knowledge and experience of the engineers surrounding them and an Engineering Mentorship Program is a great way to spread that expertise.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10522a621566" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vouch-engineering/the-inception-of-an-engineering-mentorship-program-10522a621566">The Inception of an Engineering Mentorship Program</a> was originally published in <a href="https://medium.com/vouch-engineering">vouch-engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>