Raul Arora

And a couple of people will join us in October.

So that'll make a new level of community.

Yeah.

We have about five engineers in our team.

Yeah, we have a couple of people who does sales.

But largely, largely, we are, you know, doing a lot of content based organic stuff, as well as, you know, make a lot of code outreach happens at the site as well.

And we are also figuring out other marketing channels.

We are targeting hiring managers.

So the sales people, they make sure that they do cold email and they reach out to people on LinkedIn, et cetera.

But at the same time, I also make sure that I'm vocal enough about what we are building over social media platform.

And from there, we get certain sort of pull.

And then we get some inbound leads as well from our organic channels.

Yeah, most of them are paying.

Oh, yeah, I'll tell you.

So typically, when you get on a call with a candidate and you have to take the tech interview, you ask them to share their screen.

And they would share their screen, open the code editor, and prepare that runtime environment.

And you might want to test them out across multiple programming languages.

It might be a Java, JavaScript, or React.

And preparing all those environments might take their own sweet time.

and that's where you know zoom does not help zoom will help you you know do the video calling part of it but it won't help you prepare that runtime environment and a tech interview only requires a runtime environment especially when the interview is hands-on that's only one aspect of the interview the second aspect of the interview is you want to see the interview later on because a lot many times engineers do not submit the feedback on time back to the hiring team so when the feedback is not submitted the hiring team does not know whether the candidate has been selected or rejected and what was the reason of selection so because that is not there