Nice tech, bad culture and management. Don't go there, especially if you are not a man. - Anonymous employee Vaticle Employee Review

1.0
3 Nov 2022
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

Interesting tech at the time, although stuck for a long time now. An amazing team, almost none of them still working there, but I did learn a lot from my colleagues. With all his defects, the CEO is very very good at getting people excited. In terms of nationalities, the team was a very varied, but on all other aspects, sadly there was an extreme lack of diversity.

Cons

- Constant micromanaging from the CEO who actively puts spanners in the works of very competent employees trying to do good work. - CEO and COO attitudes and arrogance actively made potential investors and client go away. I cannot count the number of bridges burnt with people who could have been and wanted to be genuinely helpful. - Complete lack of business direction, which caused regular cycles of hyper stress and layoffs. - Tech bro culture and unjustifiable late hours due to constant change of direction and focus on unimportant things. I am aware it is a startup, late hours happen (and to be fair work life balance can be way worse in startups). But the reason why they happened was most of the time not justifiable. It's not a "high pressure work" situation, it is more a useless deification of "hustle" and busyness - In some occasions questionable behaviour and lying encouraged and expected: e.g. employees made to create and use fake users on Stack Overflow to artificially boost conversations. After a single bad review on glassdoor the CEO personally chased current and former employees to leave glowing reviews (just check the dates of the reviews and observe how after the first negative ones suddenly new positive ones appeared in a matter of days, only to stop after the storm has passed). - The product is a typical solution in search of a problem. It was true at the time, it is painfully more true now that the novelty has faded - Company changed name four times in 7 years (OntoIt, Mindmaps, Grakn and now Vaticle). The internal concepts changed name even more often (sometimes going back and forth). Each of these changes require heavy code rewriting and often brings very little value. Yet they were often treated as "all hands on deck" situations, no matter the context - COO seems to drive away people more than attract them and obsessively focus on community building with very little returns for the effort and money invested (just look at the number of people attending the meetups after years of trying) PS: The CEO does yell a lot. It is not a matter of "having a loud voice" I remember witnessing him yelling at a potential (very important) customer and burning that relationship as a consequence.

avatar
Vaticle Response
3y
Thank you for your review and for keeping us accountable. I won't refute much of what you said, as you shared many truths about our past. I wish I'd done better 6 years ago, when most of the events you described transpired. First of all, I apologise for letting you down. I was 24 when I started the business 7.5 years ago. I was learning how to run a business the first time, the hard way, and often the wrong way. I started as a young and naive CEO, and I hope I've learned and grown since then. I did use to "micromanage". When someone made a mistake, I used to roll up my sleeves and show them how it's done or do it myself. It didn't scale. People will always make mistakes, including myself, and the only way to scale is to ensure people learn from their mistakes. I went from "how can I make this right?" to "what feedback can I give to help them learn?". This is a much slower strategy, but it's the only way to scale. There's truth in the "CEO & COO arrogance", albeit more in me than my COO. I also apologise for "burning bridges", as it was never my intention. I admit we were often frustrated -- in pitching, debating pessimistic views, etc. It was not sustainable. We learnt that people (investors, clients) will always have different expertise, and that we need to bridge the gap. There are truths in "lack of direction, stress, and layoffs", "name changes", and "hustle culture with unjustifiable pressure". As with many startups, we needed to iterate on our marketing strategy multiple times. I used to see every pivot as an existential threat. My fear was both genuine and naive, translating into more pressure than necessary. I don't know if the company would've died if we didn't push as hard, but I do now know that not every transition was existential. As for layoffs, we had one at the end of 2017, and one during the pandemic in 2020 when only two employees were laid off. The last time we had to pull long hours was when we completed Grakn 2.0 at the end of 2020. At the start of 2021, I was medically obese, and diagnosed with a condition that could be terminal in 5 years. This was a turning point for me. Since then, I've changed my work habits, diet, exercise routine, and my entire life. In the last 2 years, I have lost 25kg, I have a different approach to work, and I'm now engaged to the love of my life. I admit that, previously, "hustling" was the thing I knew best. I still know how to do it exceptionally well. However, I now also see that there's much more to life than our company. I'm sharing my personal journey because, for better and for worse, who I am as a founder affects our company's culture. I strongly disagree on "lying being encouraged". "Fake online users" has some truth but is not complete. It was not StackOverflow; you can verify that through these links. https://stackoverflow.com/questions/tagged/vaticle-typedb https://stackoverflow.com/questions/tagged/vaticle-typeql However, we did create some accounts to post questions on our old (Grakn's) discussion forum, the first time we launched it in 2016. We wanted to launch the forum, but we didn't want it to be empty, so we created questions ourselves to make new visitors feel comfortable. In hindsight, I should've just asked the team to post questions with their real username. Incidentally, earlier this year, we took down our old Grakn forum, and started a new one for TypeDB from scratch: https://forum.vaticle.com When our first review on Glassdoor came in, I did think it was bad that we had just 1 review and it's negative. So I did ask present and past employees for their reviews, to help us build a more comprehensive view of our company. I don't believe this was wrong, but I should have continued the culture of asking everyone who joined the company to leave a review. So this time, I'll do just that. We do lots of "code rewrites", but not for "little value". When we rewrote Grakn 2.0, performance went up 160x. Technology improves through iteration and evolution. We want to continue this, as it is how we advance. I disagree "COO driving away business". Our COO has more to learn, as do all of us. Driving commercial growth is hard, especially when we still had to iterate on our strategy. Present event attendees are expectedly lower, as we're focusing on performance before we invest in marketing again. On the point of me yelling, I sincerely apologise. I can see that the way I speak, coupled with my frustration in the past, would not have resulted in a positive experience. I do believe this has changed in the last few years. I hope my response gives you some peace of mind. I thank you for taking the time to hold us accountable. Most importantly, I sincerely apologise that you did not get the better version of me, and that I had let you down. I've tried to learn from every mistake I've made in the past, and I hope to deliver a better and healthier version of me to all our present and future employees. Sincerely, Haikal / CEO

Explore other reviews about Vaticle

5.0
30 Dec 2021
Recommend
CEO approval
Business outlook

Pros

Vaticle is a very personable company where the top officers are interested and involved in the success of both their company and the community around them. Building a community of users and technical experts around graph analytics has always been at the core of this company and I expect it will continue to be. Currently, I work as a Data Science Contractor for Vaticle doing custom graph database buildouts for top-tier clients. I think my experience with Vaticle is best demonstrated by a brief story of how I started working with Vaticle and how the relationship has grown. I first met the co-founders Haikal Pribadi (CEO) and Tomás Sabat (COO) at Graph Day 2017. After recognizing a common passion for data encoded in graphs we embarked on collaborative work analyzing PubMed medical literature. Since that time our relationship has grown and they have contracted my group to do a number of buildouts in a variety of domains including bioinformatics food science and cyber security. These buildouts have not only been a source of revenue but also an opportunity for my group to contribute and practice applying graph algorithms in bioinformatics, my domain of expertise. Working with Vaticle has contributed substantially to my growth as a Data Scientist and the growth of my company. They are always available to help and they know their business.

Cons

There are very few cons. The only issue I see is that Vaticle is a small startup. This is both a pro and a con, depending on the goals and personality of each employee. Workers need to be flexible, wear many hats, and understand the business thoroughly in order to contribute optimally. Having said that, the company is growing and I expect that it will take on more of the structured aspects of a larger company as it grows.

1
5.0
27 Oct 2021
Recommend
CEO approval
Business outlook

Pros

- An engineering-first company, code quality is prized highly to reduce compounding problems down the line. - Deadlines are flexible in favour of following the technically better path. - Naturally the two above points entail a longer-term strategy for the growth of the product. - Meaningful work. TypeDB is used in a wide range of critical industries, with many users from life sciences in particular. Often the use-cases have very meaningful motives with effects that will be seen in the real world in the coming years. - Strong community movement and events keep engineers connected to the impact of their work. - Employees have a strong sense of ownership over their products, and are given the mandate to follow their noses to engineer the right way, not the get-it-done hacky way. - Will not settle for anyone but high-achievers who mesh well with the culture Haikal has gone to great lengths to define. This certainly means the team is cohesive and you can trust your team members to come up with the goods. - The company has matured a lot over the period I have been employed for, and has learned the profile of employees that will thrive in this environment. - The leadership should maintain the existing culture of pursuing non-hacky code as this is probably the defining feature of engineering at Vaticle, which brings employees great satisfaction.

Cons

- Technical prioritisation and relationship with deadlines could be improved. - Self-taught learning required, but not enough resources for consistent mentoring to support this.

5
See reviews by: Helpful|Rating|Date|All