Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Ciridae

Full Stack Engineer

  • Seen live on Ciridae's site 3 days ago
  • Mid level
Pay
Not stated
Location
San Francisco
Open for
11+ days
First seen
Oct 24, 2026

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Ciridae's site dates the posting
  2. Ghostless first sees this listing
  3. 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 resume

What 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 turn a compelling prototype into the production system a customer actually runs on. Full-stack, at a pace that is not normal. This is a high-agency engineering role with unusual variety: every engagement brings a different industry, workflow, and technical problem. Our Forward Deployed Engineers go into the field, learn how the business works, establish the vision, and build the first version. You take that context and make it real: well-architected, reliable software that handles messy data, demanding users, and everything production exposes. While the FDE leads the customer relationship and communicates the vision, most of your time is spent building.

What you own. The application from validated prototype through launch and iteration: frontend, backend, data models, integrations, LLM orchestration, testing, deployment, and the operational plumbing that keeps it running. You translate field context into technical decisions and make complex AI systems intuitive for nontechnical users. This ownership includes identifying gaps, making architecture decisions, pushing back when solutions will not survive production. What you learn on one engagement becomes a reusable component, pattern, or capability that makes the next deployment faster

What you bring. Deep full-stack engineering fundamentals. You have shipped production software across React and TypeScript on the frontend and Python, APIs, and Postgres on the backend. You can design clean data models, debug across the stack, and reason clearly about security, performance, reliability, and maintainability. You have production experience with LLM-powered applications and practical opinions about agents, RAG, tool use, evaluations, observability, and designing around non-deterministic behavior. You use AI deeply in your engineering workflow to build, debug, and iterate faster. You pair urgency with a high bar for code quality and production readiness.

Level. We expect roughly 3+ years of software engineering experience, with demonstrated ownership of complex systems end-to-end. Technical depth and independent execution matter more than an exact number of years.

Something wrong with this posting?