The interview process was pretty much similar to the one mentioned here : https://discuss.dgraph.io/t/the-people-process-at-dgraph/6631. But please note this is not the sequence in which it happens. I have listed down my experience below.

1. It started with a HackerRank screening test and consisted of 2 Leetcode Hard and 1 LeetCode medium question.
2. It was followed by another interview where they evaluated me on my understanding of concurrency and asked me to write a multithreaded program.
3. High level and low level distributed systems understanding concepts. Asked me to design a database which can support high reads and writes.
4. Cultural Round with leadership not CEO. They told me that I will be working closely with them and reporting to them.
5. Since the feedback was positive they asked me for reference checks which turned out to be positive.
6. They came back and asked me if they can have another round with the CEO. I was unpleasantly surprised. Now, the recruitment team said that I will be working with the CEO and not the people who interviewed me earlier but reporting will be with the leadership not CEO.
7. The recruiter scheduled another round with the leadership from round 4 to let me know about the work and what my responsibilities will be.

The recruiter reached out and said they will not be going ahead. I asked the reason and he said that the CEO/CTO(CEO doubles up as CTO) has concerns. The reasons which he gave me were pretty lame. I also asked him why did they schedule another round post discussions with Manish when there were concerns.

I had couple of learnings from this process and would like to share with the community.

1. I read multiple reviews from current and earlier employees at dGraph labs and all of them highlighted that the CEO/CTO(CEO doubles up as CTO) is not open to feedback. Furthermore, I believe that he doesn't trust his leadership too. Primarily, because if he would have been open to feedback and trusted his leadership he would not have scheduled an interview round post reference checks. Or may be the leadership he has built doesn't have a spine and that is how he wants it to be.

2. I admire that the CEO/CTO(CEO doubles up as CTO) communicates pretty well. However, he has a strong superiority complex which I could sense in the interview because he asked questions like "What's your execution speed" ? I could relate this question to one of the posts he has mentioned that at Google he could do things in days which other did in weeks/months. That speaks volume about the culture and the mindset he has about his ex-peers. May be he was super good or may be he worked on trivial tasks OR may be he just has superiority complex. On another note, this is his stackoverflow profile . In my team, I have freshers who have at least 10K points and here is the founding author of DGraph labs still struggling with 3 digits.

3. One should consider multiple scenarios before they make the move to join this company. One strong reason not to join Dgraph labs is that there is no tenure tech engineering leader in India who you can look up to and CEO/CTO(CEO doubles up as CTO) is not the person one would want one to look up to given he is filled up with so much of hubris and is in US.

4. I feel I just wasted my time.

In spite of the experience, I wish the company good wishes. However, I feel the company may be projecting itself as a rocketship but it is doomed to crash given the pilot in command is so disconnected from reality and full of hubris. I feel in my case compensation was the issue and they were mostly window shopping.