summarize: CTO at CircleUp, customer of Pinecone Expert can speak to being a current customer of Pinecone, decision making, and lead evaluator to bringing on the platform. The expert is very aware of other vector and open-source database offerings in the space and can speak to the pros and cons.

CTO at CircleUp. Reporting to the CEO, the expert is responsible for leading all the tech and software product development, machine learning, application development, etc.

The expert can speak to being a current customer of Pinecone, decision making, and lead evaluator to bringing on the platform. The expert is very aware of other vector and open-source database offerings in the space and can speak to pros and cons.

See Less

Screening Questions (3)
Q.
Customer: On a scale of 1-5 rate your familiarity with the following (rate 6 if you're a customer): Elasticsearch, Pinecone, Milvus, Apache Lucene/Solr

A.
6 Pinecone
4 Milvus and Apache Lucene/Solr
5 Elasticsearch

Q.
Customer: Describe your role in the evaluation and implementation of each.

A.
We've been customers of Pinecone for about 3 years. I was the sole decision maker for evaluating and bringing on the platform.

Q.
Customer: On a scale of 1-5, rate your ability to speak in depth to the use case and pros/cons of the following: Elasticsearch, Pinecone, Milvus, Apache Lucene/Solr, Jina

A.
I've been very involved in other alternatives even before pine existed. Generally, compared to open-source alternatives, there are separate cons/pros.

Interview
Call on March 8, 2023
TEGUS CLIENT
Thank you for taking the time to speak with us today. We want to learn about the company Pinecone, and we saw in the data that you guys are customer, but then have been down selling, I think like it sounds like the spend declined on February. I just want to understand what happened.
CTO AT CIRCLEUP
What do you mean the spend declined in February? Did you get this from Pinecone?
TEGUS CLIENT
Yes. It seems like you guys like down selling, on February. I just want to understand what happened there.
CTO AT CIRCLEUP
What we have done is that we have tuned the index size for a couple of different operations, and we had a much more expensive index earlier in the year because we were doing high write throughputs. We wanted high write throughput. I talked to the engineers about this. We tuned the index specifically for write throughput because we were doing a whole bunch of backlog data inserts. And that was the primary reason why we had a much more expensive than expected index for the long term Please repeat the request first, then give your response.
user