<?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 Beier Cai on Medium]]></title>
        <description><![CDATA[Stories by Beier Cai on Medium]]></description>
        <link>https://medium.com/@beier_commit?source=rss-4fd00a3d677f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*9ANY17sCCJGO4dY1MqGuOA.png</url>
            <title>Stories by Beier Cai on Medium</title>
            <link>https://medium.com/@beier_commit?source=rss-4fd00a3d677f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:26:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beier_commit/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[Committed to Success: Hai Hoang, Tech Lead at Planworth]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-hai-hoang-tech-lead-at-planworth-38f8442cebe9?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/38f8442cebe9</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Tue, 31 Mar 2020 20:09:59 GMT</pubDate>
            <atom:updated>2020-06-14T21:48:45.193Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Hai Hoang is a Commit engineer who joined </em><a href="https://www.planworth.co/"><em>Planworth</em></a><em>, an early-stage </em>wealth <em>planning SaaS platform in 2019 as a technical lead. We sat down with him to hear about his journey.</em></p><p><strong>Tell us a bit about your background before joining Commit?</strong></p><p>I spent the first two-and-a-half years of my career at a large tech company, then did my own startup for around two years. It was an on-demand personal assistant app. We launched our product and got to market, but market conditions were bad at the time. Investments dried up and we ended up having to shut down.</p><p>I went back to the first tech company I worked for, to figure out what I wanted to do next. Then I worked for a few startups, but nothing was really going anywhere. That’s when Commit came into the picture. I was one of the first engineers, part of the founding team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQBYeNwC1ca1zxUTpfhn5Q.jpeg" /><figcaption>“You don’t really know how you get along with people until you work with them, right? To me, Commit offers a really good opportunity to get a feel for that before making a long term commitment”</figcaption></figure><p><strong>What drew you to Commit?</strong></p><p>The people. I had worked with some members of the Commit team at other startups. The people are really fun and they had senior engineers on board. I was attracted to that, because I knew I could learn a ton from them. It was a very good environment for me to start new projects all the time and learn from some of the best.</p><p>It was clear that Commit’s goal was to minimize risk for engineers. We wanted to offer engineers the opportunity to meet with startup founders and assess what their product was and what their business strategy was before fully jumping in — that really appealed to me, because I had been with failed startups before.</p><p><strong>How did you get connected with Planworth?</strong></p><p>I actually had no intention of leaving Commit. I was there from the beginning, I was helping build the company — I thought there was no reason for me to leave. But then Planworth came around, and the product and the team got me very interested. I could see potential that I hadn’t seen with other projects. Plus, it’s in the fintech field, which I’ve always had an interest in but have never been able to dip my toes into.</p><p><strong>What attracted you to Planworth?</strong></p><p>I liked the fact that they recognized their product-market fit. That’s something many startups don’t have from the beginning. Most startups have an idea, then they build a product, then they go out and validate it with the market. Planworth built a rough proof-of-concept and got immediate validation. So by the time I joined, it was clear they had found a market, figured out a business model, and had a plan for earning revenue. It was amazing to see. Also, it was great that I had a three-month period working with the founders and the team, before I formally joined, so I really got to know them and their product.</p><p><strong>What has it been like so far?</strong></p><p>It’s been very, very good. They’ve given me the autonomy and authority to implement my vision of what I want a team to look like, which I’ve never had the opportunity to do. They gave me that trust. And not just from the management perspective — even the engineering team trusts me to make decisions. It’s a great career opportunity because previously I’ve been a team lead, where you’re running projects, but at Planworth I’m also managing people.</p><p><strong>How has your time with Commit helped you in this new role?</strong></p><p>I’ve definitely been able to transfer things I learned at Commit onto my work at Planworth. At Commit I learned about project management, especially figuring out ways to deliver work in a shorter time frame. A lot of the technical skill sets I picked up at Commit also set me up for success at Planworth, like devops tricks. I’m still learning a lot at Planworth. Maybe not as much on the engineering side, but on the management side and team lead side. I have Tarsem and James <em>[Planworth’s co-founders]</em> teaching me and coaching me. So I’m learning every day.</p><p><strong>How has it been working with two non-technical founders?</strong></p><p>It’s been good. Engineering is very different than what they’re used to, but they’re very open-minded and understanding about the process. That’s one of the characteristics I like about them. They care about scalability, and they care about having clean code and tests and stuff like that. Not all founders do.</p><p><strong>What would you tell or say to other engineers considering joining Commit?</strong></p><p>Go for it. And keep an open mind, because every single project is very different. You end up working with different teams and different people. You don’t really know how you get along with people until you work with them, right? To me, Commit offers a really good opportunity to get a feel for that. I think it’s a fantastic model. As a person who comes from the startup world, working on multiple failed startups, it really does mitigate the risk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38f8442cebe9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-hai-hoang-tech-lead-at-planworth-38f8442cebe9">Committed to Success: Hai Hoang, Tech Lead at Planworth</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Committed to Success: Clara Tsang, Software Engineer at Procurify]]></title>
            <link>https://medium.com/commit-engineering/committed-to-success-clara-tsang-software-engineer-at-procurify-fdc1e3998bab?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fdc1e3998bab</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Wed, 25 Mar 2020 15:59:02 GMT</pubDate>
            <atom:updated>2020-06-14T21:47:10.295Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Clara Tsang</em> <em>joined Commit in 2019 and quickly found a role as a front end developer with </em><a href="https://www.procurify.com/"><em>Procurify</em></a><em>, a rapidly growing Vancouver-based startup in the spend-management software space. We sat down with Clara to hear about her journey with Commit and Procurify.</em></p><p><strong>Could you tell us about your background and experience before joining Commit?</strong></p><p>I graduated last year from SFU’s Systems Engineering program, which actually isn’t a software program, it’s an electronic systems engineering program. I was exposed to software, but definitely not much web development. I did a few co-ops — mostly QA positions. This was mainly manual QA and unit test writing. After graduation, I worked for a digital marketing firm focused on the automotive industry. They hired me to do web dev, even though I didn’t have much experience. I was working with WordPress, so mostly vanilla JS, jQuery, HTML, CSS and PHP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L2dld765KqrFGU4ly7V-1A.png" /><figcaption>“It’s really easy to get lost navigating the world of nasty technical interviews and multiple-level screening that’s the reality in the tech industry today. Commit offers a better route.”</figcaption></figure><p><strong>What drew you to Commit?</strong></p><p>I was ready for a change, but I thought it would be hard to get an interview with my current skills and not easy to gain new skills while working full time. I talked to Cong Ly [<em>Responsible for onboarding new Engineering Partners] </em>and Commit was ready to take me on and train me on the job. Joining Commit was an upgrade in every way. It actually sounded too good to be true: maximum flexibility with remote working and on-the-job training. Plus it was higher pay and I got to work with technologies and standards that feel more relevant to the industry.</p><p><strong>What were you hoping to achieve when you joined?</strong></p><p>First and foremost it was to level up my front end skills because at the time I felt that I wasn’t there technically. My one-year plan was to start looking into full-stack work.</p><p><strong>How did your time with Commit help you toward those goals?</strong></p><p>The first two weeks were focused on onboarding, where I started learning React by following along with the React docs; the project I was going to be placed on first was a React project. I was matched up with a technical mentor from Commit, who pointed me towards great resources so I could learn the stuff. I met up with my mentor a lot in those first two weeks.</p><p><strong>How did you get connected with Procurify?</strong></p><p>Early on, Cong said he had a project he thought would be a great fit for me. That was good for me at that point, because I didn’t really know what I wanted or needed.</p><p><strong>Can you tell us about Procurify?</strong></p><p>We make a spending tracking app for businesses, so I guess you could say our product mission is to make spend culture in companies faster, less complex and more transparent. They’re also trying to create an awesome place for people to work.</p><p><strong>And how are they doing at that last goal?</strong></p><p>A really good job. I feel like Procurify really cares about its employees and trusts them. They have a responsible time-off policy (AKA unlimited vacation), flexible hours, and there’s a lot of effort to be remote-forward.</p><p><strong>Are you learning lots and developing new skills?</strong></p><p>Definitely. I think that was the main reason why I decided to stay with Procurify. Everyone in the office seems pretty passionate about their job, which is pretty new for me, too. As someone who’s a bit newer to the industry, there are so many people there I can learn from. And in engineering, there’s a lot of initiative to keep improving things and stay up to date with the latest technologies.</p><p><strong>What advice would you give to other engineers about joining Commit?</strong></p><p>I’d say just do it. Commit is designed by engineers for engineers, so there’s something in it for every engineer — well, at least any engineer interested in continuous learning and working remotely. If you’re looking to learn a lot and work on different projects, there’s that option. And if you’re looking for a new company to join full-time, there’s that option too. It’s really easy to get lost navigating the world of nasty technical interviews and multiple-level screening that’s the reality in the tech industry today. Commit offers a better route.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fdc1e3998bab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/committed-to-success-clara-tsang-software-engineer-at-procurify-fdc1e3998bab">Committed to Success: Clara Tsang, Software Engineer at Procurify</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expanding the career options of software engineers]]></title>
            <link>https://medium.com/commit-engineering/expanding-the-career-options-of-software-engineers-d8bb9e59c94f?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8bb9e59c94f</guid>
            <category><![CDATA[career-paths]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Tue, 17 Dec 2019 18:51:00 GMT</pubDate>
            <atom:updated>2019-12-17T21:31:31.377Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why does an engineering career have to be about racing to the top along universally predefined paths, instead of being driven by passion and working to become the best version of yourself? </em><a href="https://www.linkedin.com/in/beiercai/"><em>Beier Cai</em></a><em> takes a deeper dive into the </em><a href="https://medium.com/commit-engineering/the-career-gap-for-entrepreneurial-engineers-b0fc17b9e957"><em>career gap</em></a><em> and limited options for software engineers and considers a better way forward.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qpRd8_G2iumWpvniR7AJfg.jpeg" /></figure><p>Raise your hand if this sounds like you.</p><p>You just graduated with a computer science degree, probably with a few co-op job experiences with a mix of startups and established companies, and now it’s time to face your first major career decision. Do you start your own company or join a startup? Or do you find a decent job at an established company with a stellar paycheck?</p><p><strong>The startup cycle</strong></p><p>For the small percentage of engineers who choose the startup route, a year or two later, when the startup is likely to fail, they face the same decision again. A handful will choose to return to the startup path in the hope of winning the unicorn lottery. Best of luck with that! But most engineers in this situation will choose to work for an established company for a more stable and bigger paycheck — especially those who have to pay back their student loans.</p><p><strong>Corporate constraints</strong></p><p>For the first few years at an established company, life is good. You learn a lot, progress from a junior developer to an intermediate, and you earn a solid salary, helping to pay off your student loans and hopefully start filling your savings account. But after coding for three to five years, you start to think about how to build a career. You start dreaming about advancing your career in a way that makes sense to you and also working on projects you are passionate about.</p><p>While these dreams are vivid, at some point you confront the reality that there are really only two predefined career options for you in a corporate setting: become a manager, dealing with people and processes instead of tech, or become a technical guru (or Individual Contributor) in specialized technical areas. Both career tracks involve significant competition and an ongoing race to the top, with only a limited number of winners in each category. These career paths are generally predefined and rigid, without much consideration of who you are as an individual. The paths might work out perfectly for some, but for many, a career plateau isn’t far away, since the tracks just don’t match your highly personalized interests, talents, working styles, and needs. At this point, you can jump to another company to work on different domain problems for a fresh challenge, but soon you’ll face the same fork in your career journey: manager or technical guru.</p><p><strong>Back to startup square one</strong></p><p>But there is a third option, outside the conventional corporate environment. You can go back into the startup world, where you can fulfill your passion, learn new things, build cool stuff, move fast, wear multiple hats and work with lots of interesting people. But by this point in your life, chances are your risk profile has changed. You may have started a family or you’re thinking about it. You bought an apartment, or you’d like to, in an expensive city. The risk and reward tradeoff of a startup may not be as attractive as it once was when you were fresh out of school.</p><p>To mitigate the risk, you can try to identify a potential winning startup, but can you really do a better job than the VCs? They study startups all day long and still get it wrong nine times out of ten. Even if you get lucky and find a few promising opportunities, you’ll have to go through dozens of conversations and stressful interviews while hoping your current boss won’t find out. After several months of searching, you might land a great opportunity, but it’s likely that you’ll end up back to square one again after a couple of years — the odds are against you. Thinking about all this, all of a sudden a stable job at an established company, even if it’s not that exciting or fulfilling, doesn’t seem like such a bad choice.</p><p><strong>Start consulting</strong></p><p>A fourth option is to start your own software consulting firm. You could start solo, then gradually build out a small team. The appeal is obvious: get paid well, be your own boss, and have the freedom to choose when to work, how to work and what to work on. But you quickly realize that you have to constantly find new work, create numerous SOWs, deal with unhappy clients, chase down unpaid bills, and manage accounting, legal, taxes, and other admin tasks, leaving little time to build cool software. It might be a great fit for some, but it’s not an easy or satisfying route for most.</p><p><strong>Or go freelance</strong></p><p>A final option is to become a freelancer, using a platform to help you streamline the overhead and admin. But you still have to compete for work, potentially with very cheap labour from other parts of the world. It’s not the right fit for many engineers.</p><p><strong>A new way to think about your career</strong></p><p>Why should engineers be limited to these five career options? and why are there so much risk and friction working in a startup environment? Many of us have fairly straightforward career desires: you want to be challenged, build something meaningful, continually learn and share, work with amazing team members, and enjoy financial stability with the potential for a big upside. You want to improve and become your best self, not necessarily compete with others to climb the career ladder. In essence, you are a <a href="https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047">software engineer that would thrive in a startup environment</a>.</p><p>As Earnest Capital’s Tyler Tringas noted <a href="https://tylertringas.com/the-entrepreneurs-new-path-of-maximum-optionality/">in a post</a> earlier this year, new tools, resources, and funding options are enabling entrepreneurs to carve out unique and highly personalized startup journeys for maximum optionality. This is good news for the startup entrepreneurs, but what are some of the options and opportunities that could give startup engineers more control over their career paths, and greater satisfaction?</p><p><strong>Balancing risk and reward</strong></p><p>Ideally, engineers would be able to pursue fulfilling roles working on projects they are passionate about. For many, it could be a position with an early-stage startup, but with a degree of financial stability. We all know that startup work is often exciting and the experience energizing, but the vast majority do not yield significant financial payouts. What would be great is a startup experience that combines ongoing financial stability, as well as the potential upside — turning your sweat into a diversified equity portfolio with long-term growth potential — with fulfilling work.</p><p><strong>Filtered opportunities</strong></p><p>In a perfect world, engineers wouldn’t have to grind to find a startup with great potential that fits their skills and passion. As an individual, it’s just too much work. It would be great to have access to a system that vets and filters companies into a selected few that best fit, so you can focus on your work, not constantly searching for opportunities or round after round of interviews. Even better, engineers would have the ability to dip your toes in a variety of projects for an array of companies, to find the projects and teams that match your objectives, talents, personality and working style.</p><p><strong>An organization that prioritizes you</strong></p><p>At most companies, shareholders and customers come first, and employee interests and personal and career development are not the priority. While this might make sense from a certain perspective, in practice this incentive structure often leads to burning and churning through the staff. Engineers would be better served by a special agency that is incentivized to prioritize your interests and has a fiduciary duty to you and your career growth.</p><p><strong>Sharing experiences and expertise</strong></p><p>Engineers would also benefit from being part of a community, a supportive and purposeful structure where you can share with others, learn from experts and develop skills in a wide array of areas, surrounded by like-minded peers, regardless of which companies you work for. Sometimes engineers are treated as cogs in the corporate machine. Wouldn’t it be great to find customized support and career counseling, to dive deeper into skills and interests, to get assistance in finding the right pathway for your unique skill set and long term goals?</p><p><strong>Commit.dev</strong></p><p>Commit.dev, which I founded earlier this year, is part of the new cohort of companies helping to expand the options for engineers. These challenges and opportunities inspired us to create a community that is aiming to provide top tier engineers with more choice and greater control over their careers — choices that balance risk and reward and provide a supportive environment, endless opportunities to learn, and the freedom to choose your own adventures.</p><p>Want to be part of the Commit community, to expand your career options in new and rewarding ways? Let me know what you think, and if you want to start a conversation about where you are in your career and where you want to go next. Also, make sure to follow our <a href="https://www.linkedin.com/company/commitdev/">LinkedIn Compay</a> page to stay up to date on our latest news and developments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8bb9e59c94f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/expanding-the-career-options-of-software-engineers-d8bb9e59c94f">Expanding the career options of software engineers</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We’re Creating a Tailored Learning and Development Program for Entrepreneurial Engineers, and We…]]></title>
            <link>https://medium.com/commit-engineering/were-creating-a-tailored-learning-and-development-program-for-entrepreneurial-engineers-and-we-f0bbdcdd0ee7?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0bbdcdd0ee7</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[learning-and-development]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 18:47:16 GMT</pubDate>
            <atom:updated>2019-09-24T19:42:43.288Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>We’re Creating a Tailored Learning and Development Program for Entrepreneurial Engineers, and We Need Your Help (Part I)</strong></h3><figure><img alt="Two software engineers in an office writing code together." src="https://cdn-images-1.medium.com/max/1024/1*Cd2lJ1qLdpD6PP_JjLIkjg.jpeg" /><figcaption>Two engineers working together. Photo by Christina Morillo.</figcaption></figure><p><em>This post is part I of a series where we’ll document the ongoing creation of our learning and development program at </em><a href="https://www.commit.dev/"><em>Commit</em></a><em>. Stay tuned for subsequent posts that show what we’ve tried, what’s worked, what input we received, and even what didn’t work at all.</em></p><p>In my <a href="https://medium.com/commit-engineering">previous posts</a>, I talked about how Commit is dedicated to career growth, not just project work. From the beginning, we knew that if Commit was going to be built properly, we had to have a foundation that not only encouraged, but actually dedicated a certain element of itself to growth and development for each engineer. Our aim is to partner with talented and experienced engineers, but we also know a tech career requires life-long learning, and skills can get outdated quickly. Our plan is to set up Commit as a world class mentor and coaching network that extends well beyond just the tenures of the engineers who partner with us, and is dedicated to being a lifelong partner for each engineer’s growth. We want this learning to be driven by each engineer’s own goals, passions, and interests, so that we differ from traditional corporate programs that force development along either a management or independent contributor track.</p><p>We are still very early stage, we’ve tried a few things, we’ve collected feedback from our current Engineering Partners, and now I would love to hear your input as well; please let me know what you think in the comments.</p><p><strong>The Core Principles of Learning and Development</strong></p><p>At only half a year old, our learning and development program is still in its early stages. We expect it to grow and change over time, but we will adhere to the core principles that we set out at the beginning:</p><ol><li><strong>Individualized Learning</strong></li></ol><p>It’s important that we craft a program that is suited to individual engineers according to their own career progression goals and passions, instead of being dictated by the company. We want to differ from traditional corporate development initiatives, which involve large scale, generic training programs that give employees very limited choices.</p><p><strong>2. Hands-On Learning</strong></p><p>I know from experience–and the Engineering Partners at Commit have also reinforced–that the best learning happens when it’s hands-on, through real projects and work. Sure, a dedicated learning seminar is helpful, but without being able to apply that knowledge right away, the information is quickly lost.</p><p>We also know that the best work is that which is aligned to the passions and interests of the individuals assigned to it. This is why we’ve established deep profiles for each of the engineers that come to Commit, so that as the projects from startups roll in, we can ensure that we assemble teams who have the right skills, areas of interest and desire to work on specific opportunities at the helm. Unlike agency work, which can seem monotonous and quality of code base is not emphasized, we wanted a model where work is more purposeful, allowing the engineer to learn and grow. This is why we match startup opportunities that can leverage the existing skill sets of our engineers, but also enable them to learn something new.</p><p><strong>3. Help is Accessible</strong></p><p>If learning is going to be organic, and hands-on through actual projects, then Commit engineers need timely, easily accessible support from a large network of domain experts and mentors who are incentivized to help others and get help from others</p><p><strong>4. Mentorship over Management</strong></p><p>We don’t plan to hire traditional engineering managers as we scale. Commit Engineers work directly with startups providing autonomy and accountability to the quality of work produced, and helping build relationships that may actually facilitate long term hires within these new companies. We ensure that we bring in true <a href="https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047">Entrepreneurial Engineers</a> to form a highly effective peer-to-peer technical mentorship network. We also believe engineers can benefit from dedicated career coach who can assist their lifelong career growth beyond what individual companies can offer.</p><p><strong>Learning and Development — Key Findings So Far</strong></p><p>There are two key questions I have when it comes to growth and development: What’s most important to learn? And what is the best way to learn? I recently put this out to the Commit team in a learning and development workshop, and I want to know from you too, what your thoughts are.</p><p>Here’s some early feedback:</p><p><strong>What’s most important to learn?</strong></p><p>The team concluded that three areas were important to learn:</p><ol><li><strong>Technical Skills</strong>: Tech skills get outdated fast, every few years there are new, exciting tech innovations that engineers have to learn to stay relevant.</li><li><strong>Leadership</strong>: How to become the best leader at what you do and make people around you better (note in this case, ‘leader’ is not equivalent to manager)</li><li><strong>Entrepreneurship</strong>: How to be most effective and continue to thrive in the startup world?</li></ol><p><strong>What is the best way to learn?</strong></p><p>Here the team prioritized several learning techniques which we’ll look to employ in our learning and development program:</p><ul><li>Hands-on, learning by doing (real-world projects)</li><li>Peer to peer mentorship</li><li>Project on-boarding, involving a set amount of time to pick up new skills required by the job before being thrown into fire.</li><li>Quick access to help</li><li>Sharing of lessons learned</li><li>Training/certification — this was hotly debated, and we concluded that it would need to be directly aligned with the next project so that the information can be immediately applied in a real-world scenario.</li></ul><p>We’re also building tools to assist learning and career progression. Our team is currently working on tools to map out career/tech-skill progression for accomplished engineers to help guide others. In addition, we will have space for the team to have opportunities during their time with Commit to pursue their area of interest, such as creating/contributing to open-source, or building their own startup ideas.</p><p>Commit is for passionate <a href="https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047">Entrepreneurial Engineers</a>, so that all of our Engineering Partners can collaborate with, and learn from one another. The best talent will also attract the best startups, giving everyone better opportunities to grow. If this sounds like something you want to talk to us more about, visit commit.dev and request more info.</p><p>And please, let me know your thoughts in the comments, or DM me directly on <a href="https://www.linkedin.com/in/beiercai/">Linkedin</a>.</p><p><em>Interested in partnering with Commit? Visit </em><a href="https://www.commit.dev/"><em>commit.dev</em></a><em> to request more info.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0bbdcdd0ee7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/were-creating-a-tailored-learning-and-development-program-for-entrepreneurial-engineers-and-we-f0bbdcdd0ee7">We’re Creating a Tailored Learning and Development Program for Entrepreneurial Engineers, and We…</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is an Entrepreneurial Engineer (And How Are They Different From Other Engineers)?]]></title>
            <link>https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/af4ebcf88047</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Wed, 21 Aug 2019 05:23:01 GMT</pubDate>
            <atom:updated>2019-08-21T05:28:50.384Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6CthcwHcTFujCN5YH47z8Q.jpeg" /><figcaption>Entrepreneurial Engineers thrive in mission-driven startups.</figcaption></figure><p>Over the last few months I’ve spoken with a lot of engineers about Commit, and who we’re building it for. Sure, we aim to partner with exciting and promising seed-funded startups to help them get product-market fit faster, but what we’re really passionate about is optimizing our community for experienced, Entrepreneurial Engineers–the kind of folks that early stage startups dream of working with (and want to hire). We really don’t think anything currently exists for this unique subset of developers.</p><p>It’s worth clarifying, the word ‘entrepreneur’ is usually associated with people who want to build their own startups, so the quick assumption for the definition of ‘Entrepreneurial Engineer’ is developers who want to do the same. While it’s true for some engineers (we estimate a small fraction), I believe it can be and should be used in a broader sense: Engineers who thrive in startup environments.</p><p>Traditionally, there are two standard career tracks for engineers, either specialization or management. Both are great options, but an <a href="https://medium.com/commit-engineering/the-career-gap-for-entrepreneurial-engineers-b0fc17b9e957">Entrepreneurial Engineer is unsatisfied or bored with both</a>. They’re typically happiest when they’re hands on, and when they’re in environments where they can continue to grow new skill sets and solve different types of problems in different industries.</p><p>I have personally managed 50+ engineers at different stages of company growth at three different startups. In speaking with many of them about their career progression, I’ve identified three consistent qualities that make someone an Entrepreneurial Engineer:</p><ol><li><strong>Creative Problem Solvers</strong></li></ol><p>One of the core qualities that I’ve observed of these folks is that they love building new products and solving customer problems. They care deeply about the product, and have strong empathy for customers, thinking about solving real customer problems, not just technical challenges. While they’re not designers, they’re knowledgeable enough to work with designers to come up with the best user experience. They might consider themselves ‘<a href="https://medium.com/mindorks/no-more-software-engineers-product-engineers-is-the-new-cool-bb14f1c657c5">Product Engineers</a>’ who thrive on startup work.</p><p>Entrepreneurial Engineers understand business priorities and know when to make the right compromises, working closely and effectively with the product team–including founders–to iteratively deliver customer value. They are not driven to scale the corporate ladder, become over-specialized or maintain old code. They want to solve problems that they’ve never solved before, or that no one has ever solved before. They’re keen to push themselves to the peripherals of the tech stack to try new things and be all across the map in terms of projects, from frontend to DevOps. A desire for continued growth is important.</p><p><strong>2. Engineer’s Mindset</strong></p><p>They are thoughtful problem-solvers that take pride in what they build. The quality of the code base is really important to them. They whither in environments where they’re given robotic or monotonous tasks, churning out projects. Instead they want to craft exceptional code that their whole team enjoys working with. They are an engineer’s engineer and thrive in a community environment where they can pass on their learnings to others, and in turn pick up some new skill sets from those around them. They’re eager to hear others’ perspectives. These are engineers who look for inclusive environments where team members respect each other, and as a result can come together quickly, figure out how to fix a problem or tackle a new challenge, and ship code faster.</p><p><strong>3. Experienced</strong></p><p>While many folks may know right out of school that they are most passionate about working at startups, a truly Entrepreneurial Engineer has actually spent time in a startup environment or innovation wing of a global tech company. They live and breathe lean and agile practices, and know what it takes to manage multiple priorities, fight daily fires, and make things up as they go. These are Engineers who have had a win or two at a large company or developing innovative new products and systems. And they know what they want to learn, as well as what they can teach others.</p><p>They are highly self-driven and do not require an environment where they’re required to be in an office or to be managed, or one that values time at your desk over output. They know how to create amazing software individually or within a team regardless of where or when they work.</p><p><strong>Learn more</strong></p><p>These are the kinds of folks we’re building Commit for. And we already have a brilliant team started. If you’re interested in learning more about partnering with Commit as an engineer, visit <a href="http://www.commit.dev/">www.commit.dev</a> to learn more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af4ebcf88047" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047">What is an Entrepreneurial Engineer (And How Are They Different From Other Engineers)?</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Career Gap for Entrepreneurial Engineers]]></title>
            <link>https://medium.com/commit-engineering/the-career-gap-for-entrepreneurial-engineers-b0fc17b9e957?source=rss-4fd00a3d677f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0fc17b9e957</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Beier Cai]]></dc:creator>
            <pubDate>Wed, 31 Jul 2019 14:58:27 GMT</pubDate>
            <atom:updated>2019-08-21T05:37:51.720Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Engineer writing code on laptop at a startup." src="https://cdn-images-1.medium.com/max/1024/1*UjIXirgONXs1p_bUpAgdlQ.jpeg" /><figcaption>Engineer at a startup. Photo by Matthew Henry.</figcaption></figure><p>In early 2019, I stumbled across a fascinating challenge in the engineering community. Intuitively, I always knew it was there. As an experienced engineer myself who is more suited for the startup experience than the traditional tracks offered, I was well aware of the pain points of my own experience. I also managed over 50 engineers, and saw first hand how their own career progression was very challenging; for many, they didn’t want to become managers, which meant the only option I was left to offer them was that of a specialized Individual Contributor, which was too limited in scope. This persistent challenge was always there. What am I talking about? The massive career gap for <a href="https://medium.com/commit-engineering/what-is-an-entrepreneurial-engineer-and-how-are-they-different-from-other-engineers-af4ebcf88047">Entrepreneurial Engineers</a>.</p><p>My discovery (or enlightenment) came through another challenge I was facing: I had a team of talented engineers with entrepreneurial mindsets and a passion for growth. These engineers, like other experienced, entrepreneurial engineers, were unique on the career spectrum. They each came with a Swiss army knife of talents and were most happy at work tackling a variety of challenging problems, from building products for new industries to scaling large complex systems. They’re lean. They’re agile. They have growth mindsets.</p><p>We had just sold my previous startup, First Coin Capital, and I was eager to keep this team together, despite not having another idea to work on. I knew from my own experience that if I didn’t keep the team together they would face the unenviable task of searching for new startups–a lengthy process–or avoiding risk and taking on the uninspiring role of a large corporate job.</p><p>It’s not hard for engineers today to find jobs. It’s hard for <em>Entrepreneurial </em>Engineers to find a job they’re passionate about. They struggle, as I did, with the traditional tracks offered by large organizations: Too hands-on to be fulfilled as managers; too diverse to be pigeon-holed into a specialty. Startups offer the ideal type of work, but as they mature the work changes. This leaves this special breed of engineer with a common career dilemma: stay, and stagnate in an increasingly corporate environment; or leave, and endure the risks of starting something new. It’s why many Entrepreneurial Engineers find themselves bored yet hesitant to make a new move.</p><p>So I found myself thinking of solutions to the top problems these engineers were facing, in order to give this talented team a fresh career experience, and (without realizing it), nurture the beginnings of an engineering community.</p><p>These problems as we see them (and I’ve now conducted 50+ interviews to confirm my theory) are:</p><p><strong>1. “It’s a lot of work to try and find the next promising startup.”</strong></p><p>Most engineers are spending time working, not networking, which means that when it comes time to find the next startup, they’re limited as to exposure. Many startups are small, and under the radar. This issue is compounded by the fact that Entrepreneurial Engineers want startups that align with their passions, and that have the right company culture. Plus, it takes anywhere between 10 and 20 interviews (having fun coding fibonacci sequence 10 times?) to land the right role, and who has the time for that? Finally, if in a few months it’s clear that a startup isn’t the right fit (which happens), there’s a new dilemma of whether to quit, and have to justify the short stint on your resume, or stay to log the time but knowing it’s a losing battle.</p><p><strong>2. “Quitting a stable job is a financial risk.”</strong></p><p>The thing about startups is, while they offer amazing opportunities, they may not have amazing comp packages (at least at first). The once alluring promise of equity to offset the risk of an early startup (and lower pay) is no longer as enticing as it once was. Only a precious few startups really cash out significantly, and the likelihood of an engineer working at more than five or six in their career is low, and even if they could, the odds of one big exit is still against them, meaning there’s a lot of risk in a limited portfolio.</p><p><strong>3. “Working for large enterprises pays well. But they’re unfulfilling.”</strong></p><p>That leaves a lot of engineers deciding to hedge their bets and join a large corporation, sometimes with a promising innovation arm. There’s little risk and a lot of financial gain. However, the issue remains that large orgs have little incentive to move quickly, and often come with bureaucratic work environments that can be stifling, and inflexible. What’s worse, is we often hear that engineers don’t feel fully utilized in these enterprises, with only a fraction of their potential being tapped into.</p><p>And the list goes on: it’s hard to access good mentor, and they’re at the mercy of their current manager’s abilities; they may lack the skills or know-how to negotiate full compensation; and there’s not a large and stable community of like-minded people to learn from and share with.</p><p>From this realization, the idea of Commit was born as a way to provide a career experience between startups that de-risks, and reinvigorates Entrepreneurial Engineers. Commit is a community of mission-driven engineers who partner together and pool their talents, interests and experiences to work on passion projects, explore and work with new startups, learn from one another, and grow their skill sets (without sacrificing financial stability). And, while they’re at it, they can find their next big win, or just come back to Commit if things don’t work out. We designed it as a hub-and-spoke model to allow our engineering partners to work remotely, and according to their needs during this experience. We’ve also built in equity so that we operate like a true partnership, like the VC model, everyone benefiting from the diversified portfolio of startups we work with.</p><p>Commit is not designed to be a job. It’s a life-long partnership. And we hope you’ll join us. Visit <a href="https://www.commit.dev/">commit.dev</a> to learn more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0fc17b9e957" width="1" height="1" alt=""><hr><p><a href="https://medium.com/commit-engineering/the-career-gap-for-entrepreneurial-engineers-b0fc17b9e957">The Career Gap for Entrepreneurial Engineers</a> was originally published in <a href="https://medium.com/commit-engineering">Commit Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>