Ideas and Validation October 28, 2020

I'll give $10 to charity for a 15-minute interview with you

Scott Rogowski @scottrogowski

An incubator I'm applying to challenged me to talk to 40 potential customers by the end of this week. That's a tall challenge so I'm trying something new.

I am looking to interview experienced software engineers who regularly work in Python. Bonus points if you have data experience (e.g. data-science / data-engineering) or if you have leadership experience (e.g. you have been the decision-maker in buying software). I won't be trying to pitch. My goal is just to understand my market better.

To make things easier, here are the three charities I'll donate to. You can pick which one you like best. I'll send the receipt after I make the donation.

  • Project Healthy Children - My personal favorite. Supports food fortification programs in developing countries. This has a huge demonstrated benefit for early-age cognitive development.
  • Malaria Consortium - Malaria is cheap to prevent and doing so saves a lot of lives.
  • The Humane League - Make the lives of livestock better through advocacy and lobbying.
  1. 1

    40 in a week - that's a real challenge! Let's go! Not an engineer so can't help :)

    1. 1

      No worries. Thanks for the encouragement! It helps!! :)

  2. 1

    Happy to have a chat

  3. 1

    How many did you talk to so far?

    1. 2

      Seven 😂. I was expecting to get more from this post 🙂.

      They sent a rejection email this morning so I'm not on that time crunch like I was. I think talking to customers is incredibly useful and I would like to get as much as possible over the next week or two but I'm not desperately aiming for any number. A good rule of thumb I learned is to keep talking to customers until you stop getting new information. For now, I'm still getting new information so I'll keep going.

      1. 1

        What are you building?

        1. 1

          In an attempt to get good data, I won't pitch here :).
          But in short, I'm working on a different approach to two problems which might have the same solution:

          1. Slow code when processing massive amounts of data
          2. Backend architectural complexity and microservice madness
  4. 1

    You probably mean potential customers, not customers, right?

  5. 1

    happy to have a chat!

    1. 1

      Awesome! This is my calendly. Schedule whenever works: I appreciate it!

Recommended Posts