Your briefing
Loading…
How often should we check in?
When nobody has set a date, Trellis works one out: the last thing recorded about someone, plus the gap below. Set a gap to 0 to stop chasing that stage altogether.
A players know A players
If you'd happily work with someone again, add them — whether or not we're hiring.
- You add them Their name, what they do, and why you rate them. Two minutes.
- We take it from here We check the fit, reach out if it makes sense, and you'll see what happened.
Your people
We're hiring for
Loading…
Loading your network…
Where everyone is
Who's growing the network
Recent activity
What deepset is hiring for
Straight from deepset's careers board — the same postings a candidate sees, refreshed whenever the TA team opens Trellis. Confidential reqs are never posted publicly, so they never appear here.
Talent garden
Everyone the team has grown a relationship with. Add anyone worth keeping warm; Trellis watches for when they become a fit.
| Person | Role | Company | Location | Referred by | How we know them | Stage | Tags | Considering for | TA progress | Last activity | Actions |
|---|
Ready for a conversation
Flagged when someone's profile lines up with an open role, or with how we describe our culture and bar in Notion.
Suggestions compare job title, team, seniority and location against the open Ashby roles. Trellis has not read anyone's notes and has never seen a scorecard, so treat them as a shortlist to check, not a verdict. Nothing changes stage until you press Flag.
Who's using Trellis
Everyone who has signed in at least once. Accounts appear here on their own — there is nothing to invite, people just open the link with their deepset account.
| Person | Role | Referrals | First signed in | Last seen | Actions |
|---|
TA can see the whole talent garden, the referral flags and the integrations. Employees see the open roles and only the people they referred themselves. You can't change your own role here — ask another TA, or do it in the Firebase console.
Where Trellis reads and writes
Notion and Ashby feed the pipeline's matching step. Slack is where new people get added. Ashby is where flagged prospects go.
Ashby careers board
Slack
How people know each other
Share the add link
&linkedin=… to it and the name and profile link fill themselves in.
Back it up
Data & retention
Duplicate lookup
Manual role import — fallback, if the board sync ever fails
data/ashby-roles.json from the project folder, or paste its contents. Re-importing updates roles in place; any role missing from the file is marked closed, so this file is the full picture of what is open. Reqs marked confidential in Ashby are refused — Trellis is visible to everyone at deepset, so match those in Ashby instead.Slack
- New people, from anywhere in Slack (write, on submit only)
Notion
- Role scorecards and competency frameworks (read)
- Team and values pages (read)
Ashby
- Open jobs, team, location, confidential flag (read, manual)
- Scorecards and requirements, for real matching (read) — not yet
- Existing candidates, for de-duplication (read) — not yet
- New referral prospects (write, on approval) — not yet