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
Conversion

Software Engineer (Infra)

  • Seen live on Conversion's site today
  • Mid level
Pay
Not stated
Location
San Francisco Office
Open for
7 days
First seen
Oct 28, 2026

Posting record

No flags

Open 7 days

The posting's record, oldest first
  1. Conversion'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.

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 it asks of you

3+ years of experience
“Have 3+ years of experience building cloud infrastructure, dev tooling, and platform systems at fast-growing companies” (quoted from the posting)

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

About Us

Conversion is the agentic marketing automation platform for modern enterprises such as Plaid, ClickHouse, Webflow, and Productboard. Our platform lets growth teams run their entire go-to-market motion in one place, from acquisition through retention, with AI agents doing the work that legacy tools like Marketo, HubSpot, and Pardot can't.

We've raised $28M+ from Abstract Ventures, True Ventures, and HOF Capital. The team is based in San Francisco and includes engineers, designers, and operators from Airbnb, Palantir, Pinterest, IMC, Shopify, LinkedIn, and Microsoft.

About the Role

Hey there! James here 👋, co-founder and CTO at Conversion. Just wanted to share my thoughts on the perfect candidate we're looking to join our engineering team.

First off, I want to stress the technical difficulty and scale of what we're building here at Conversion. The reason marketing automation platforms haven't seen a new player in decades is because building one is hard. Our platform needs to handle terabytes of data syncs per customer with the utmost reliability, coordinate complex workflows that automate mission critical go-to-market processes, handle form submissions that directly generate revenue for customers, and serve high delivering emails to millions of our customer's recipients.

Here's what we're looking for in an infrastructure engineer to join our core team

  • Engineer multiplier: Your customers are all other engineers. The goal is to unlock and empower them to ship features faster and more reliably for our customers. The best infra work here is measured in how much leverage you give the rest of the team.
  • Pragmatic optimizer: Over-optimizing is a real thing. As a startup, our goal is to grow and build an amazing product that delivers value, not to needlessly upgrade our tech stack for the sake of it. Your job is to strike the line between the cost of infrastructure changes and the potential benefits. Everything's a tradeoff and we want to take the worthwhile ones.
  • Intellectually curious: Conversion engineers are the kind of people who get excited about a weird edge case and end up sending five Slack messages about it before lunch.

This role is in-person 5 days/week in San Francisco.

You Might Be a Good Fit If You

  • Have 3+ years of experience building cloud infrastructure, dev tooling, and platform systems at fast-growing companies
  • Have shipped and operated systems that other engineers depend on, including CI/CD, observability, deploy tooling, or internal platforms
  • Have a startup mindset and want early ownership in a fast-paced environment
  • Have experience with our tech stack:
  • Go for backend services
  • Kafka, Temporal, PostgreSQL, Clickhouse, Terraform as foundational technologies
  • Kubernetes as the compute platform
  • ArgoCD, Grafana, VictoriaStack for logging and management
  • GCP for cloud hosting

You Might Be a Great Fit If You

  • Have built internal developer tools or platforms that meaningfully changed how a team shipped
  • Believe keeping things in good shape is paramount (security, reliability, organization)
  • Have worked at a Series A to C startup that scaled quickly
  • Have a strong track record of side projects, apps, or hackathons. Our engineers have built a live-streaming security system for their parents' new house, a database from scratch, a better Splitwise app, and hosted our Minecraft server, all while at Conversion

Useful links

  • Website: https://conversion.ai/
  • Careers: https://conversion.ai/careers
  • Next Play article on our team: https://nextplayso.substack.com/p/how-a-big-pivot-helped-this-company
  • Engineering blog: https://conversion.ai/blog

Something wrong with this posting?