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
Composio

Member of Technical Staff, Enterprise Product

  • Seen live on Composio's site today
  • Senior
Pay
Not stated
Location
sf
Open for
17+ days
First seen
Oct 18, 2026
Apply on Composio's site (opens in a new tab)

Posting record

No flags

Open 17+ days

The posting's record, oldest first
  1. Composio'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 Composio, so its true age is longer.

Last checked Nov 4, 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

At Composio, we are building infrastructure that allows agents to communicate with the tools you use for work including Github, Gmail, Notion, Salesforce, etc. We raised a $25M Series A from Lightspeed with angels like Guillermo Rauch (CEO of Vercel), Dharmesh Shah (CTO of Hubspot), and Gokul Rajaram. We've 3x'd our ARR this year, and our customers range from your friends in the YC batch to Wabi, Glean, Zoom and many more.

Enterprise Product sits where the hardest customer workflows become durable product. You will work directly with enterprise customers and FDE, turn ambiguous asks into product primitives, and ship the code that makes the next customer easier than the last.

WHAT YOU'LL WORK ON

1. Turn large enterprise APIs into agent-usable tool surfaces: tool granularity, composite tools, descriptions, scopes, auth, and evals.

2. Productize repeated FDE work into self-service patching, QA harnesses, deployment paths, admin controls, docs, and guardrails.

3. Make enterprise deployments repeatable across hosted, VPC, on-prem, regulated, and BYOK environments.

4. Build the product layer that lets Composio scale from bespoke enterprise engagements to repeatable enterprise motion.

WHAT YOU'LL DO

  • Own enterprise product surfaces end to end: discovery, spec, design, implementation, QA, release, adoption, and iteration.
  • Ship production code across toolkits, SDKs, auth and scope flows, admin surfaces, deployment tooling, and customer-facing enterprise features.
  • Work with FDE, customers, and core engineering to convert field pain into crisp product requirements and shipped primitives.
  • Build evals and QA loops that prove enterprise workflows are reliable, not just demo-ready.
  • Write the specs, docs, launch notes, and customer-facing updates that make the work easy to adopt.

"MUST HAVES"

if you are very good, nothing is a must per se

  • Product-minded engineer: you turn messy workflows into clean product, then ship the code.
  • Enterprise integration depth: OAuth, consent, scopes, service accounts, webhooks, rate limits, and strange API behavior do not scare you.
  • Customer ownership: you can take a named customer or product surface from first conversation to live usage.
  • AI native: you have built with language models, built for language models, and have opinions on agents, MCP, evals, and tool choice.
  • Systems judgment: you think in rollout paths, rollback paths, security exposure, version skew, and maintainability.
  • Clear writer: your specs, docs, and customer updates earn trust under deadline.

OPTIONAL

  • Python in production; TypeScript a plus.
  • API platform, iPaaS, developer tools, infra, or integration-heavy background.
  • Prior FDE, solutions architect, sales engineer, or enterprise product engineering role.
  • Kubernetes, Helm, Temporal, Postgres, Replicated, cloud secret managers, or packaged self-hosted delivery.
  • Security and compliance exposure: SOC 2, Vanta-style programs, questionnaires, CVE triage, or RCAs.

Something wrong with this posting?