Meeting Title: Recruitment: Rico <> Kaela Date: 2026-02-23 Meeting participants: Rico Rejoso, Kaela Gallagher
WEBVTT
1 00:01:14.320 ⇒ 00:01:16.569 Kaela Gallagher: Hey Rico, can you hear me okay?
2 00:01:16.990 ⇒ 00:01:18.899 Rico Rejoso: Yep. Hey, Kayla. How are you?
3 00:01:19.290 ⇒ 00:01:21.779 Kaela Gallagher: Good, how are you? Good morning.
4 00:01:21.790 ⇒ 00:01:29.419 Rico Rejoso: Good, good. Yeah, I’m sorry I wasn’t able to turn on my camera, and for the voice, just had a dental surgery last week, this weekend.
5 00:01:29.790 ⇒ 00:01:32.380 Kaela Gallagher: Oh my gosh, how are you recovering?
6 00:01:33.110 ⇒ 00:01:36.429 Rico Rejoso: Good, doesn’t hurt, but the swelling is still there.
7 00:01:36.900 ⇒ 00:01:41.249 Kaela Gallagher: Oh my gosh, I’m so sorry to hear that, wow, that’s crazy!
8 00:01:41.700 ⇒ 00:01:43.809 Rico Rejoso: Yeah, it was unexpected, but…
9 00:01:44.490 ⇒ 00:01:46.820 Rico Rejoso: I mean, I can still work.
10 00:01:46.980 ⇒ 00:02:03.060 Kaela Gallagher: Okay, okay. Well, I appreciate you taking some time for me while you’re under the weather, especially. But yeah, excited to kind of get onboarded and learn more about your processes and, the team.
11 00:02:03.650 ⇒ 00:02:05.510 Rico Rejoso: Definitely. Yeah,
12 00:02:05.530 ⇒ 00:02:17.779 Rico Rejoso: So, just a few things before we can start. Let me just introduce myself. I’m Rico, I’m from the operations. I’m also handling the hiring and recruitment for the meantime, until you get onboarded and ramped up.
13 00:02:17.780 ⇒ 00:02:32.520 Rico Rejoso: So for today, I will just be presenting you the onboarding and the flow of hiring and recruitment. We’ll have a further discussion about this one later on with, along with Utam, who handles recruitment before I did.
14 00:02:32.790 ⇒ 00:02:36.360 Rico Rejoso: Which is also the CEO and owner of the company, right? So…
15 00:02:36.360 ⇒ 00:02:36.980 Kaela Gallagher: Yeah.
16 00:02:36.980 ⇒ 00:02:43.170 Rico Rejoso: Giving you a quick intro on what we’re doing and what we’re handling for now, and, you know, we can try to…
17 00:02:43.420 ⇒ 00:02:53.690 Rico Rejoso: Discuss further about your ideas and how you wanted to implement such… or what, how do you want some processes to be implemented, based off your experience and your suggestions, okay?
18 00:02:54.280 ⇒ 00:02:55.930 Kaela Gallagher: Perfect. Awesome.
19 00:02:55.930 ⇒ 00:02:57.960 Rico Rejoso: Okay, let me just share my screen real quick.
20 00:03:01.170 ⇒ 00:03:14.820 Rico Rejoso: Okay, so this is a bit different than what we do during onboarding with other team members, but for the sake of it, I’m also gonna go through the onboarding process. So again, welcome to Brainforge, and the purpose of this orientation is to
21 00:03:15.350 ⇒ 00:03:26.360 Rico Rejoso: introduce you to Brainforged vision, culture, and values, and to help you better understand what the company does, what it offers, and, what we’re serving, or what we’re doing for our clients.
22 00:03:27.580 ⇒ 00:03:39.349 Rico Rejoso: Now, for our mission, we help businesses turn chaos into clarity using data and AI to drive faster and smarter decisions. We envision that everybody eats, we operate like giants, and we give back and pay forward.
23 00:03:39.500 ⇒ 00:03:46.139 Rico Rejoso: So before I proceed, may I know how, I mean, how did you learn about Brainforge?
24 00:03:46.750 ⇒ 00:04:00.550 Kaela Gallagher: Yeah, I actually, know Robert. We did the same, like, program in college, so I had, like, recently reconnected with him, and he told me… told me more about what you guys do, so… yeah.
25 00:04:01.680 ⇒ 00:04:02.240 Rico Rejoso: Great.
26 00:04:02.400 ⇒ 00:04:04.029 Rico Rejoso: And actually,
27 00:04:04.680 ⇒ 00:04:18.769 Rico Rejoso: I kind of tracked your, I mean, when I was organizing the hiring and recruitment pipeline, like, a month ago, I also noticed that you were first, the role that you applied first was the, project manager, right?
28 00:04:20.049 ⇒ 00:04:31.949 Kaela Gallagher: That is kind of what was first, suggested to me, yes. And then, we kind of readjusted, and they presented, like, the recruiting side.
29 00:04:32.510 ⇒ 00:04:35.150 Rico Rejoso: Yep, definitely, we need help on this.
30 00:04:36.110 ⇒ 00:04:37.569 Rico Rejoso: That’s a risk stream, yeah.
31 00:04:37.600 ⇒ 00:04:48.930 Rico Rejoso: So, yeah, again, great to have you here. So, moving forward, what we do, what we… our services that we offer are data platform and analytics, data automation and co-pilots, and training and enablement.
32 00:04:48.930 ⇒ 00:05:01.240 Rico Rejoso: As of now, this is the current services that we are offering. Not sure if we’re gonna revamp this, but again, companies looking to further expand, so we’re looking to add more services that we can offer to our clients. But take note of the current services that we are offering.
33 00:05:01.570 ⇒ 00:05:02.500 Kaela Gallagher: Perfect.
34 00:05:02.500 ⇒ 00:05:04.480 Rico Rejoso: Alright, who we serve,
35 00:05:04.730 ⇒ 00:05:18.879 Rico Rejoso: Sorry, we target, C-suites, VPs, directors, or heads, founders, and division leaders. The industries that we mostly work with are e-commerce, CPGs, and business-to-business, and software as a service.
36 00:05:18.930 ⇒ 00:05:29.379 Rico Rejoso: This is as of 2025, but right now, again, we’re looking to further expand, so we’re targeting furthermore into insurances or financial, financial institutions. So, yeah.
37 00:05:30.630 ⇒ 00:05:31.240 Kaela Gallagher: Awesome.
38 00:05:31.240 ⇒ 00:05:35.619 Rico Rejoso: Great that you’ll be a part of that, further expansion and growth of Brainforge.
39 00:05:36.410 ⇒ 00:05:38.339 Rico Rejoso: Okay, we can skip this…
40 00:05:38.940 ⇒ 00:05:48.049 Rico Rejoso: And the tools that you’ll be using. So these are the tools that we’ve onboarded you with, which is Slack, Notion, Clockify, Linear, 1Password, RAMP,
41 00:05:48.190 ⇒ 00:05:54.340 Rico Rejoso: ChatGPT, the Forge, or the BrainForge platform, and our automation tools.
42 00:05:54.600 ⇒ 00:06:00.180 Rico Rejoso: This is outdated, but we are also using tools Code default.
43 00:06:00.890 ⇒ 00:06:11.629 Rico Rejoso: Which is, I mean, a primary tool that we’re using in recruitment for, notification and for booking or appointments, with our interviewers.
44 00:06:12.820 ⇒ 00:06:17.250 Rico Rejoso: Okay, so to discuss it further, we’ll… I mean, we’ll discuss that further later on.
45 00:06:19.550 ⇒ 00:06:36.979 Rico Rejoso: Now, for our payments, payment schedule, we offer a net 30 payment schedule. I believe you are, if there are changes on your contract, or let’s say adjustments that was suggested prior to you signing it, there should be, it should be on your contract, but for most cases.
46 00:06:36.980 ⇒ 00:06:45.420 Rico Rejoso: Most team members are offered a net 30 payment schedule. Means that full payment for an invoice is due 30 days after the end of the month. This is the…
47 00:06:45.440 ⇒ 00:06:52.770 Rico Rejoso: first option that we have, but again, it depends case to case. There are some member… some team members that are,
48 00:06:52.820 ⇒ 00:06:59.890 Rico Rejoso: That are offered a different payment schedule, but again, that is upon discussion with our, executives, okay?
49 00:07:00.750 ⇒ 00:07:01.450 Kaela Gallagher: Okay.
50 00:07:02.250 ⇒ 00:07:07.359 Rico Rejoso: Alright, so regarding tools, what we have here is Flockify, okay?
51 00:07:08.100 ⇒ 00:07:11.810 Rico Rejoso: So, Clockify is our time tracking tool, so we don’t necessarily…
52 00:07:11.820 ⇒ 00:07:27.810 Rico Rejoso: track every hour, every minute that you’re spending to work with Brainforce, but what we’re doing is to make sure that all the hours that you work with Brainforce are in Clockify, whether you put it, whether you do… I mean, there are 3 options on how you can record your, hours in Clockify. You could just input it on a timesheet.
53 00:07:27.810 ⇒ 00:07:36.090 Rico Rejoso: Or you can track it by clicking on Start, pause, or, once you’re done, you can just
54 00:07:36.520 ⇒ 00:07:41.540 Rico Rejoso: end the recording, or you can use your calendar to track your hours on DocuFi.
55 00:07:42.290 ⇒ 00:07:57.820 Rico Rejoso: I’ll show it to you, since this is one of the most important tools that we have, and make sure that, and want to make sure that all team members incoming will use Clockify efficiently, and all of their hours are in Clockify, every day of every week, okay?
56 00:07:57.980 ⇒ 00:07:59.700 Rico Rejoso: So, just a few reminders.
57 00:07:59.700 ⇒ 00:08:21.849 Rico Rejoso: when using Clockify, make sure to record your hours daily and accurately. Don’t create your own project, okay? If you’re working on other projects, this goes for, other engineers that are working on multiple projects or multiple clients. We create one project per client, or depending on the work stream that we have per client, and we want to make sure that they are added onto it.
58 00:08:21.950 ⇒ 00:08:39.229 Rico Rejoso: The operations team take care of adding them into those projects that they’re assigned to, but let’s also make sure that during our onboarding, we also inform our team members not to create their own project and just inform the operations team, and we can help them out in regards to that, okay?
59 00:08:39.830 ⇒ 00:08:40.559 Kaela Gallagher: Okay.
60 00:08:41.419 ⇒ 00:08:46.939 Rico Rejoso: Alright, so, as I mentioned, I’m also gonna show you… Clockify works.
61 00:08:47.889 ⇒ 00:09:05.619 Rico Rejoso: So yeah, there are 3 ways of putting in your hours in Clockify. First is the timesheet, which is used by most people in the company, wherein you just have to put in the hours that you’ve worked on, you just have to select a project, let’s say for, now, let’s say you’re working for… on hiring and recruitment, right?
62 00:09:05.859 ⇒ 00:09:24.589 Rico Rejoso: for hiring, you just have to put in the hours that you spent working on this, and since you’re working most of your hours on hiring and recruitment, just put in 8 hours, let’s say, for today, but if you are working on a different project, per se, GTM or consulting or the operations, you just have to select that project and put in your hours that you spent, okay?
63 00:09:24.659 ⇒ 00:09:27.470 Rico Rejoso: So it is supported… Yes, go ahead.
64 00:09:27.470 ⇒ 00:09:36.580 Kaela Gallagher: Sorry, really quickly, I am, like, I have my own Clockify pulled up here, just to kind of follow along with you, and I,
65 00:09:36.910 ⇒ 00:09:44.159 Kaela Gallagher: I don’t see hiring as an option. Can I… can I maybe share my screen with you and show… show you?
66 00:09:44.190 ⇒ 00:09:45.539 Rico Rejoso: Sure, definitely, yeah.
67 00:09:45.720 ⇒ 00:09:46.340 Kaela Gallagher: Okay.
68 00:09:47.650 ⇒ 00:09:54.300 Kaela Gallagher: Let’s see… Okay.
69 00:09:55.050 ⇒ 00:09:56.930 Kaela Gallagher: Can you see my clock of eye?
70 00:09:57.190 ⇒ 00:09:57.730 Rico Rejoso: Yep.
71 00:09:57.970 ⇒ 00:10:01.839 Kaela Gallagher: Okay, perfect. Yeah, when I click Select Project… Oh!
72 00:10:02.000 ⇒ 00:10:10.150 Kaela Gallagher: Here it is. Okay, perfect. And then, so if I was doing, like, one-on-ones, I guess.
73 00:10:11.210 ⇒ 00:10:12.599 Kaela Gallagher: Or 1 and 1?
74 00:10:13.000 ⇒ 00:10:14.750 Kaela Gallagher: boarding, I would click here.
75 00:10:15.000 ⇒ 00:10:15.590 Rico Rejoso: Yep.
76 00:10:16.040 ⇒ 00:10:16.820 Kaela Gallagher: Okay.
77 00:10:17.250 ⇒ 00:10:21.180 Rico Rejoso: That is for company-wide meeting and one-on-one with other team members.
78 00:10:21.480 ⇒ 00:10:31.210 Kaela Gallagher: Okay, so for example, on Fridays, we have, like, a company-wide meeting, right? So, would I be clocking that under this category?
79 00:10:31.350 ⇒ 00:10:32.020 Rico Rejoso: Yep, but…
80 00:10:33.100 ⇒ 00:10:33.870 Kaela Gallagher: Okay.
81 00:10:34.440 ⇒ 00:10:36.580 Kaela Gallagher: Okay, got it, thank you.
82 00:10:37.060 ⇒ 00:10:37.920 Rico Rejoso: No worries.
83 00:10:38.520 ⇒ 00:10:40.540 Rico Rejoso: Let me share my screen again.
84 00:10:44.480 ⇒ 00:10:51.659 Rico Rejoso: Alright, so, yeah, that’s for Clockify. Other… Other ways of…
85 00:10:52.010 ⇒ 00:11:10.969 Rico Rejoso: logging your hours in Clockify is using the time tracker. We suggest this for engineers who don’t have time to manually record their time on Clockify. They could just select the project and start recording the time, especially if they’re focused on just one project, let’s say, for the next two hours. They can use this. This is more efficient for them, since, they tend to not
86 00:11:11.330 ⇒ 00:11:18.229 Rico Rejoso: Remember, the hours they spend exactly working on one project, especially if they’re working on multiple ones.
87 00:11:18.230 ⇒ 00:11:31.520 Rico Rejoso: So we suggest them using this, and another way is using your calendar. So you just have to link your calendar here in Clockify. It shows up all your meetings, so if in case, like, let’s say you’re working for one work, or for hiring and recruitment for, like.
88 00:11:31.540 ⇒ 00:11:32.670 Rico Rejoso: From 1…
89 00:11:33.850 ⇒ 00:11:42.090 Rico Rejoso: 2, 3 in the afternoon. You just have… you can just, add an event on your calendar. It shows up here, and you can just
90 00:11:42.280 ⇒ 00:11:43.519 Rico Rejoso: Click it here.
91 00:11:43.950 ⇒ 00:11:47.919 Rico Rejoso: And submit a, select a project and add it to your timesheet.
92 00:11:48.700 ⇒ 00:11:49.460 Kaela Gallagher: Okay.
93 00:11:51.520 ⇒ 00:11:54.860 Rico Rejoso: So that’s it for Clockify. Next one…
94 00:11:56.240 ⇒ 00:12:09.450 Rico Rejoso: Yeah, follow Brainforge on LinkedIn, keep company info updated on LinkedIn. If needed, we can provide the LinkedIn header, just, you can make a request on the marketing team, or if you’re not part of the channel yet, let me know and I can add you to it.
95 00:12:10.030 ⇒ 00:12:24.110 Rico Rejoso: So, there are times that the hiring and recruitment team are also working hand-in-hand with the marketing team for job ads and, for promoting the business. So, I might as well need to add you on that channel, after this meeting, okay?
96 00:12:24.420 ⇒ 00:12:25.270 Kaela Gallagher: Okay.
97 00:12:25.510 ⇒ 00:12:40.899 Rico Rejoso: Yep, instead of Friday team meetings, we have a Friday… we have Friday meetings, or retro, every two weeks, so make sure that you have your camera on. The meeting structure is very simple. Every, every time we had this meeting, we will be assigning a host.
98 00:12:40.900 ⇒ 00:12:54.810 Rico Rejoso: And they will do a quick icebreaker, a lab share. A lab share is sharing anything that you want to share with your team. It may be work-related, personally, some personal stuff that you want to share with the team, anything that you want to share, okay?
99 00:12:54.820 ⇒ 00:12:56.939 Rico Rejoso: And that is for these 9 posts to do so.
100 00:12:57.020 ⇒ 00:13:14.710 Rico Rejoso: Afterwards, we have the department updates. So, currently, the department updates that we have are for executives to update on the team, marketing, or the GTM team, operations, we have the recruitment, updating the team of our hiring process, and, like, since, like.
101 00:13:14.960 ⇒ 00:13:25.119 Rico Rejoso: 40% of the team are also conducting the interview, the interviews. We also update them of those individuals that are on second round or are on final rounds, okay?
102 00:13:25.250 ⇒ 00:13:36.640 Rico Rejoso: And you can also see the, or let’s say view the recent BrainForge retro that we have on the Forge platform, which we’ll further introduce you with later on, okay?
103 00:13:37.400 ⇒ 00:13:38.150 Kaela Gallagher: Okay.
104 00:13:38.150 ⇒ 00:13:45.079 Rico Rejoso: Alright. Before we proceed to the discussion, just confirming, do you have any questions so far?
105 00:13:46.200 ⇒ 00:13:52.240 Kaela Gallagher: Let’s see… I think I am all…
106 00:13:52.860 ⇒ 00:14:02.239 Kaela Gallagher: good for now. I have access to Notion and ChatGPT, and I’ll have some questions for you at the end, but for now, I’m okay.
107 00:14:02.420 ⇒ 00:14:17.480 Rico Rejoso: Okay, got you. Yep, so yeah, please confirm access for the following tools that we’ll be discussing. Notion, using… we use this for documentation. I’ll also share you our hiring and recruitment Notion page, but it’s also on our main page in, Notion.
108 00:14:17.480 ⇒ 00:14:17.910 Kaela Gallagher: Check it out.
109 00:14:17.910 ⇒ 00:14:26.809 Rico Rejoso: you can further explore Notion as well, and let us know if you have any questions or clarification, and especially suggestions on pages that you are working on, okay?
110 00:14:27.880 ⇒ 00:14:28.640 Kaela Gallagher: Okay.
111 00:14:28.640 ⇒ 00:14:35.979 Rico Rejoso: ChatGPT, we have this, we can invite you to it, but right now, most of the team, most of the team members are also using, cursor.
112 00:14:36.310 ⇒ 00:14:44.150 Rico Rejoso: So, I believe I added or sent an invite for cursor. If you haven’t got any access to it yet, let me know and I can provide it to you, okay?
113 00:14:44.670 ⇒ 00:14:56.830 Kaela Gallagher: Yes, I… I did log into ChatGPT with my Brainforge email, and then, I logged into Cursor as well, although I have no idea how to use it yet.
114 00:14:57.790 ⇒ 00:15:02.550 Rico Rejoso: Same thing, I just, you know, had the whole onboarding cursor stuff in GitHub.
115 00:15:02.770 ⇒ 00:15:07.080 Rico Rejoso: of last week, so I’m not that well, you know.
116 00:15:07.460 ⇒ 00:15:18.640 Rico Rejoso: educated yet with Cursor, but yeah, I can refer you to team members that can help you wrap up with Cursor. Okay. The simple framework is that we have everything, I mean, all in GitHub.
117 00:15:18.790 ⇒ 00:15:29.970 Rico Rejoso: On those, repo, and we just use Cursor to, you know, take a look at all those notes that we have in GitHub, and it’s a mix of, like, you know, document
118 00:15:30.310 ⇒ 00:15:34.779 Rico Rejoso: what do you call this? Documentation, reading at the same time.
119 00:15:35.060 ⇒ 00:15:36.520 Rico Rejoso: AI generating.
120 00:15:36.630 ⇒ 00:15:48.500 Rico Rejoso: But I think it’s better that you explore it yourself, and if ever you have problems, or let’s say, questions on how to use it, just let us know, and I can refer you to a person or a team member that can help you out with… when it comes to ramping up with Chrysler, okay?
121 00:15:49.020 ⇒ 00:15:49.830 Kaela Gallagher: Perfect.
122 00:15:51.690 ⇒ 00:15:56.160 Rico Rejoso: Alrighty, next one. We have, Slack and Linear.
123 00:15:57.420 ⇒ 00:16:08.830 Rico Rejoso: Slack basically is our, main communication channel. You can use it to, converse with anyone on the team, and if you are not added to a specific channel, or let’s say,
124 00:16:08.950 ⇒ 00:16:19.220 Rico Rejoso: Uthumb or Robert is asking you to be part of this channel, and you haven’t yet, you can also let the operations team know that you need to be on this channel, and we can help you out on this, okay?
125 00:16:19.790 ⇒ 00:16:33.839 Kaela Gallagher: Okay, yeah, I can send you, a screenshot of the channels that I’m in so far. I’m only in a few. I know I definitely need to be added to marketing, but, I might be… I might need to be added to a couple more.
126 00:16:33.970 ⇒ 00:16:52.609 Rico Rejoso: Definitely, yes, I can help you on that, okay? So I just changed this one. Best practices for us is to use the status updates in Slack. We have the Slack etiquette documentation that I shared with you earlier today. Check that out. Let’s make sure to update our status, so if in case that you’re having your lunch, or you’re not
127 00:16:52.770 ⇒ 00:16:54.470 Rico Rejoso: Or you’re out of office.
128 00:16:54.770 ⇒ 00:17:03.539 Rico Rejoso: Every team member will know, and at the same time, we will not be, you know, sending you messages, or bringing you in and out, requesting updates, okay?
129 00:17:04.050 ⇒ 00:17:05.300 Kaela Gallagher: Okay, perfect.
130 00:17:05.300 ⇒ 00:17:18.510 Rico Rejoso: Alright, Linear is our project tracking tool. Basically, everything that we have is on linear. Every work stream or project or task that we’re working is in linear, and how… that’s how we track the progress of it from backlogs up to done or completion.
131 00:17:18.700 ⇒ 00:17:29.870 Rico Rejoso: This is mainly used by our delivery team, but most, I mean, some of the internal team also are using it to track their progress, okay, on the tasks that they’re working on.
132 00:17:30.720 ⇒ 00:17:38.769 Kaela Gallagher: Got it. Yeah, I was able to log in there, and I’m part of the onboarding, the recruiting, the out-of-office, and the operations,
133 00:17:38.890 ⇒ 00:17:44.520 Kaela Gallagher: Groups? I’m curious, what is the difference between linear and operating?
134 00:17:45.770 ⇒ 00:17:47.660 Rico Rejoso: Great question.
135 00:17:47.710 ⇒ 00:18:02.410 Rico Rejoso: Operating is where we track our… it’s where we plan our hours, basically, for the delivery team. Okay, so we allocate hours for each engineer that are working on projects or on client works, and we allocate hours on how
136 00:18:02.410 ⇒ 00:18:09.599 Rico Rejoso: how many hours should they be spending for those projects each week? Okay, linear is where we track just the tasks.
137 00:18:09.750 ⇒ 00:18:14.750 Rico Rejoso: Everything, and everything. And we use it to,
138 00:18:15.280 ⇒ 00:18:24.870 Rico Rejoso: Also, like, check if you are allocated, like, 5 hours on, or let’s say 10 hours for a project and operating on the same project on linear, how many tasks
139 00:18:25.140 ⇒ 00:18:43.829 Rico Rejoso: do you have, right? And if you are meeting that allocated hours, or if you’re over your allocated hours for that, then we can adjust. I know there’s, like, a tool that has all these features, but right now, or as of now, we’re using it separately, with linear and operating. We also have, like, an instant.
140 00:18:43.950 ⇒ 00:18:58.999 Rico Rejoso: tool that we’re using, basically, it’s just a Ganttrak with all the tasks and everything. Right now, we’re using everything separate, separately, but it comes hand-in-hand when it comes to checking and, you know, checking out the projects and work streams that everyone is working on.
141 00:18:59.700 ⇒ 00:19:09.260 Kaela Gallagher: Okay, got it. So, on the recruiting side of things, operating is not something that we’re using for ourselves. Like, we’re not allocating our own hours, basically.
142 00:19:09.380 ⇒ 00:19:13.320 Kaela Gallagher: We would… we would be using linear more often for our tasks.
143 00:19:14.420 ⇒ 00:19:21.510 Rico Rejoso: definitely fall in there, or your, hiring pipeline, which I’ll also share later on, okay?
144 00:19:22.200 ⇒ 00:19:22.780 Kaela Gallagher: Perfect.
145 00:19:23.480 ⇒ 00:19:25.889 Rico Rejoso: Already, one second.
146 00:19:26.220 ⇒ 00:19:28.060 Rico Rejoso: Just reply to this.
147 00:19:28.450 ⇒ 00:19:32.640 Rico Rejoso: Alright, next to… we have the Brainforge platform and Zoom.
148 00:19:32.880 ⇒ 00:19:37.970 Rico Rejoso: So, Brainforge platform is a tool set up by the team.
149 00:19:38.340 ⇒ 00:19:56.460 Rico Rejoso: where we have the recording of all the meetings and highlights. It’s now also being developed as a Zoom summarizer, and has all the notes from the meeting that was completed, for a specific day or week, okay? Just to, you know, show you what the platform looks like, let’s just open it.
150 00:19:58.970 ⇒ 00:20:02.749 Rico Rejoso: As mentioned, it’s a collection of all the recordings or meetings that we had.
151 00:20:02.780 ⇒ 00:20:19.410 Rico Rejoso: For a day or for a week. So you can check it out, you can open one of this. You can see here below, you can get the transcript, the summary of the meeting, you can also, like, generate linear tickets from it. And I also use this to, you know, get notes.
152 00:20:19.420 ⇒ 00:20:24.700 Rico Rejoso: From the interview that was conducted by our team members,
153 00:20:24.850 ⇒ 00:20:39.779 Rico Rejoso: then put it into AI to get the good points, the negative points, and help them get a… I mean, get a note of what was discussed during their interview with our… with a candidate, and, post it on their…
154 00:20:39.920 ⇒ 00:20:42.090 Rico Rejoso: what do you call it? Notion profile.
155 00:20:42.340 ⇒ 00:20:43.020 Rico Rejoso: Okay.
156 00:20:43.740 ⇒ 00:20:44.649 Kaela Gallagher: What is this?
157 00:20:44.650 ⇒ 00:20:46.370 Rico Rejoso: I mean, yeah, go ahead.
158 00:20:46.370 ⇒ 00:20:58.469 Kaela Gallagher: Okay, I just logged into this platform for the first time, so I’m taking a look, but, can you show me, like, how you would navigate to an interview that occurred?
159 00:20:59.340 ⇒ 00:21:05.059 Rico Rejoso: Yep, let’s say I know we have one here in the 20th, and let’s have a wish.
160 00:21:06.060 ⇒ 00:21:10.089 Rico Rejoso: Okay, so this is the interview with Abuish, our engineering lead.
161 00:21:11.130 ⇒ 00:21:16.560 Rico Rejoso: with a candidate Lagani Patel. So…
162 00:21:16.710 ⇒ 00:21:28.940 Rico Rejoso: I usually just go through this, get the transcript, and get, add it to AI, and have AI… I mean, I have a prompt in AI, and it just generates, the notes.
163 00:21:29.180 ⇒ 00:21:38.620 Rico Rejoso: And after… afterwards, I just copy the notes and put in the Notion profile for each lead. So we have, like, a profile for each lead that we have here, our candidates.
164 00:21:38.740 ⇒ 00:21:41.099 Rico Rejoso: Oh, that we have in the… I just added there.
165 00:21:41.650 ⇒ 00:21:42.530 Rico Rejoso: Take care.
166 00:21:45.510 ⇒ 00:21:49.149 Rico Rejoso: Okay, but for platform, I know this is a question, I’m sorry.
167 00:21:49.400 ⇒ 00:21:52.440 Rico Rejoso: For platform, you could just select the date.
168 00:21:52.760 ⇒ 00:22:08.419 Rico Rejoso: of, let’s say, the meeting, let’s say for interviews. Interview conducted is around February 20th. Select the date. You can, further filter it by selecting a participant or the team member in that meeting, then it will show you all the lists of the meetings that
169 00:22:08.640 ⇒ 00:22:10.429 Rico Rejoso: Person has for the day.
170 00:22:10.960 ⇒ 00:22:11.670 Rico Rejoso: Okay?
171 00:22:12.220 ⇒ 00:22:22.159 Kaela Gallagher: Got it. Okay. And then can you go back to Notion? Sorry, I saw you open up really quickly. Okay, so this is the candidate’s page.
172 00:22:22.350 ⇒ 00:22:29.940 Kaela Gallagher: And you… You pasted the notes into this page?
173 00:22:30.280 ⇒ 00:22:36.959 Rico Rejoso: Yeah, what I do is, after I generate the notes from the meeting transcript, I usually add it here.
174 00:22:37.860 ⇒ 00:22:41.529 Rico Rejoso: For, like, guide for…
175 00:22:41.640 ⇒ 00:22:56.970 Rico Rejoso: the team member that conducted the interview, whether… for making the final decision whether the team passed. Because right now, on the recruitment, process that I created, I… we usually have the, interviewer be the decision maker for the, for…
176 00:22:57.110 ⇒ 00:23:04.119 Rico Rejoso: that candidate. Let’s say Awash conducted interview. It is Awish who will be,
177 00:23:04.760 ⇒ 00:23:24.210 Rico Rejoso: making a first pass if we… if this is… if we should continue with this candidate or not. If not, we can… we can move it to not fit and send a denial email with the results of the interview. If it passed, then we will send an email, regarding the next steps, and who’s gonna be the interviewer next.
178 00:23:24.590 ⇒ 00:23:25.360 Rico Rejoso: Okay?
179 00:23:25.610 ⇒ 00:23:26.270 Kaela Gallagher: Got it.
180 00:23:27.320 ⇒ 00:23:34.710 Rico Rejoso: We’re… I mean, we’ll further discuss this after the onboarding, so you can, you can… if you have any questions, you can park it for now, and we’ll come back to it later, okay?
181 00:23:34.710 ⇒ 00:23:35.520 Kaela Gallagher: Perfect.
182 00:23:35.920 ⇒ 00:23:52.140 Rico Rejoso: Alrighty, we’re almost done, to be honest. After the platform, we have Zoom. I know you need this. I think I haven’t set it up yet, because for pro licenses in Zoom, this is usually for the delivery team, or other team members that the,
183 00:23:52.410 ⇒ 00:24:00.790 Rico Rejoso: that our stakeholder, who Tom and Robert, mentioned needed one, but I know perhaps that you will need this one, so I’ll add you to it afterwards, okay?
184 00:24:01.200 ⇒ 00:24:01.890 Kaela Gallagher: Okay.
185 00:24:02.020 ⇒ 00:24:03.220 Rico Rejoso: Just take note of that.
186 00:24:03.930 ⇒ 00:24:04.830 Rico Rejoso: Okay.
187 00:24:05.180 ⇒ 00:24:16.839 Rico Rejoso: So yeah, quick check-in, make sure that you have all access to the core tools listed or discussed a while ago. If you need any department-specific tools, it will be provisioned after the onboarding, and…
188 00:24:17.350 ⇒ 00:24:27.800 Rico Rejoso: For any other tools that you need, or confirmation questions and guidance that you need, you can contact the operations team, and we’ll gladly assist you with anything that you have in mind, okay?
189 00:24:28.490 ⇒ 00:24:36.420 Kaela Gallagher: Okay, perfect. I think the only one I’m missing out of the ones that you mentioned was the calendaring, like, interview scheduling, platform.
190 00:24:38.530 ⇒ 00:24:43.360 Rico Rejoso: That is default and Zoom that I need to provide you access with, okay?
191 00:24:43.630 ⇒ 00:24:44.450 Kaela Gallagher: Perfect.
192 00:24:45.390 ⇒ 00:24:47.400 Rico Rejoso: Alrighty, almost done.
193 00:24:48.940 ⇒ 00:24:57.819 Rico Rejoso: This one, day one, we usually have, like, a check-in for new team members for their day one, after one week, and after 30 days.
194 00:24:57.820 ⇒ 00:25:15.470 Rico Rejoso: Okay? It is to make sure that you are capable, or let’s say that you have everything that you need, set you up for success after your first 30 days here at Brainforge. And if not, we can go back to it and discuss further what you need, and how we can further help you out to ramp up and, you know, become efficient in your hours here at Brainforge, okay?
195 00:25:15.680 ⇒ 00:25:24.090 Rico Rejoso: So I’ll probably set this up, we need one. I mean, I’m gonna set you up a meeting with Utam.
196 00:25:24.470 ⇒ 00:25:27.560 Rico Rejoso: After a week one or month one, okay?
197 00:25:28.440 ⇒ 00:25:29.190 Kaela Gallagher: Okay.
198 00:25:29.370 ⇒ 00:25:30.120 Kaela Gallagher: Alright.
199 00:25:30.820 ⇒ 00:25:38.990 Rico Rejoso: So yeah, feedback matters. We appreciate your feedback for the onboarding process. Let us know how we can improve. We have this feedback form that
200 00:25:39.240 ⇒ 00:25:55.420 Rico Rejoso: Probably should have shared it to you earlier, but yep, I will share it after this meeting, and let us know how we can further improve our onboarding process. Since I think this also will be part… and I mean, this is the end stage for the recruitment, right? So, help us come up with a better plan and how we can, you know.
201 00:25:55.800 ⇒ 00:25:58.909 Rico Rejoso: Make the onboarding process for new team members a success.
202 00:25:59.810 ⇒ 00:26:01.740 Kaela Gallagher: Alrighty, yeah, sounds good.
203 00:26:01.740 ⇒ 00:26:08.989 Rico Rejoso: Alrighty, and as mentioned, reach out with questions anytime, be proactive, ask for help, and enjoy the journey, okay?
204 00:26:09.150 ⇒ 00:26:09.770 Rico Rejoso: Again, welcome.
205 00:26:09.770 ⇒ 00:26:11.070 Kaela Gallagher: That’s the range watch.
206 00:26:11.300 ⇒ 00:26:13.879 Kaela Gallagher: Thank you, thanks for running through that.
207 00:26:14.090 ⇒ 00:26:33.789 Rico Rejoso: Alright, I know we just have, like, 4 minutes left before this meeting ends. I just wanted to show you the hiring and recruitment page that we have in Notion, okay? And feel free to ask questions if you have any. So, I created this recruitment handout for you. I’m not sure if you were able to take a look at it or not yet, but basically, here’s the pipeline that we have.
208 00:26:33.820 ⇒ 00:26:43.820 Rico Rejoso: for, for our recruitment, just want to give you a quick overview in this one. For the intake, we have two ways of getting, candidates.
209 00:26:43.880 ⇒ 00:26:59.350 Rico Rejoso: it’s either through outbound or inbound. Inbound is when the lead is interested, or a candidate is interested to apply, we send out the application form and have them fill it out. After filling it out, they will show up on our pipeline, and that’s
210 00:26:59.450 ⇒ 00:27:14.009 Rico Rejoso: I mean, our stakeholder or our service leads are assigned to screen whether their, Brainforge or their Loom interview or Loom video are a success, and we can proceed with the next process, which is the initial interview.
211 00:27:14.320 ⇒ 00:27:18.869 Rico Rejoso: But yeah, that’s, the first intake. Second will be the outbound applicant.
212 00:27:19.100 ⇒ 00:27:21.700 Rico Rejoso: These are for those individuals that
213 00:27:22.150 ⇒ 00:27:32.959 Rico Rejoso: Robert and Dutam Scouted, and CEAS is a good fit for Brainforge. We usually reach out to them, invited them to apply, and to further… and to further, you know,
214 00:27:33.450 ⇒ 00:27:37.640 Rico Rejoso: get them to be part of Brainforge team, we conduct a Brainforge chat.
215 00:27:37.760 ⇒ 00:27:40.360 Rico Rejoso: Okay, it’s a morph…
216 00:27:40.520 ⇒ 00:27:48.130 Rico Rejoso: informal discussion, or let’s say, a meeting with Robert and Utam, and Robert and Utam will further
217 00:27:48.380 ⇒ 00:28:06.999 Rico Rejoso: discuss, the benefits of being with Brainforge and, you know, the good points of being part of the team. I created a document for the pre-interview conversation, also known as the Brainforge chat. This is for Robert and Uten’s, guidance. You can take a look at it and see if it needs, you know.
218 00:28:07.400 ⇒ 00:28:17.679 Rico Rejoso: if it’s a good process or not. If not, just let us know. You can adjust it freely based on what you think is the best way to conduct this process.
219 00:28:18.850 ⇒ 00:28:19.420 Rico Rejoso: Okay.
220 00:28:19.420 ⇒ 00:28:20.130 Kaela Gallagher: Perfect.
221 00:28:20.130 ⇒ 00:28:24.350 Rico Rejoso: That is the other, intake process for our recruitment.
222 00:28:24.640 ⇒ 00:28:38.309 Rico Rejoso: Right, then it’s the same thing for everyone, whether you’re a BF chat, or an outbound applicant, or inbound applicant. Once you’re good to go, once our service lead or stakeholder says that you’re good, they proceed to the next process.
223 00:28:38.320 ⇒ 00:28:50.310 Rico Rejoso: We have the straight, same pipeline for everyone, which is the initial interview, second interview, and the final presentation, final presentation, which is a panel discussion, with the candidate and a few team members, okay?
224 00:28:50.960 ⇒ 00:28:51.860 Kaela Gallagher: Perfect.
225 00:28:52.670 ⇒ 00:28:54.150 Rico Rejoso: Alright,
226 00:28:55.320 ⇒ 00:29:09.860 Rico Rejoso: It is as what you see it is, so, I think to further, you know, get a hold of the process and everything, I think it’s better to offer you to read off some of the documents here, and, you know, list out all the questions that you have, and let me know.
227 00:29:09.900 ⇒ 00:29:16.789 Rico Rejoso: We can further discuss it on a… I mean, async, or during our meeting with Utam later this afternoon, okay?
228 00:29:17.330 ⇒ 00:29:28.890 Kaela Gallagher: Okay, awesome. I know you might have to hop right now, but would love to maybe schedule just some more one-on-one time
229 00:29:28.890 ⇒ 00:29:42.870 Kaela Gallagher: for us, just so I can get to know, like, a little bit more about you, and, kind of what your day-to-day looks like, what… what are your… well, first of all, like, where are you based, and what do your hours look like?
230 00:29:43.510 ⇒ 00:29:51.740 Rico Rejoso: Yeah, I’m sorry, I wasn’t able to inform you about it. I’m from the Philippines, and I work from 10pm to 6am.
231 00:29:52.600 ⇒ 00:29:54.569 Rico Rejoso: So it’s a night shift for me.
232 00:29:55.180 ⇒ 00:29:56.290 Kaela Gallagher: 10 p.m.
233 00:29:56.700 ⇒ 00:30:05.549 Kaela Gallagher: to 6 a.m, like, Philippine time. Okay, what does that translate to, I guess, Eastern, or, like, in a U.S. time zone?
234 00:30:05.720 ⇒ 00:30:07.730 Rico Rejoso: Yeah, 9 a.m. to 6 p.m.
235 00:30:08.720 ⇒ 00:30:09.180 Kaela Gallagher: No names.
236 00:30:09.340 ⇒ 00:30:11.930 Rico Rejoso: Eastern Time to 6 p.m. Eastern Time, yeah.
237 00:30:12.300 ⇒ 00:30:22.970 Kaela Gallagher: Eastern, okay, okay, cool. Well, yeah, if you have some more availability, like, maybe this, this afternoon, would love to spend some more time together.
238 00:30:23.430 ⇒ 00:30:26.979 Rico Rejoso: Definitely let me know, I’ll probably… I mean, you can check my…
239 00:30:27.160 ⇒ 00:30:37.570 Rico Rejoso: calendar, it’s updated, you can set up, and I’ll let you know if you need to reschedule or not, okay? But if you have questions right now, let me know, I definitely have time to further discuss that.
240 00:30:38.320 ⇒ 00:30:48.980 Kaela Gallagher: Okay, okay, cool. Yeah, I guess while we’re here on this, this Notion page, this section…
241 00:30:49.110 ⇒ 00:30:54.160 Kaela Gallagher: Where… that you’re viewing right now, where we have everybody categorized into buckets.
242 00:30:54.670 ⇒ 00:31:04.419 Kaela Gallagher: What… this BF chat move forward? What does that mean? Does that mean that they’ve already chatted with either Utam or Robert?
243 00:31:04.980 ⇒ 00:31:09.130 Rico Rejoso: Yeah, okay, great question. So, whenever, Let me…
244 00:31:09.910 ⇒ 00:31:24.640 Rico Rejoso: I mean, let me start basically from the start. Okay, yeah. So, as I mentioned, there are two intake, ways, right, or process. First is the DF Chat. So, whenever we scheduled one for DF Chat, we have a booking link in default.
245 00:31:24.810 ⇒ 00:31:33.260 Rico Rejoso: That is, once you schedule one, you will show up here in the BF chat, or if you submitted an application form.
246 00:31:33.870 ⇒ 00:31:46.120 Rico Rejoso: you will show up here a needs loom review, and our stakeholders, or the individual or team member assigned to review them, which are the previous leads, or Thelma Robert, will be reviewing this column here.
247 00:31:46.420 ⇒ 00:31:55.859 Rico Rejoso: if we have, like, anyone that can proceed to the next process, they will be… they will be moved to Loom Review Move Forward. So, move forward means that they
248 00:31:56.370 ⇒ 00:32:00.629 Rico Rejoso: past the previous process, which is loom review or BFChat.
249 00:32:00.810 ⇒ 00:32:06.430 Rico Rejoso: And they’re good to go to schedule to the next round, because I usually move them from one column to another.
250 00:32:06.950 ⇒ 00:32:07.940 Rico Rejoso: Let’s see…
251 00:32:08.330 ⇒ 00:32:25.639 Rico Rejoso: this one, Jonathan Reyna, which is BFChat Move Forward. Meaning to say that the BFChat was a success, he is good to move forward to the next process, which is the first round, but we haven’t sent out a… an email invite yet for the next process, which is the first round interview.
252 00:32:25.660 ⇒ 00:32:29.840 Rico Rejoso: Or they haven’t scheduled one yet. You can see it here on the…
253 00:32:30.430 ⇒ 00:32:43.510 Rico Rejoso: comments that I leave, like, for example, Feb 20, there was an email follow-up for rescheduling. On Feb 17, a candidate was no-show. So, we removed the interview, dates here.
254 00:32:44.460 ⇒ 00:32:48.280 Rico Rejoso: On the properties, and… I sent out a…
255 00:32:48.540 ⇒ 00:33:04.110 Rico Rejoso: an email following up for the rescheduling for Jonathan Reyna. And if he haven’t booked yet, we will not move him, or we will not change the status to first round, but we’re gonna wait for him to respond on the next, I mean.
256 00:33:04.610 ⇒ 00:33:19.620 Rico Rejoso: we will be waiting for him to book a meeting with the next interviewer, which is Awish, and once he is booked, we can… we will be changing the status to first round, okay? So I don’t move them yet to the next column unless they’ve scheduled the meeting yet, so everybody
257 00:33:19.620 ⇒ 00:33:29.519 Rico Rejoso: Who should be on the first round, second round, are those individuals that are good to go, or just waiting for their, scheduled meeting, and they should also have, like, a interview date.
258 00:33:30.990 ⇒ 00:33:34.709 Kaela Gallagher: Okay. Okay, got it. So then clicking on…
259 00:33:35.110 ⇒ 00:33:43.740 Kaela Gallagher: Lagani, they had their first interview on Friday, so at this point, we’re waiting for feedback from the interviewer.
260 00:33:43.800 ⇒ 00:33:44.490 Rico Rejoso: Yep.
261 00:33:44.660 ⇒ 00:33:47.789 Rico Rejoso: So, I haven’t removed them yet, because…
262 00:33:48.250 ⇒ 00:34:01.759 Rico Rejoso: I haven’t come… I mean, I didn’t receive any, you know, news yet about the decisions for the following individuals. I requested, like, updates here on the Recruiting General channel. If you can see here, I requested, like, for elation, let me…
263 00:34:01.800 ⇒ 00:34:10.679 Rico Rejoso: them is, the session for the following folks that they’ve conducted interview with, and I’ll update this after I receive those updates from them.
264 00:34:11.260 ⇒ 00:34:19.970 Kaela Gallagher: Okay, and in the recruiting channel, when you say DE or AE, that’s Data Engineer and AI engineer?
265 00:34:20.500 ⇒ 00:34:23.500 Rico Rejoso: Data engineer and analytics engineer.
266 00:34:23.500 ⇒ 00:34:25.749 Kaela Gallagher: And analytics, okay, got it.
267 00:34:26.400 ⇒ 00:34:27.400 Kaela Gallagher: Okay.
268 00:34:30.880 ⇒ 00:34:38.789 Kaela Gallagher: Cool. Yeah, I’ve been able to take a look at, like, most of the documents, within this, like, hiring and recruitment.
269 00:34:38.940 ⇒ 00:34:44.940 Rico Rejoso: page, since I’ve had access for about a week now.
270 00:34:45.469 ⇒ 00:34:50.940 Kaela Gallagher: I guess I’m curious for you, like, what…
271 00:34:51.060 ⇒ 00:34:56.390 Kaela Gallagher: Role right now are you finding is, like, most difficult for us to hire for?
272 00:34:57.940 ⇒ 00:34:59.250 Rico Rejoso: data engineers.
273 00:34:59.980 ⇒ 00:35:02.239 Kaela Gallagher: And why… why do you think that is?
274 00:35:02.680 ⇒ 00:35:09.459 Rico Rejoso: we have, like… I mean, it’s not… it’s not that it’s hard to look for our candidates for the position, it’s just that…
275 00:35:09.760 ⇒ 00:35:22.769 Rico Rejoso: we get, we have, like, a few already, but they didn’t meet, or didn’t met the expectations, or, you know, the requirements we’re looking for as a data engineer. So, I think that role was open for, like, the past…
276 00:35:23.180 ⇒ 00:35:24.999 Rico Rejoso: 9, 10 months already?
277 00:35:26.270 ⇒ 00:35:28.460 Kaela Gallagher: Oh, wow. Okay. Okay.
278 00:35:28.460 ⇒ 00:35:28.850 Rico Rejoso: We have a.
279 00:35:28.850 ⇒ 00:35:29.370 Kaela Gallagher: Do we…
280 00:35:29.370 ⇒ 00:35:32.630 Rico Rejoso: Was onboarded, but, you know, they’re usually,
281 00:35:33.120 ⇒ 00:35:39.120 Rico Rejoso: There’s the expected learning curve and everything, but they don’t usually last up to, like, 3 months.
282 00:35:39.250 ⇒ 00:35:49.170 Rico Rejoso: So I think the, you know, after 3 months, it’s… that’s where the decision came in, if they could… to continue with, with the team or not, but yeah, I think that’s…
283 00:35:49.370 ⇒ 00:35:51.719 Rico Rejoso: That, I think, is the issue.
284 00:35:52.540 ⇒ 00:35:58.309 Kaela Gallagher: Okay, so we’re having a hard time… like, we’re hiring them, but we’re having a hard time retaining them.
285 00:35:58.790 ⇒ 00:36:04.689 Rico Rejoso: Yeah, or they’re not meeting the expectations that the, you know, the The team has for that.
286 00:36:05.390 ⇒ 00:36:09.559 Kaela Gallagher: Oh, like within the interview process, they’re not meeting expectations?
287 00:36:09.560 ⇒ 00:36:14.310 Rico Rejoso: They’re good within the interview, but upon hiring them, you know, They kind of…
288 00:36:14.500 ⇒ 00:36:20.419 Rico Rejoso: failed to met the expectations of what a DE looks like for… for brain pressure for the DE.
289 00:36:21.270 ⇒ 00:36:30.790 Kaela Gallagher: Okay, interesting. Yeah, we can definitely, like, dig into that a little bit deeper, later. That’s very interesting.
290 00:36:33.520 ⇒ 00:36:48.449 Kaela Gallagher: Rico, I guess just, like, we can definitely talk more business later, and I know we’re gonna meet with Utam as well. But I’m curious for you, like, so you’re from the Philippines, and you’ve lived there your whole life?
291 00:36:48.910 ⇒ 00:36:49.650 Rico Rejoso: Yep.
292 00:36:49.810 ⇒ 00:36:52.680 Kaela Gallagher: Okay, what part of the Philippines are you in?
293 00:36:53.360 ⇒ 00:36:58.379 Rico Rejoso: I mean, near the metro, but it’s still considered as a province in Laguna.
294 00:36:59.440 ⇒ 00:37:06.520 Kaela Gallagher: Laguna, okay. Okay, cool. And, how long have you been with Brainforge now?
295 00:37:06.720 ⇒ 00:37:09.749 Rico Rejoso: I’ve been with Brain Forge for about 8 months already.
296 00:37:09.870 ⇒ 00:37:12.000 Rico Rejoso: Since… June of last year.
297 00:37:12.600 ⇒ 00:37:14.840 Kaela Gallagher: Okay, and how are you liking it?
298 00:37:15.890 ⇒ 00:37:16.990 Rico Rejoso: it was…
299 00:37:17.350 ⇒ 00:37:28.910 Rico Rejoso: you know, the… I mean, everything, it was very interesting, and I learned a lot, working alongside with Tom and Robert. First, I don’t really know what… I mean, I don’t have an idea what AI and data is.
300 00:37:29.560 ⇒ 00:37:48.170 Rico Rejoso: Yeah. It’s, like, it’s an industry that I haven’t really, you know, taken a look at, ever since. I’m more on the BPO side, on, like, BPO, call center stuff, since it’s the famous industry here in the Philippines. But, yeah, taking it on, Ulta gave me the chance to, like, learn
301 00:37:48.280 ⇒ 00:37:53.789 Rico Rejoso: with Brainforge, every week, every month, I learned something new from them, like.
302 00:37:54.230 ⇒ 00:37:58.309 Rico Rejoso: for this month, I just learned how to use Cursor, how to use, you know, set up AI,
303 00:37:59.170 ⇒ 00:38:00.339 Rico Rejoso: EPs and stuff.
304 00:38:00.460 ⇒ 00:38:10.770 Rico Rejoso: So, yeah, for the past 8 months, it’s been life-changing with the processes and with the, you know, new learnings that I’ve learned from the team members and stakeholders.
305 00:38:11.380 ⇒ 00:38:29.400 Kaela Gallagher: That’s awesome. Yeah, I am excited about that as well. My background’s in recruiting, and I have recruited for, like, engineering positions, and so, like, I kind of understand maybe a little bit of the language of, like, data and AI, but
306 00:38:29.400 ⇒ 00:38:43.539 Kaela Gallagher: actually, like, logging into Cursor was a little bit scary, so I understand being, new to the AI side of things, but I’m excited to learn a lot, in this role, and…
307 00:38:43.640 ⇒ 00:38:48.769 Kaela Gallagher: I’m sure I’ll be learning a lot… a lot from you, since you’ve already been doing this for…
308 00:38:48.890 ⇒ 00:38:55.490 Kaela Gallagher: you know, a while, I’m sure I’ll have a lot of questions for you, but… I guess?
309 00:38:55.780 ⇒ 00:38:57.870 Kaela Gallagher: How is the night shift?
310 00:38:59.170 ⇒ 00:39:03.459 Rico Rejoso: Kinda used to it since I’ve been working in this, I mean.
311 00:39:03.670 ⇒ 00:39:07.499 Rico Rejoso: for U.S. team members, U.S. clients for, like, 5 years already.
312 00:39:07.630 ⇒ 00:39:08.189 Rico Rejoso: Please stop.
313 00:39:08.190 ⇒ 00:39:09.040 Kaela Gallagher: Yeah.
314 00:39:09.710 ⇒ 00:39:14.090 Rico Rejoso: My… it’s just, you know, you just have to adjust… you just have to adjust your body clock.
315 00:39:14.720 ⇒ 00:39:15.510 Kaela Gallagher: Right.
316 00:39:15.660 ⇒ 00:39:16.790 Kaela Gallagher: Right, okay.
317 00:39:17.020 ⇒ 00:39:17.760 Rico Rejoso: rest.
318 00:39:19.770 ⇒ 00:39:26.969 Kaela Gallagher: Okay, okay. I guess, is there, like, anything that you…
319 00:39:27.760 ⇒ 00:39:38.369 Kaela Gallagher: want to see, changed at Brainforge, or I guess maybe a part of your role that you… you don’t enjoy, your least favorite part?
320 00:39:39.140 ⇒ 00:39:47.240 Rico Rejoso: No, actually, I… I mean, there’s a lot of, you know, the things that needs to be changed and processed that we need to align to make it more smoother, but…
321 00:39:47.390 ⇒ 00:40:00.650 Rico Rejoso: Yeah, I think it’s an ongoing process for everyone in the team to further refine our processes and stuff. The recruitment process, to be honest, first… I mean, all these changes that you’re looking at right now, we just made these changes in the last month.
322 00:40:01.530 ⇒ 00:40:02.770 Kaela Gallagher: Wow, yeah.
323 00:40:02.770 ⇒ 00:40:10.550 Rico Rejoso: So, so everything, I mean, all the documents here were… I created this for, like, since January of… since… I mean, January of this year.
324 00:40:10.700 ⇒ 00:40:20.750 Rico Rejoso: we had a very messy process when it comes to recruitment. It’s… it was very unstable, to be honest, on my first 6 months. Then, upon the new year.
325 00:40:20.870 ⇒ 00:40:36.219 Rico Rejoso: we decided to change things up and make sure that we, you know, make documentations in regards to the different process that we have. We don’t have, we created the referral policy, we created the SOP, all the templates for sending emails or LinkedIn messages.
326 00:40:36.360 ⇒ 00:40:47.840 Rico Rejoso: We also created that so, you know, everything is uniform and, you know, we don’t stay out of the… you know, we don’t get out of the process, make sure that everyone’s following the same pipeline and stuff.
327 00:40:48.040 ⇒ 00:40:50.489 Rico Rejoso: So, everything’s new here, so…
328 00:40:50.630 ⇒ 00:41:06.290 Rico Rejoso: we really need, you know, your experience as a recruiter before, for engineers to, like, take a look at all the documents that we have, since I don’t have experience in recruitment, to be honest. I just rely on… I was just reading some documents, or let’s say, published notes.
329 00:41:06.370 ⇒ 00:41:11.429 Rico Rejoso: that Uptam recommended, and just come up with an idea on how recruitment should look like.
330 00:41:11.540 ⇒ 00:41:28.290 Rico Rejoso: So, this is just basically based off my learning on how the recruitment side should work, and my experience on the past 5 years. So, if you have, like, you know, some things that you need… that you suggest that we change, or, you know, we refine further, let us know. We can definitely hop on a call with UCOM and
331 00:41:28.380 ⇒ 00:41:31.780 Rico Rejoso: Change things up here that will benefit everyone in the future.
332 00:41:32.270 ⇒ 00:41:35.169 Kaela Gallagher: Okay, awesome. What do you see as, like, the biggest…
333 00:41:35.360 ⇒ 00:41:41.179 Kaela Gallagher: priority for the recruiting side of the house right now? Like, what do you think is, like, the biggest…
334 00:41:41.810 ⇒ 00:41:47.379 Kaela Gallagher: I guess, the most important thing I should dedicate my time to.
335 00:41:48.720 ⇒ 00:41:52.440 Rico Rejoso: I think it’s cleaning up the pipeline,
336 00:41:52.590 ⇒ 00:42:05.269 Rico Rejoso: try to keep it updated as much as possible, but there were, like, some operations tasks that overlapped it, and I could just spend, like, 2 hours working on the recruitment side. Let’s say, for example, here there are staying candidates that we have.
337 00:42:05.840 ⇒ 00:42:16.630 Rico Rejoso: that doesn’t have any date, or any appointment or interviews scheduled yet with the team. So, I tried to follow up with the team. I didn’t get any response, so I haven’t, you know, followed up yet.
338 00:42:16.760 ⇒ 00:42:24.239 Rico Rejoso: For the remainder. We thumb did take a look at it last week, and there were, like, some that were left here, so I don’t know if we should, like.
339 00:42:24.750 ⇒ 00:42:33.910 Rico Rejoso: change the status to lost individuals, since they’ve been here, like, for a month already, and there’s, like, no date on the process. They’re still in first round, right?
340 00:42:35.150 ⇒ 00:42:43.419 Kaela Gallagher: Got it. So these are people that have maybe completed, like, the Loom interview, but then they never put time on calendar for an actual interview with us?
341 00:42:43.670 ⇒ 00:42:56.150 Rico Rejoso: Yeah, or maybe they have put in, or they have conducted, because the automations and everything, the date here, I just created, like, in the last 3 weeks, so these individuals here are way beyond that. They’ve been here.
342 00:42:56.150 ⇒ 00:42:56.960 Kaela Gallagher: Oh…
343 00:42:56.960 ⇒ 00:43:05.029 Rico Rejoso: for the 30 days, so I don’t know if… I’m not sure what the processes should be for them on… or how should we further proceed with this, folks.
344 00:43:05.500 ⇒ 00:43:09.849 Kaela Gallagher: Okay, so we don’t actually have 8 people in first round, so that’s good to know.
345 00:43:12.090 ⇒ 00:43:12.510 Rico Rejoso: I tried.
346 00:43:12.510 ⇒ 00:43:12.850 Kaela Gallagher: Okay.
347 00:43:13.220 ⇒ 00:43:19.559 Rico Rejoso: backtrack everything and put in notes here as much as I can, then confirm with our stakeholder, but due to the.
348 00:43:19.560 ⇒ 00:43:19.940 Kaela Gallagher: Yes.
349 00:43:19.940 ⇒ 00:43:25.590 Rico Rejoso: schedules, they really haven’t come up with… I mean, they haven’t responded to my inquiry yet.
350 00:43:26.870 ⇒ 00:43:28.230 Kaela Gallagher: Okay. Okay.
351 00:43:28.230 ⇒ 00:43:33.329 Rico Rejoso: just us following up with them, like, what should we do with Andrew Peacher, or, like, for Harry’sush?
352 00:43:33.450 ⇒ 00:43:38.759 Rico Rejoso: What should be the next process for this? Should we move on with the interview, or should we follow up with it?
353 00:43:39.760 ⇒ 00:43:41.250 Kaela Gallagher: Okay. Okay.
354 00:43:41.710 ⇒ 00:43:44.380 Kaela Gallagher: That’s good to know.
355 00:43:45.010 ⇒ 00:43:56.750 Kaela Gallagher: Okay, cool. I guess, I’ve been able to take a look at the documentation that you’ve sent me. Between now and our meeting with Utam, is there anything you recommend that I…
356 00:43:56.860 ⇒ 00:43:59.370 Kaela Gallagher: Like, review or prepare?
357 00:44:00.770 ⇒ 00:44:06.999 Rico Rejoso: Yeah, just to get to know what the recruitment process is, the SOP that we have for it, and the interview hiring decision style that we have.
358 00:44:07.180 ⇒ 00:44:16.479 Rico Rejoso: Because… Right now, all the, folks that are doing the interviews, They are also engineers.
359 00:44:16.820 ⇒ 00:44:17.510 Kaela Gallagher: Yes.
360 00:44:17.510 ⇒ 00:44:32.889 Rico Rejoso: still working, externally with clients and stuff, so we don’t want to take up much of their time. We want to make sure that we set up a process that is smooth for them, and they just have to attend it and, you know, do the interview, rate them, then move forward.
361 00:44:33.340 ⇒ 00:44:33.770 Kaela Gallagher: Right.
362 00:44:33.770 ⇒ 00:44:41.720 Rico Rejoso: That kind of smooth process for our engineers, and you know, and the rest of it should be taken care of by us and the hiring and recruitment team, or the operations team.
363 00:44:41.720 ⇒ 00:44:42.300 Kaela Gallagher: Yeah.
364 00:44:42.650 ⇒ 00:44:51.050 Kaela Gallagher: I agree, I definitely want to, you know, treat our interviewers kind of as our clients in a way, of, like.
365 00:44:51.080 ⇒ 00:45:08.189 Kaela Gallagher: making their jobs the easiest we can make it, and making the process, of course, as smooth for the candidate as well. That’s something that I’ve always, like, been super focused on, is kind of the candidate experience side of things, so excited to dive into that part as well.
366 00:45:08.860 ⇒ 00:45:20.250 Rico Rejoso: Yeah, it’s hard because you have to make sure that the experience for the candidate and the team members, you know, are good and smooth for it. And, you know, we don’t experience any hiccups during that process, right?
367 00:45:20.430 ⇒ 00:45:22.140 Kaela Gallagher: Right, right, yeah.
368 00:45:22.140 ⇒ 00:45:28.129 Rico Rejoso: My day-to-day, like, I usually send out a message on the Recruiting General channel.
369 00:45:28.240 ⇒ 00:45:39.800 Rico Rejoso: Updating them about today’s scheduled interview, so they don’t forget, and they can attend, even though it’s on their calendar already, and also asking them for the sessions for the following folks that has finished the interview with them.
370 00:45:39.990 ⇒ 00:45:42.269 Rico Rejoso: And afterwards, you just take care of everything.
371 00:45:43.910 ⇒ 00:45:49.250 Kaela Gallagher: Okay, okay, perfect. Yeah, I’m looking in the recruiting channel now, so I’m seeing, like.
372 00:45:49.640 ⇒ 00:45:58.850 Kaela Gallagher: you asked for feedback on something, and then, Demalad said that they rescheduled, so… is that, like…
373 00:45:59.130 ⇒ 00:46:05.099 Kaela Gallagher: an issue that we’re having where it’s not reflecting on our calendar side of things, I guess?
374 00:46:06.080 ⇒ 00:46:13.119 Rico Rejoso: It is. I just figured it earlier, like what I had mentioned, it’s a work in progress still, so…
375 00:46:13.560 ⇒ 00:46:13.890 Kaela Gallagher: Yeah.
376 00:46:13.890 ⇒ 00:46:20.510 Rico Rejoso: I figured that, you know, whenever a meeting is rescheduled, we didn’t get any notifications for it, so I wasn’t.
377 00:46:20.510 ⇒ 00:46:21.200 Kaela Gallagher: Okay.
378 00:46:21.200 ⇒ 00:46:28.459 Rico Rejoso: on the recruitment weren’t aware that the interview was rescheduled. So I… using default, this is one of the tools that we have. Let me mention it. I will be also…
379 00:46:28.460 ⇒ 00:46:29.110 Kaela Gallagher: Yeah.
380 00:46:29.260 ⇒ 00:46:44.479 Rico Rejoso: access with. I set up a workflow for when a meeting is rescheduled here from the following, booking links that we have. It will also notify us in Slack about the rescheduling event.
381 00:46:46.000 ⇒ 00:46:46.550 Kaela Gallagher: Okay.
382 00:46:46.970 ⇒ 00:46:53.999 Rico Rejoso: workflow that I created, like, for reminder, for cancellation, whenever an interview is canceled, let’s say.
383 00:46:54.120 ⇒ 00:47:00.460 Rico Rejoso: the candidate canceled it or did not attend, will also have a notification in Slap and for rescheduling.
384 00:47:02.180 ⇒ 00:47:04.609 Kaela Gallagher: Perfect. Okay. Okay.
385 00:47:04.860 ⇒ 00:47:16.510 Kaela Gallagher: Cool. How much, like… outbound messaging are you doing right now? Like, are you…
386 00:47:17.190 ⇒ 00:47:30.089 Kaela Gallagher: Are you guys sending any messaging to candidates and, like, running searches on LinkedIn or other platforms, or, are you mostly getting candidates through, like, job postings?
387 00:47:32.530 ⇒ 00:47:41.670 Rico Rejoso: We have one for job posting in LinkedIn, and for other platforms, not sure, because that’s what we’re working with with the marketing team.
388 00:47:41.850 ⇒ 00:47:45.259 Rico Rejoso: To set up those job posts and, you know, a campaign
389 00:47:45.980 ⇒ 00:48:01.910 Rico Rejoso: for recruiting for a specific position, especially if we’re really in demand of, let’s say, data engineers, we usually do outbound, but that is being taken care of by the stakeholders, by Tom and Robert, and what we also want to take off their plate, right?
390 00:48:01.980 ⇒ 00:48:11.639 Rico Rejoso: So, whenever, like, a position opened, we wanted, like, to take the initiative of doing it through Lincoln, but we haven’t come up with a process for it yet.
391 00:48:12.330 ⇒ 00:48:16.699 Kaela Gallagher: Okay, okay. Do you guys have a,
392 00:48:17.600 ⇒ 00:48:24.189 Kaela Gallagher: A list of the positions that we’re currently hiring for, like, our current needs for the team?
393 00:48:24.790 ⇒ 00:48:27.150 Rico Rejoso: Yep, it’s on Brain Forge Careers.
394 00:48:27.570 ⇒ 00:48:30.349 Rico Rejoso: They’re the following positions that are opened.
395 00:48:31.070 ⇒ 00:48:32.760 Rico Rejoso: For hiring.
396 00:48:33.760 ⇒ 00:48:34.660 Rico Rejoso: So I just agreed.
397 00:48:34.660 ⇒ 00:48:35.440 Kaela Gallagher: Okay.
398 00:48:37.300 ⇒ 00:48:53.699 Rico Rejoso: when was it? Yeah, like, in January, third week. So, this should be updated, but if in case, we can, like, confirm, or maybe have a, you know, a monthly cadence to check in if these roles are… and still are… if we still need to fill in these roles or not.
399 00:48:53.760 ⇒ 00:48:58.529 Rico Rejoso: But we usually depend on the… on our stakeholders from
400 00:48:58.620 ⇒ 00:49:02.999 Rico Rejoso: If we should be… we should say open this position for hire… for hiring.
401 00:49:03.730 ⇒ 00:49:06.200 Kaela Gallagher: Yeah, okay. Okay, so these are…
402 00:49:06.570 ⇒ 00:49:07.839 Rico Rejoso: Yeah, go ahead.
403 00:49:08.110 ⇒ 00:49:12.459 Kaela Gallagher: These are probably all still, needs for us right now.
404 00:49:12.460 ⇒ 00:49:13.060 Rico Rejoso: Yep.
405 00:49:13.420 ⇒ 00:49:15.550 Kaela Gallagher: Yeah, okay. Okay.
406 00:49:16.250 ⇒ 00:49:16.940 Kaela Gallagher: Cool.
407 00:49:16.940 ⇒ 00:49:20.240 Rico Rejoso: And also, just to add to this, as,
408 00:49:20.390 ⇒ 00:49:35.840 Rico Rejoso: as you notice, a bunch of the processes that we have here are still depending, or dependent with, with Tom and Robert’s feedback, or, like, let’s say they still dictate what the next processes should be. Like, let’s say for the LinkedIn outbound and stuff, and
409 00:49:35.970 ⇒ 00:49:42.309 Rico Rejoso: Moving forward, like, one of our goals is to set up, like, a process where we, you know, not totally
410 00:49:42.420 ⇒ 00:49:46.689 Rico Rejoso: Get them off of it, but have them, you know, have them
411 00:49:46.940 ⇒ 00:49:51.870 Rico Rejoso: Do less time, checking things out on the recruitment side, and we can take care of it, right?
412 00:49:52.280 ⇒ 00:49:52.880 Kaela Gallagher: Yeah.
413 00:49:52.880 ⇒ 00:49:56.239 Rico Rejoso: One thing that we also, like, wanted to see how we can improve on.
414 00:49:56.850 ⇒ 00:49:57.500 Kaela Gallagher: Yeah.
415 00:49:57.500 ⇒ 00:49:58.390 Rico Rejoso: What’s out quick?
416 00:49:59.230 ⇒ 00:50:18.860 Kaela Gallagher: Yeah, definitely, yeah. I noticed that Utam and Robert right now are, part of the final rounds for everybody, it seems like, but, it also seems like they’re doing a lot more than that, kind of, throughout the process as well, so yeah, would be curious to see what I can kind of take off their plates.
417 00:50:19.790 ⇒ 00:50:31.310 Rico Rejoso: Yep, thank you. And yeah, feel free, if you have any questions, other questions on stuff here on recruitment, I can definitely help you out and assist you with, what is…
418 00:50:32.910 ⇒ 00:50:38.109 Rico Rejoso: Not sure… not sure if I have anything in the mind, but… Yeah, I guess…
419 00:50:38.250 ⇒ 00:50:42.580 Rico Rejoso: We can take a look… take a better look at all… or everything that we have here.
420 00:50:42.870 ⇒ 00:50:46.009 Rico Rejoso: On this page, and let me know if you have any questions.
421 00:50:46.470 ⇒ 00:50:51.409 Kaela Gallagher: Okay, alrighty, sounds good. I will see you on the meeting with you, Tom.
422 00:50:51.750 ⇒ 00:50:53.580 Rico Rejoso: Yep, thank you so much for the timing.
423 00:50:53.780 ⇒ 00:50:56.670 Kaela Gallagher: Yeah, thank you, Rico, for your help. Talk to you later.
424 00:50:56.890 ⇒ 00:50:57.750 Rico Rejoso: Alright, have a good one.
425 00:50:57.750 ⇒ 00:50:58.979 Kaela Gallagher: I’m ready. Bye.