Matt Cowell
👤 PersonAppearances Over Time
Podcast Appearances
And they wanted to spin it out as a separate company, raise money. and sort of have its own future. And that's really how QuantHub got its start. I came on to run it as a separate company. It was sort of day one for the company. We didn't have any customers. We had kind of a proof of concept for the product. Didn't have any marketing. It was kind of early, early days.
But that's how we got our start. They were doing this internally to help in their own hiring. Kind of realized that hiring is difficult. You spend a lot of time. It's relatively error prone in this field. And so they started tuning their hiring process by using assessments. And then that's what we took on as a business.
But that's how we got our start. They were doing this internally to help in their own hiring. Kind of realized that hiring is difficult. You spend a lot of time. It's relatively error prone in this field. And so they started tuning their hiring process by using assessments. And then that's what we took on as a business.
But that's how we got our start. They were doing this internally to help in their own hiring. Kind of realized that hiring is difficult. You spend a lot of time. It's relatively error prone in this field. And so they started tuning their hiring process by using assessments. And then that's what we took on as a business.
The initial product was PHP Laravel. In terms of how long it took, when I got here, we had sort of a fledgling product. So our product is two things. It's software, of course, but then it's also content. So in particular, it's assessment content. So we have to write assessment questions across a platform.
The initial product was PHP Laravel. In terms of how long it took, when I got here, we had sort of a fledgling product. So our product is two things. It's software, of course, but then it's also content. So in particular, it's assessment content. So we have to write assessment questions across a platform.
The initial product was PHP Laravel. In terms of how long it took, when I got here, we had sort of a fledgling product. So our product is two things. It's software, of course, but then it's also content. So in particular, it's assessment content. So we have to write assessment questions across a platform.
range of technologies that do a good job of determining whether a person knows that skill or not. And so there are really sort of two aspects for us building the software and then actually generating all the content, making sure the content is good, going through QA review, making sure that it's not plagiarized and it's not just literally pulled off the internet and
range of technologies that do a good job of determining whether a person knows that skill or not. And so there are really sort of two aspects for us building the software and then actually generating all the content, making sure the content is good, going through QA review, making sure that it's not plagiarized and it's not just literally pulled off the internet and
range of technologies that do a good job of determining whether a person knows that skill or not. And so there are really sort of two aspects for us building the software and then actually generating all the content, making sure the content is good, going through QA review, making sure that it's not plagiarized and it's not just literally pulled off the internet and
And so from a product perspective, we had kind of the beginnings of a product when I first started on sort of day one. It probably took us about three or four months to get something that we were ready for a customer to use. And then in that same amount of time, we were building that content library.
And so from a product perspective, we had kind of the beginnings of a product when I first started on sort of day one. It probably took us about three or four months to get something that we were ready for a customer to use. And then in that same amount of time, we were building that content library.
And so from a product perspective, we had kind of the beginnings of a product when I first started on sort of day one. It probably took us about three or four months to get something that we were ready for a customer to use. And then in that same amount of time, we were building that content library.
So probably about three or four months before we were doing some beta type work with an early adopter.
So probably about three or four months before we were doing some beta type work with an early adopter.
So probably about three or four months before we were doing some beta type work with an early adopter.
There are several features, I would say, that people talk about a lot in our market. And, you know, just frankly, we had to do without those early on. So an example of that would be, you know, we were testing or we are assessing coding skills, but also more kind of foundational skills like statistics and mathematics and machine learning algorithms and, you know, these types of things.
There are several features, I would say, that people talk about a lot in our market. And, you know, just frankly, we had to do without those early on. So an example of that would be, you know, we were testing or we are assessing coding skills, but also more kind of foundational skills like statistics and mathematics and machine learning algorithms and, you know, these types of things.
There are several features, I would say, that people talk about a lot in our market. And, you know, just frankly, we had to do without those early on. So an example of that would be, you know, we were testing or we are assessing coding skills, but also more kind of foundational skills like statistics and mathematics and machine learning algorithms and, you know, these types of things.
And so early on, We had to make a decision whether we wanted to spend a lot of time and actually allow people to build, in essence, a code editor where we could assess coding skills in the browser. And It didn't make sense to spend a lot of time doing that until we were starting to get more feedback from customers. We had people using the product and testing statistics and other things like that.