Looking for Technical Lead for SaaS Podcast Platform
Hello all,
I'm the co-founder of AudioStaq, a podcast hosting, and monetization platform. I'm currently looking for a technical lead to head development efforts as we start scaling our customer base.
Important details: Past the MVP stage, with early revenue. We make money from both SaaS subscriptions and programmatic Advertising. I've funded the MVP by winning pitch competitions, awards, and winning a ridiculous amount of AWS and Google App Credits.
About me:
I'm a Technical CEO/Founder but I'm not a true developer. Most of my experience comes from being a QA Engineer/Product Manager in gaming and ad-tech. I can write front-end code, some javascript, review code, write some SQL, talk and solve issues with the best developers. Trying to learn more react now. I also designed our current website/dashboard and closed all current customers.
What I need:
We are looking for a technical co-founder that can come in and get started fast. You would help us:
- Lead developments efforts
- Build new features
- Troubleshoot customer request, and fix bugs
- Review code
Tech Stack - Node, React, Firebase, Cloudflare CDN, Cloudflare workers, Google Functions, a full serverless stack.
How would you get compensated: I prefer someone who can work with equity while we continue to increase revenue. Current money in the bank is not enough to cover a real salary.
Last Words:
If anyone has any further questions, please reach out to me. When you write, please include the following about yourselves: Current Location, Experience, How many hours per week you're able to contribute to the project if you were to be brought on.
Please PM me your replies, email or post here. If detailed info is needed, PM is best. [email protected]
#looking-for-cofounder
Hey!
The decision was made on cost, current team skill set, and overall maintenance of the platform. I had to decide, keep plugging holes of the current system and keep losing customers, or try something new using what we learned about the first stack.
The current system crashes almost every 3 days because of memory leaks. Which, I've already spent money and time trying to fix. The short term solution was to reboot the server every 3 days via a script.
The system was too complicated and things would continue to break once we fixed another thing. I was not using contractors at first, I had a friend build the first version. Its debatable whether he made the right choices for scaling. Contractors were not the issue, the core codebase was as most on the contract all work was reviewed, and check by me and the cofounder before being merged.
I had multiple people pitch the new framework and we decided on this current one based on our needs. The core reason the new tech stack was decided is that I could not wait any longer or we were going to lost customers, some who are paying a good chunk of revenue. I didn't have time to wait it out.
With the new system, we have logging, we can find issues fast and fix them. The code is already less complicated and performance is way faster. On top of all that, the cost is almost half of our last stack. We are now maybe 70-75% feature complete.
I hope this helps. Please let me know if you have any other questions.