Automated Codility Hiring Funnel Reports
Every Monday, WebRun opens Codility, counts invitations sent, tests started and tests completed per role for the past week, reads how scores are spread, files the funnel in Airtable next to previous weeks, and creates a Trello card for any role whose drop off or score spread needs a look.
How do I measure how well each role's technical test is converting?
WebRun scores your technical screening funnel every Monday. It counts Codility invitations, starts and completions per role, reads how scores are spread, files the week alongside previous weeks in Airtable, and queues a Trello card for any role where the drop off needs attention.
- Drop off shows as a number rather than a hunch
- A test that is too long is spotted within a week
- Role level trends build up without anyone counting by hand
Built for talent acquisition leads · engineering managers · recruiters · people operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.codility.comin a real browser with your saved login - no setup, no API keys. -
1
Codility - count the funnel per role
codility.com
WebRun opens Codility to count the funnel per role. - Open Codility and list tests sent in the past week grouped by role
- Count invitations sent, tests started and tests completed for each role
- Read the score spread on completed tests: how many passed your bar and how many were far below
- Note the average time candidates took against the time allowed
- Do not change a test, extend a deadline, or reject a candidate. Those stay human decisions
Done when Each role has last week's invited, started, completed and score spread figures.
-
2
Airtable - file the weekly numbers
airtable.com
WebRun opens Airtable to file the weekly numbers. - Open the hiring metrics base in Airtable
- Add this week's row per role with invited, started, completed and pass counts
- Work out the start rate and the completion rate for each role
- Compare against the previous few weeks so a trend is visible, not just one week
- Highlight roles where completion dropped or scores clustered at the bottom
Done when This week's funnel per role is filed alongside recent weeks.
-
3
Trello - queue the roles worth reviewing
trello.com
WebRun opens Trello to queue the roles worth reviewing. - Open the hiring board in Trello
- Create a card for any role whose completion rate fell below your threshold
- Name the likely cause on the card: test too long, bar too high, or too few invitations
- Leave the card for the talent lead to action. No candidate is contacted
Done when Roles worth reviewing have a card with the numbers behind them.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it contact candidates?
No. WebRun counts the funnel and reports it internally. It never emails a candidate, sends a test invitation, extends a deadline, or moves anyone forward or back in your process.
Does it record individual candidate names?
No. The scorecard works at the role level: counts, rates and score spread. Individual results stay in Codility, so the metrics base holds no personal candidate data.
How does it tell a bad test from a quiet week?
It compares completion rate against recent weeks for the same role, so a low count with a normal completion rate reads as low volume, not a problem with the test.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.