Joni Klippert

And then we fill in all the stuff that you have to fill in, right? Like customer requests or hardening of our systems. But that's generally how we build a roadmap.

And then we fill in all the stuff that you have to fill in, right? Like customer requests or hardening of our systems. But that's generally how we build a roadmap.

Early on when we were building out our technical team, I looked for experience. I just felt like this is a really interesting problem to solve. I think it's important to solve it. I'm going to hire engineers who have several startups under their belt of building SaaS, building authentication and multi-tenant SaaS, like building like the core pieces and a really scalable infrastructure.

Early on when we were building out our technical team, I looked for experience. I just felt like this is a really interesting problem to solve. I think it's important to solve it. I'm going to hire engineers who have several startups under their belt of building SaaS, building authentication and multi-tenant SaaS, like building like the core pieces and a really scalable infrastructure.

Early on when we were building out our technical team, I looked for experience. I just felt like this is a really interesting problem to solve. I think it's important to solve it. I'm going to hire engineers who have several startups under their belt of building SaaS, building authentication and multi-tenant SaaS, like building like the core pieces and a really scalable infrastructure.

Because the death knell is you hire inexperienced engineers to get an MVP off. And the second you start to get traction in your business, you have to rewrite your code base. That was not going to happen. I picked up really awesome folks that I had met in the Boulder community or had known that I knew would help tee up this platform for success.

Because the death knell is you hire inexperienced engineers to get an MVP off. And the second you start to get traction in your business, you have to rewrite your code base. That was not going to happen. I picked up really awesome folks that I had met in the Boulder community or had known that I knew would help tee up this platform for success.

Because the death knell is you hire inexperienced engineers to get an MVP off. And the second you start to get traction in your business, you have to rewrite your code base. That was not going to happen. I picked up really awesome folks that I had met in the Boulder community or had known that I knew would help tee up this platform for success.

And then as we expanded outside of engineering, the value that I look for the most is I want to hire people that feel an inappropriate amount of responsibility for their title, for the success of this company. I want them to care so much that they really think about the whole business and everything that they're doing day to make sure we are in a position to succeed and to win.

And then as we expanded outside of engineering, the value that I look for the most is I want to hire people that feel an inappropriate amount of responsibility for their title, for the success of this company. I want them to care so much that they really think about the whole business and everything that they're doing day to make sure we are in a position to succeed and to win.

And then as we expanded outside of engineering, the value that I look for the most is I want to hire people that feel an inappropriate amount of responsibility for their title, for the success of this company. I want them to care so much that they really think about the whole business and everything that they're doing day to make sure we are in a position to succeed and to win.

Sense of responsibility. Now, this is my job and I do this one job. I'll do anything it takes to help make StackHawk successful. And we've really tried to continue to find people with that. It can be hard as you scale, right? And you do start to hire people more specific type employees than generalists.

Sense of responsibility. Now, this is my job and I do this one job. I'll do anything it takes to help make StackHawk successful. And we've really tried to continue to find people with that. It can be hard as you scale, right? And you do start to hire people more specific type employees than generalists.

Sense of responsibility. Now, this is my job and I do this one job. I'll do anything it takes to help make StackHawk successful. And we've really tried to continue to find people with that. It can be hard as you scale, right? And you do start to hire people more specific type employees than generalists.

But that fire in the belly and that level of responsibility is something we really try to screen for.

But that fire in the belly and that level of responsibility is something we really try to screen for.

But that fire in the belly and that level of responsibility is something we really try to screen for.

I think part of hiring really seasoned engineers have kept us out of that problem to date. Early technical decision we made, and I honestly didn't fully understand it as we were making it because I was so used to SaaS-based software, is we decided the deployment mechanism, the scanning capability is deployed in the client site, so via Docker or within your CLI.

I think part of hiring really seasoned engineers have kept us out of that problem to date. Early technical decision we made, and I honestly didn't fully understand it as we were making it because I was so used to SaaS-based software, is we decided the deployment mechanism, the scanning capability is deployed in the client site, so via Docker or within your CLI.

I think part of hiring really seasoned engineers have kept us out of that problem to date. Early technical decision we made, and I honestly didn't fully understand it as we were making it because I was so used to SaaS-based software, is we decided the deployment mechanism, the scanning capability is deployed in the client site, so via Docker or within your CLI.