Plan your day
6 open — here's where to start live · Tue 09:14Morning, Rita.
6 things open. Two are getting tight.
/ Where I'd start
The Senior Java @ Banco Atlântico match — client's waited 4 days and they decide fast. Then reconnect with Miguel S. before he cools; he's mid-process elsewhere.
Open · needs you today
Senior Java — Banco Atlântico 4 days waiting
3 candidates ready. Client decides fast — don't let it sit.
Reconnect — Miguel S. cooling
No reply in 3 days, and he's in a hurry. Likely talking to others.
New CV in inbox — Data Eng @ Nearform
Add the candidate and I'll tell you which open role fits best.
2 candidates going quiet
Ana R. and Tiago M. haven't moved in 2 weeks. Still on the market?
Open points to validate · by position
Senior Java — Banco Atlântico 3 open
Confirm before submitting: candidate accepts on-site, English at bar, rate within ceiling. Each one re-scores the match.
DevOps — Nearform 1 open
Just confirm timing — candidate available in the client's window? Then it's ready.
/ Worth knowing
Banco Atlântico tends to be slow (~3 wks). If a candidate's in a hurry, line up a faster client in parallel — don't lose the match to the wait.
Senior Java Engineer
Banco AtlânticoEvaluation criteria — weighted for this client
Not a job description. What Banco Atlântico actually weighs, learned from outcomes. Skill splits into four — and this client weights domain over raw technical.
Functional / domaindecisive
Banking depth (SEPA, fraud, compliance). Last 3 rejections were sector outsiders.
Hard / technicalweighed
Java/Spring, Kafka, microservices. Strong-enough beats strongest here.
Leadershipweighed
Owned a migration end to end? Confirm architected vs executed.
Soft / communication + Englishdecisive
Client-facing role, strict on English. A common rejection cause here.
Add a candidate to this match
LinkedIn for the trajectory, CV for the detail — I read both against what this client actually accepts.
Before I look — who's your gut say fits?
Call it first. I'll tell you if I agree — and it sharpens the read over time.
Six agents reading the match against the client
BCandidate B
Not the best engineer of the three — but the best fit. 6 yrs Java/Spring, two real banking builds (SEPA, fraud). Banking domain is exactly what this client keeps rejecting outsiders for not having. Here, fit beats raw skill.
I'm confident on:the domain match and the rate (€450 sits inside their band). I'm inferring the seniority — worth confirming, not assuming.
CV says "led migration" but not team size or his real role — confirm he architected vs. executed. For this band, that's where offers fall apart.
↳His Kafka depth is unproven on paper.
ACandidate A — best engineer, riskier fit
Cleanest Kafka/microservices work. But ~1 level short on seniority and zero banking — and this client passes on sector outsiders. Wants €520, above their ceiling. Clears the bar technically; on fit, it's a gamble.
CCandidate C — watch the pattern
Good profile, but 3 roles in 4 years. For a long banking placement that gets flagged at client interview — and his rate likely runs above what they close at.
Before you submit, ask in screening
- "Walk me through the SEPA project — what did you own end to end?"
- "What kept you moving roles every ~18 months?"
- "What day-rate are you targeting?"
Open points to validate — both sides
Tap each as you confirm it. The score re-runs on real data, not inference. Unconfirmed points stay as tasks on the opportunity.
Client side
Domain — banking experience real?
inferred · confirm
English at the client's bar?
inferred · confirm
Seniority matches the brief?
inferred · confirm
Candidate side
Accepts rate within ceiling?
inferred · confirm
Accepts 2 days on-site?
inferred · confirm
Available in the client's window?
inferred · confirm
Match score
72
→
72
Confirm points to move from inferred to confirmed.
Clarify the fit — positioning, not a quiz
The system turns open points into simple sliders — sent to both sides. No right answers; the fit is how close the candidate lands to what this client wants. Things ChatGPT can't fake.
Two simple links — clicks and sliders, barely any typing. Each answer re-runs the match and feeds the network. The fit is the overlap, not the answer.
Submitting reaches the client — it's your call, not mine.
Good day's work, Rita.
Here's what moved.
1
match closed
4
candidates read
3
submissions advanced
2
cleared with reason
/ I noticed
You called B over the stronger engineer — and you read the banking-fit right where the obvious pick was A. Third time this month your gut beat the CV. You're becoming the desk's banking-fit specialist.
Just for you — never shared with your manager.
Close the loop — it's what makes the next match sharp
Banco Atlântico — how did the submission land?
One tap. It teaches the system what this client really accepts.
Candidate B — was this client a fit for him?
Send him a 2-tap check. His answer makes the next match better.
Today's timeline
Closed — Senior Java @ Banco Atlântico → submitted B
Read 4 candidates · 1 match, 3 quick reads
Cleared 2 · stack mismatch on Data role
Miguel S. still pending · follow-up drafted, not sent
Your update
Standup brief's ready for tomorrow. Review it, then send — or don't. It's yours.
All · 9HotWaiting on clientNeeds candidates
47
active candidates
12
in a process now
AllJava / BackendDevOpsDataAvailable now
Where the rates land
What clients actually close at for Senior Java, contract, Lisbon — last 90 days.
Your best-fit clients
Where your submissions actually convert — fit rate, not volume.
Your pipeline, by stack
What you're holding right now.
Java / Backend42%
DevOps / Cloud30%
Data / ML28%
Your desk only — never rolls up to your manager as individual performance.
Huntchy assists — it never decides. It shows the fit and what to confirm, never who to cut. Your performance is yours alone.