SSW Coding Challenge Updates Sep... I mean Oct 2025

How's everyone? This is Gordon from SSW

and today I just want to take you

through some of the changes we've made

to the coding challenge app. So, with

the app having run now for a couple of

years, um I thought it'd be quite cool

to introduce some charts.

Um so, the first thing I'll show you is

on the tech challenges. So, you'll now

notice there's this little uh charts

button.

If we click that, you'll see it shows

you uh some summaries. So this shows you

for the last 12 months how many

challenges we've had every month and

then also um every month well of those

challenges how many challenges have been

done by which people and then you can

see at the bottom here that it's just

showing you this is currently the date

range that these are showing and then

you can click and open this up and this

will show you who's been doing how many

challenges um across that time span. The

summary at the top is for total amount.

So this summary isn't um just for um

this sort of bottom uh range here.

That's for all of them.

Now obviously if we adding um charts to

the tech tech challenge, it makes sense

that we'll just add them for the coms

challenge as well. So if we head over to

the coms challenge, you can see that

these charts are also here. um and they

also show in the same way. So you can

see it does the the little split u and

the chart show. So those are those two

work um pretty much identical to each

other.

Then the next bit of changes here. So

when I showed these changes to cookie,

he had some ideas of other stuff that

sort of that they

um look for um or data that they're

trying to pull out of the system. And so

I went and added more charts for this.

So as you'll see, sorry I haven't

mentioned here, but charts is now on the

on the dashboard as well. And part of

the reason for that is they wanted some

filtering as well, which I thought would

make sense if this data was all together

to show it. So if we're on the

dashboard, you can see we've got a date

range here. So currently this when this

loads, it will show from uh one year

back and to the 1st. So, because we're

on the 13th of October, this goes back

and shows you from the 1st of October.

And then it shows you for the current

month to the end of that month. So,

again, because we're on the 13th of

October, it defaults to the end of this

month.

And then this shows you that just a

quick summary inside this range. So

there's 85 challenges um across that

span um more coms challenges 27 tech

challenges and then um there's been 10

challenges which from this funnel on the

side haven't actually made it uh gone

through the full uh funnel. Now, that

could happen when we have to change the

email address of someone. Um, or if

there's a test. Um, so like Vlad or

myself does a test to check some stuff.

Uh, we might create a test challenge

that hasn't actually gone through this

full funnel. Which brings me to

obviously that next part of the the

chart and a chart that you didn't see on

the previous pages and that is the

candidate funnel. So, we look at the

email address of the coms challenge and

we see how many people get the V1 that

then make it through to the V2 and then

of those people that then obviously drop

down to the tech challenge.

I'll show you something about that soon.

But then at the bottom here, these are

basically just these same charts that

you saw on the other page um just

filtered down to these date ranges.

So if I go ahead and make this be just

October of last year,

we can see that it says that there was

15 total challenges or coms challenges.

Um on the V1 input of the funnel, there

was 14 and the V2 there was 13. Now,

those three numbers feel like they don't

make much sense, but the way that we

actually calculate this is we look at

the date for the appointment

um and we check if that's inside this

range. So, in this case, it's saying

that we have 14 candidates where their

um appointment date was in this range

and then we have 13 where the V2 was in

that range. And in this case, the actual

data for that, if we go and look at it

and we look at past and then we find

October,

you'll notice if you had to go through

here and count these records that we

have 14 records up until this point, um,

which matches with the, uh, 14 that you

saw. But then if we scroll a little bit

lower down, we have this um this record

that had a V1 that was in September and

the V2 was in October. And that's how

when we look at this um data again,

we get apply we get 13 people that had a

V2 um and only 14 with a V1. And

obviously because that one extra person

is outside of the range that makes the

total amount of coms challenges in that

period 15.

Now outside of just um charts there was

one other small change. So around the

way we sort of cancel and delete com ch

coms's challenges.

So there was a record and if we had to

go look in production you would um see

it but there is a record that was sort

of stuck here because the coms challenge

had been set up but it couldn't get

cancelled

and the reason it couldn't get uh

cancelled is because we had some logic

that said that you can only cancel

something after it's been provisioned

which means that you can only cancel it

after you've created an appointment and

then save that which means the meeting

requests have been sent out to the

candidates.

Now that case itself was a little bit of

an edge case with the way that candidate

was sort of came into the system and

then didn't want to be in the system. Um

but yes, nonetheless there was a record

that was stuck here. So what we've gone

and done is changed how you can delete

um com challenges and we've changed this

for two reasons. one, we've changed it

because of that issue where someone got

stuck on the on the sort of homepage and

you couldn't get rid of them without

actually fully setting them up and then

deleting them. And the second one is um

say for example this person

um had their followup so they they have

their V2 scheduled and then they don't

show up for their V2. Now what would

currently happen or maybe they say

actually I'm fine thanks I don't want to

do the V2. our recruitment team would

hit delete and when they hit delete they

would actually clear out all of these um

times uh time slots and would go cancel

all the meetings and we wouldn't know

that this challenge actually happened

from our data perspective. So now what

happens is if you click delete it says

um do you want to cancel the V1

appointment which is for this date? Do

you want to cancel the the follow-up

which is on this date? Um, and you can

go ahead and say yes, you want to cancel

this one or actually I want to cancel um

basically everything. Um, and then that

just says, hey, when you cancel this,

you'll actually be canceling the V2 as

well. So now if I go and delete this,

that candidate is fully cancelled and

they'll show up in this list.

Now one other thing that you'll notice

here is that from that previous delete,

as I was saying, it would cancel

everything. So in this list currently

everyone has uh no data.

This person if I just move myself to the

side um happens to be the person that

was stuck previously. Um so now um

you'll see that they actually do have

data even though they're showing in the

deleted um appointments which means from

a charting perspective we can pick up

that they had a V1 and a V2 scheduled.

um they just happen to get deleted and

those um the data saying that they

actually did that V1 and V2 um didn't go

with it.

So that's all the changes that I had um

or that I'm publishing at the moment. Um

if you have any questions or feedback uh

let me know. The idea is to let the

recruitment team use these these changes

for a little bit and then potentially

get someone to do any tweaks that they

need. Um, I just had some time um, a

couple weeks back and I decided to start

vibe coding some stuff and this is how

this stuff came up. So yeah, if you have

any questions, let me know. Otherwise,

this has been Gordon from SSW. Cheers.