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
Neosigma

Member of Technical Staff - Infra Engineer

  • Seen live on Neosigma's site today
  • Senior
Pay
Not stated
Location
San Francisco, CA
Open for
12+ days
First seen
Oct 23, 2026
Apply on Neosigma's site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Neosigma'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 Neosigma, 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 it asks of you

Bachelor's degree asked for
“Bachelor's degree in CS, Engineering, or related field (or equivalent practical experience)” (quoted from the posting)
Equivalent experience accepted instead of a degree
“Bachelor's degree in CS, Engineering, or related field (or equivalent practical experience)” (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

NeoSigma is a product-driven research lab building the intelligence layer that helps close the feedback loop between your customers, products, and AI systems.

We are a small, intensely technical team of researchers and engineers who have trained frontier-scale models and widely used AI products and agents at MIT, Parallel Web, Essential AI, Apple, and Amazon.

We are backed by world-class investors and leaders from Google DeepMind, OpenAI, Decagon and others.

The Role

We are looking for a Infrastructure Engineer to build and scale the foundation that powers NeoSigma's AI platform. You will work across cloud infrastructure, deployment automation, security, observability, and enterprise deployments. Some weeks you'll be deep in Kubernetes, Terraform, and platform reliability . Other weeks you'll partner with enterprise customers to ship secure, production-ready deployments and the infrastructure that enables AI systems to run at scale.

What you'll do

  • Design and ship enterprise-grade deployment architecture across multi-cloud (GCP), BYOC, and VPC-isolated environments for regulated customers
  • Own data retention policies end-to-end: minimal collection, defined TTLs, PII handling, and data residency baked in by default
  • Build private and secure connectivity solutions including VPC peering, PrivateLink, and Private Service Connect for customer-managed environments
  • Own our critical CI/CD infrastructure: pipelines, deployment automation, and rollout/rollback tooling across the full stack
  • Architect security from the ground up: IAM, secrets management, least-privilege access, encryption, and audit logging by default
  • Own the enterprise deployment relationship: SSO/SAML/SCIM, network configuration, and compliance documentation (SOC 2, HIPAA, GDPR)
  • Build and maintain observability: structured logging, metrics, alerting, and on-call practices across distributed deployments

What we look for

  • Shipped real infra at a startup and lived with the consequences
  • Strong fundamentals across cloud (GCP), Kubernetes, and Terraform
  • Experience with enterprise deployment patterns: BYOC, VPC isolation, SSO/SAML/SCIM, and compliance
  • Security-first mindset: blast radius, attack surface, audit trails
  • High ownership mentality: you see problems through and don't wait for someone else to notice what's broken
  • Comfortable writing technical design docs and operational runbooks
  • Bachelor's degree in CS, Engineering, or related field (or equivalent practical experience)

Our Core Values

  • Customer Obsession - We start with the customer and work backwards. We aim to earn trust through consistent delivery, thoughtful listening, and by obsessing over customers.
  • Intellectual Honesty - We operate with high trust and low ego. Ideas matter more than titles, and we communicate openly and directly while assuming good intent, even in strong disagreement.
  • Bias for Action - We set high standards and move quickly to meet them. We prefer building and learning with customers over debating in the abstract, and we iterate based on real feedback.
  • Extreme Ownership - We take responsibility for outcomes, not just tasks. Ownership means seeing problems through to completion and ensuring solutions truly work in practice.

Benefits and perks

  • Competitive salary plus meaningful equity package
  • Comprehensive medical benefits and generous PTO
  • Flexible work arrangements
  • Direct impact on company direction and technical decisions
  • High ownership and the opportunity to make a career-defining impact
  • Visa sponsorship

As a founding member, you’ll help define the technical foundation of NeoSigma. Your scope will grow with the company, from owning core systems end-to-end to shaping architecture, hiring, and engineering culture. This role has a natural path toward technical leadership or engineering management as the team scales.

Something wrong with this posting?