Basically I run all technology for Okta. That means that from a service perspective, the people that are writing the code, so basically all of the developers, and the technical operations team, meaning the team that is keeping the servers running and deploying the new system, and monitoring and keeping them secure. So all of that and I also handle the internal corporate IT, which is basically the systems that power Okta as a business.
So that's my scope. Been with the company for about seven years and obviously the role has changed quite a bit. When I joined the company, it was all kind of an idea of really trying to build cloud first, multi-tenant, identity management product delivered as a service. But the team was very, very small. And frankly, the scale was a completely different place than where it is right now. And I think that's one of the things that has changed my job quite a bit, because it's not the same thing if you're dealing with a system that scales through, I don't know, a thousand users, versus a system that scales through 10,000 users. That alone is very different.
Now, if you fast forward seven years and make a system that scales to hundreds of millions of users, it's a completely different ball game. Now, the architecture has evolved over time. We have taken account of the good things that we were doing 10 years ago and made them better, but also we have learned to adopt new technologies to really deal with the scale that we have right. I don't think eight years ago, dealing with something like Albertsons, MLB, Major League Baseball, was impossible with the architecture that we had at that point. But now we're basically looking into even bigger scalability requirements now.