1

Taro amassed a lot of content in its courses and blogs - how long did it take to create initial MVP of quiz app before founders quit their jobs?

Profile picture
Senior Software Engineer at Taro Community6 months ago

Questions for Alex and Rahul which I know were covered in some videos somewhere in snippets, but maybe not all in one question. Taro has amassed a lot of great content in its courses and blogs -- how long did it take to create initial MVP of quiz app before the Taro founders quit their jobs to go and work on Taro full time as a startup entrepreneurs?

  • When did the founders pivot?
  • How long did it take to create initial content (blogs over the years, lots of videos, powerpoints etc.)?

It's impressive to see the amount of rich content, how long did it take for Rahul and Alex to conceptualize Taro (in its early form, name), what ways did they test the success metrics of various pieces of content for a single feature (video series, single video/blog etc.) - how well did they perform over a given period of time?

43
2

Discussion

(2 comments)
  • 2
    Profile picture
    Tech Lead @ Robinhood, Meta, Course Hero
    6 months ago

    Something that's been on my backlog for a while is to make a course on how to start a startup, but in the meantime, check these out:

    To answer the questions:

    • Rahul and I were working on the precursor to Taro for around a year before quitting our jobs. It was called Tech Career Growth community.
    • The content on Taro easily took us thousands of hours to make. We have a really high quality bar that is only getting higher. Each course takes us minimum 20 hours to release.
    • We never really had a hard pivot with Taro. Taro has tried many features over the past 2 years, but the core of helping engineers with high-quality content and community has always been the same.
  • 1
    Profile picture
    Tech Lead/Manager at Meta, Pinterest, Kosei
    5 months ago

    Like many other startups, Taro came more from listening to users rather than a stubborn perspective of what we want to build.

    We've constantly received feedback (implicitly and explicitly) from users about what would be most helpful, and we try to make something to satisfy their needs. Of course, we have opinions on what would be valuable, but we're also frequently wrong 😅