🦄👩💻👨💻We're looking for our #CTO
If you're looking for the "startup life" build technology that not only helps millions of children around the world but have the opportunity to own everything related to tech, grow your own team, work with amazing people and have fun then, let's talk.
Keen to relocate to Melbourne Australia? We'll cover everything for you ✈️
Here is a sneak peek of Dystech:
~ 🤼 We're 5 people, very agile, all with superpowers from ML to Literacy expertise
~ 🖐 You're in good hand, multi-time founder, we made mistakes in the past, we've learned from it
~ 😍 It feels good to wake up knowing we're supporting struggling students around the world
~ 💸 We have amazing & supportive investors
~ 🌎 We're solving a global problem, we have a global vision and high ambitions
Sound good? Get in touch! https://lnkd.in/gt7VQaVd
PS: Credit to Bryan Helmig for this amazing CTO growth tree picture
Can Tapflow.app be your CTO?
You are getting into hype tech instead of something that can build and maintain a business system with. Drop the tech requirements from the advert and ask the potential CTO what they suggest using after you explain what you want to do.
Let me know if you want to have a 3th party technical advice on what you are doing (contacts in profile).
Hey, thank you for your feedback Nikolay! Do you mean from an interview perspective, remove the tech stack and see what the candidate would sugest?
You can do that only if you have a good tech person to conduct the interview, otherwise it is pointless conversation.
In general CTO interviews (when non technical people are involved) are more about compatibility as a person, work ethics and discussion of the product and what is expected from the CTO to deliver.
Not sure how did you decided on the tech stack you have listed, but that is the CTO job, if you already have someone deciding this just hire a head of development.
CTO is more of a technological planning to achieve the goals of the business development, selecting the best technology to develop & maintain/support the product(s) now and at least the next 2 versions (3-5 years) and also to monitor new technology trends and evaluate their fusibility for future business and technical development.
Head of development is someone that executes the CTO plans, ideally that is the same person, but that also depends on the size of the company and the projects.
Hey, thanks for sharing your view. I feel that I have a different definition of CTO. The role of the CTO for me completely depends on the stage of the company.
When you start, the CTO is 100% hands-on building an MVP, as you grow from 2 to 5 engineers, the CTO role evolves towards something around 80% coding 20% management/hiring and as the company scale, this changes and can look different for every company.
We are at phase 2 where we have a couple of engineers with us, a product on the market with paying customers and about to raise $1M+ seed round.
That would be why we have stated our existing tech stack in the JD because the role of the CTO in this context is not to start everything from scratch, but more to slowly take ownership of the existing product and architecture and evolved it in the best way possible (changing tech stack could also be an option) 😇
you are right about the changing requirements for the CTO, I was assuming that as you are offering a salary you have passed the "CTO as a title only" phase and you are looking for a real one.
Problem is you need to be very lucky to get the software developer that builds the MVP to be able to create and lead a good dev team and create a decent strategy for future development.
MVP's are throw away in 90% of the time, it is obvious you did not find the right person in the beginning and it is a good thing you are looking for a CTO now, don't make the same mistake a second time (the person that did the MVP obviously was not good for the CTO position).
No idea what is you particular business situation so can't give you a specific advice, but what you have is build with different ideas and requirements, you may think it is not but from a technical point of view (especially when it comes to system architecture and code base) it is and using it as a base of your future business is a bad idea. In most cases trashing the MVP and starting again is the best way forward (obviously you need to be well funded and have a transition plan before you do that)
but I digress, good luck with your project.