Posting record
Open 11+ days
- Ciridae's site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Ciridae, so its true age is longer.
Last checked Nov 1, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat the posting discloses
Not stated: Pay, real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Some employers add pay only on their own site. Check the original posting before you rule it out.
Skills mentioned
About the role
You build the systems behind the systems. Every Ciridae customer deployment runs on the platform you maintain - the leverage of your work compounds with every new engagement. This is the role for engineers who would rather solve the hardest infrastructure problem once than the same problem six times.
What you own. The hard problems behind running production AI across many live customer environments at once. Multi-tenant infrastructure, reliability and cost controls for non-deterministic systems, evaluation and observability where the ground truth keeps moving, and the internal tooling that turns what we learn on the ground into leverage for the next deployment. The questions a seed-stage team would normally postpone - we answer them now, because we have to.
What you bring. Deep systems engineering - distributed systems, APIs, databases, cloud infra. Expert Python (Go or TypeScript a plus). Terraform, GCP, containers, multi-tenant production experience. Taste for the LLM-specific infra problems: model routing, evals, cost and latency controls.
Something wrong with this posting?