6
13 Comments

How can I grow my entrepreneurship skills in my backend dev job?

Hi, does anyone have suggestions/advice on how I can grow my entrepreneurial skillset in my day job as a backend software engineer?

I'd love to grow and learn during my day job because I don't have much time outside work right now, so I'm curious if anyone else has found a way to incorporate this into your regular work. Like maybe there are certain opportunities to look for or different perspectives to practice?

Thanks!

on March 2, 2022
  1. 4

    1/ Explore how other roles like marketing, sales work.
    2/ As a dev, you get feature requests to implement. Understand the business reasons and business behind the requests.

    Once you start doing these two, you will eventually understand the Enterpreneur ecosystem. This is where most Devs fail too as Devs think that 'The implemented feature is bringing business' but it's actually 'The business is bringing the feature request'.

    1. 3

      1 is solid advice, but I'm still not sure how to do that in a way that fits into my role/company, since I work for a large (10K+ employee) organization. That is something I've done in the past though, and is definitely eye-opening!

      2 makes a lot of sense too. Seeing and understanding the big picture behind the small daily tasks is super important.

      Thanks upenv!

  2. 3

    I was also a backend dev and I did this by cold messaging people in the company and heads of departments. (I'd typically do this when I was already travelling to the HQ for other reasons)

    Company was ~400 people, I messaged the head of sales and asked for details about how sales at the company worked. He set meetings up with me with a few people in the sales org who told me about their role and how they worked with the people around them. From that I learned what the sales process was (really, what an example of a sales process is) and phases of deals are, that sort of thing.

    I did the same thing with marketing. I got to know a bunch of them and it actually helped a lot in my scope of understanding at the company as well as my network and understanding of how big orgs work.

    1. 3

      Thanks Matt! That’s a great idea to leverage connections within the company to simply ask and learn.

      I am wondering though, we’re people receptive to you reaching out to them? It would be very unusual at my company (10K+ employees) for a random dev like me to reach out to marketing/sales. Though that doesn’t mean I shouldn’t! I have actually chatted with some sales folks before. 🙂

      1. 3

        Yeah, they were super receptive and really energetic. Though some in the sales org were a bit confused about why I was interested in their world in the first place haha

        It was basically zero effort for the head of sales to set me up with a few people in his org, and since it was a tech company, he probably felt like getting engineering cross-pollination was a good thing. Same for the marketing team.

        I feel you- 10K feels big, but you work for the same company, so at least you already have something in common and people love to talk about themselves. Whenever I asked anyone about their work, I always just expressed that I think what they do is cool and how curious I was about their day to day and I had good results!

  3. 3

    Hey @Logan,

    Depending on your company structure, try to listen to other departments and what problems they have that "automation" or engineering work might highly benefit from. Ask your manager that the are some tasks that might benefit the overall situation of that team in X, Y, Z.

    Listen to how product people talk, convince each other, what metrics matter. Learning why we do things in a company where you are an individual contributor might help you.

    1. 1

      Thanks David! Solid advice. I’m always a big fan of optimizing/automating repetitive tasks!

  4. 2

    Do something intrapreneurial, an entrepreneur in your company. Take babysteps and learn.

    This could be e.g. coming up with a proposal how you can help the company do something better (i.e. faster, cheaper, more secure, easier, money saving). Champion and develop the idea, talk to people, "sell the idea" and concept to others, then see through the implementation.

    An example:
    As a backenend engineer you figured out that you can do something with less CPU cycles (or storage, RAM, bandwidth, etc.), so go talk to Finance & DevOps (or whoever owns the infrastructure budget) and propose to them changes how they can save money, then if they like the idea, have them talk to your boss/manager/sprintlead to convince them that you need to work on this.

    (Source: I once was the guy who owned the budget and I loved having people come to me with ideas how to save the company some money. Nobody likes to waste money.)

    1. 1

      Thanks for the detailed answer Jan! This is great advice and opens my eyes to some ways I can practice these skills.

  5. 0

    You should start a side project and try to make money with it. There are many backend devs doing the same in the WBE Space and they are learning a lot from each other and the other entrepreneurs...

    1. 1

      Thanks, but I am specifically asking for ideas on how to do this in my regular day job.

      1. 2

        As a backend dev myself I have to say that it is really hard because most companies don't have the flexibility to put devs in charge of a whole product. You can always ask to be responsible for one main project like moving to K8s or refactoring the code...

        1. 1

          Definitely! That’s the struggle. 🙂

  6. 1

    This comment was deleted 5 years ago