Vaticle Reviews

4.6

90% would recommend to a friend

(17 total reviews)
avatar

Haikal Pribadi

95% approve of CEO

88% positive business outlook

Vaticle has an employee rating of 4.6 out of 5 stars, based on 17 company reviews on Glassdoor which indicates that most employees have an excellent working experience there. The Vaticle employee rating is in line with the average (within 1 standard deviation) for employers within the Information Technology industry (3.9 stars).

Reviews by job title

17 reviews
1.0
3 Nov 2022
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
1.0
16 Oct 2021

Don't go there

Recommend
CEO approval
Business outlook

Pros

Get to experience some niche technology.

Cons

High pressure at work. Constantly being micromanaged. CEO yelling at people frequently. Overtime paid with deliveroo only.

avatar
Vaticle Response
4y
Hi, I'm Haikal, the Founder and CEO of Vaticle. Thank you for taking the time to share your feedback with us. I apologise for the experience you've had that didn't seem to be so great. I do completely see where you're coming from, and so I'd just like to share my thoughts and hopefully some additional context. 1) Our work is indeed high pressure in nature. As a small startup working on a database technology used by global companies, the goal that we need to deliver on is definitely ambitious. The maturity and quality of code that's expected of every engineer is very high. Combined with the size of our open source community and commercial clients, the challenge that stands ahead of us every day only gets bigger. There's a lot of code to be written, and they need to be written well. To some of us, we find thrill and excitement in this type of work. However, I can understand that it may not be everyone's cup of tea. I apologise that this was not what you expected. We will continue to communicate this clearly to all future hires so everyone has the right expectation. 2) I can see how you could have felt micromanaged. As the technical founder of a database technology company that is still small in size, my day-to-day role (2021) is still as the company's software architect and lead programmer. In a much larger company, many of us would not expect the CEO to review a junior engineer's code. However, being the architect and lead programmer in a young and small software company, my responsibility today still includes reviewing every line of code that goes into the main codebase, along with the architectural consequences of every code contribution and software delivery. Being a database technology, where software reliability and scalability is of critical nature, these code and architecture reviews need to be performed very thoroughly and rigorously, especially among very junior engineers. I apologise that these reviews, especially those done by the CEO, made you feel micromanaged. We certainly plan to delegate these responsibilities to new lead engineers and architects as the company grows. However, these engineering practices do need to continue to ensure quality across our codebase, which today still needs to be performed by me, the CEO, as I continue to fulfil the role of a software architect and lead programmer. 3) I apologise for making you feel like I was yelling. I have often been told that my voice is a bit too loud at times, but this would be the first time I've been told that I'm yelling. I sincerely apologise for this unpleasant experience. I take your feedback very seriously, and thank you for reminding me of this; I will continue to improve on my manner of speaking. 4) People do get dinner delivered when they work overtime, as well as bonuses. When we do work late at the office, we want to make sure everyone is taken care of. That includes ordering in dinner of whatever the team chooses, as well covering transportation whenever it's needed. However, we don't usually have plenty of overtime; I would say 1 out of every 10 weeks do we have a bit more of a stressful week where we have to run the extra mile. Most weeks, most team members leave at very reasonable times. Sometimes, such as Q4 2020, when we were behind the deadline for releasing TypeDB 2.0 (then called Grakn), we had to really run the extra miles for several consecutive weeks, where for a few weeks, the work spilt to a day on the weekend. In these periods, we pay our team members daily bonuses for their overtime at rates much higher than the base salary. Today (2021), while our company is still young in size and revenue, we don't yet have a formal overtime pay scheme. We certainly hope to implement an overtime pay scheme starting next year (2022). However, for the past few years, since we've started making revenue, we have been able to reward employees for their overtime throughout the year, through salary bonuses, during salary appraisals. We will continue to reward our team members through bonuses for their overtime, and we look forward to implementing a formal overtime pay scheme next year too. 5) The technology stack we work with indeed may feel more "niche" than the general software development ecosystem. Today (2021), the main development language in our team is Java - the most widely adopted language for backend server development. For our build system, we use Bazel: a modern build system built by Google to handle large, heterogeneous, and complex systems. For our client-server communication, we use GRPC: a high-performant RPC protocol built by Google to implement stateful over-the-network library APIs. For our embedded storage, we use RocksDB: a highly performant embedded key-value store built by Facebook. For our Mathematical Integer Programming solver, we use Google OR Tools and SCIP to build our query planner. For distributed systems messaging protocol, we use ZeroMQ. For language parsing, we use ANTLR. For Actor Model distributed systems framework, we use Akka. There are more frameworks and libraries that we use, but the aforementioned libraries paint a picture of what our technology stack looks like. Compared to general software development, these libraries are considered more advanced and definitely "niche". However, when it comes to building low-level "systems engineering" required in building highly scalable databases and distributed systems, these libraries are prevalent, powerful and widely adopted. Mastering these libraries would allow you to grow as a distributed systems engineer, enabling you to work on any underlying infrastructure of internet-scale technology. I hope my comments above help us understand our team and culture with a bit more context. Thank you so much for sharing your feedback, as they will always help us improve. Haikal Pribadi Founder and CEO of Vaticle
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.

Viewing 1 - 3 of 17 Reviews

Glassdoor has 20 Vaticle reviews submitted anonymously by Vaticle employees. Read employee reviews and ratings on Glassdoor to decide if Vaticle is right for you.