Lightfield

Software Engineer, Security (Staff+)

HQ: San Francisco (USA)
Salary
$220K - $300K
Level
Staff
Work type
On-site · HQ: San Francisco

Not stated in the posting: visa.

Open. First seen 18 November 2026.

About the role

About Lightfield

Lightfield's standard text

Lightfield is reimagining CRM as a world model of a business. By learning from emails, meetings, and customer conversations, we’re building a living understanding of how a company works—so AI can help teams anticipate what comes next, make better decisions, and take action.

More than 5,000 companies have used the product since its November launch. We’ve raised more than $70M from Andreessen Horowitz, Coatue, Maverick Ventures, and Greylock to attack the biggest software category in the world. We previously built Tome, which reached more than 25 million users, and our team brings experience from Llama, Instagram, Google, and Salesforce.

About the role

Lightfield connects to some of a company's most sensitive systems: email, calendars, meetings, Slack, and CRM data. We use that context to power AI agents that take action on a customer's behalf. Earning and keeping that trust is part of the product, not a layer on top of it.

We're hiring our first dedicated security engineer. This is a hands-on staff software engineering role, not a CISO or a compliance-management role. You'll be the engineer closest to our hardest security problems: helping identify which risks matter most, turning them into well-scoped engineering projects, and shipping much of that work yourself.

You'll work closely with our CTO, the engineering leaders who run security today, and our compliance partners, and you'll work directly with customers and go-to-market teams when security is what stands between us and a deal. As you build context, there's room for your scope across the security program to grow.

The work spans application and data security, cloud infrastructure, identity and access, and the security model for AI agents. Some of it is well-trodden (least privilege, encryption, audit logging). Some of it isn't: what should an agent be allowed to read, write, or do on behalf of a user, and how do we prove it stayed inside those lines?

We want someone who would rather ship the fix than write the policy about it. You won't arrive needing a team to be effective. As Lightfield grows, you'll help decide whether and when to build one.

This role can be based in Cambridge or San Francisco. In Cambridge, you'd join an initial group of backend and infrastructure engineers at our new Kendall Square site. In San Francisco, you'd work from our HQ alongside the founders and most of the engineering team.

What you'll do

  • Shape the security roadmap: contribute to threat modeling, help rank risks by how bad the worst case is, and turn findings into well-scoped projects.
  • Design and ship security-critical systems yourself, including tenant isolation, encryption and key management, authentication, and authorization.
  • Define the security model for AI agents: tool-use authorization, data boundaries, defenses against prompt injection and cross-tenant exfiltration, and safe execution.
  • Harden our AWS footprint: least-privilege IAM, short-lived production access, network posture, and infrastructure-as-code guardrails.
  • Build detection, logging, and incident response, and lead the investigation when something looks wrong.
  • Own the engineering side of compliance (SOC 2, ISO 27001), making controls something our systems enforce rather than something we attest to.
  • Join customer security reviews and architecture conversations, especially with enterprise buyers.
  • Help decide what to build, what to buy, and what to contract out, then hold vendors and specialists to a high bar.
  • Raise the security bar for every engineer through design review, code review, secure defaults, and tooling, without slowing the team down.

What your first year could look like

The slate below is real work we've already scoped or started. Priorities will shift as we learn more.

  • Threat model remediation: take the output of our first formal threat model (assets like CRM records, OAuth tokens, and agent action authority) and drive the highest-severity findings to done.
  • Customer secret encryption: finish moving stored customer credentials to per-tenant envelope encryption with key rotation, so database access alone never grants the ability to decrypt.
  • Tenant isolation: strengthen isolation in a multi-tenant Postgres system where it's enforced in the application layer today, including protecting customers from their own misconfigurations.
  • Agent and developer-tool security: set controls for AI coding agents and automations that touch our codebase and production, and for the agents we ship to customers.
  • Infrastructure access: build on our Terraform migration to deliver least-privilege access tiers, just-in-time production access, and SSO everywhere.
  • Audit and authentication: ship customer-facing audit logs (including actions taken under impersonation) and stronger workspace authentication options.
  • ISO 27001: own the engineering controls on the path to certification, alongside our existing SOC 2 program.

What we're looking for

  • You're a strong software engineer first. You write production code, and you'd clear our bar for a staff backend or infrastructure engineer.
  • Deep, hands-on security experience across application security and cloud infrastructure security, ideally as the person who owned security at a fast-growing product company.
  • You reason from first principles about attack surfaces, trust boundaries, and failure modes, especially in multi-tenant SaaS.
  • Strong judgment about which risks are material and which are theoretical. You know what to fix first and what can wait.
  • A record of shipping security-critical systems such as authorization, encryption and key management, identity, or audit logging, from design through production.
  • Autonomy. You can take a loosely defined security problem and turn it into a sequenced plan and shipped work with little direction.
  • You communicate clearly with engineers, executives, and customer security teams, and build alignment without formal authority.
  • You're excited by security problems that don't have a textbook answer yet, like AI agents acting on behalf of users.

Helpful experience

You don't need all of these:

  • AWS security: IAM, Organizations and multi-account setups, KMS, network design, and infrastructure as code (Terraform).
  • TypeScript/Node.js and Postgres, our core stack.
  • Security for LLM applications: prompt injection, tool-use authorization, sandboxing, and data-boundary enforcement.
  • Identity: SSO/SAML/SCIM, MFA, and joiner-mover-leaver automation.
  • Detection and response: logging pipelines, alerting, and leading incident investigations.
  • SOC 2 or ISO 27001 programs, and enterprise customer security reviews.
  • Penetration testing, red teaming, or vulnerability research.
  • Experience at a high-growth startup handling sensitive customer data, such as a CRM, communications, fintech, or developer platform.

Why this role is interesting

Most security engineers join a company after the architecture is set and spend years retrofitting. Here, the foundations are still taking shape. The agent permission model, the encryption design, and the access model you build will define how Lightfield earns trust as it moves into the enterprise. You'll have a direct line to the CTO, real budget for tools and specialists, and room for your scope to grow with the program.

Benefits & Perks

  • Competitive salary
  • Meaningful early equity
  • Health insurance (medical, dental, vision)
  • 3 weeks of PTO
  • 11 paid company holidays + we enjoy a winter holiday break
  • 3 months of paid family leave
  • Wednesdays work from home
  • Regular team dinners, events, offsites, and retreats
  • 401k plan
  • Other perks include: commuter and lunch stipend

What this role asks for

Particular to this role

IAM · OAuth · Penetration Testing · Terraform

Rare in Lightfield's other 8 open postings.

Standard for security roles

AWS

Common in security postings at any company.

In most of Lightfield's ads

PostgreSQL · Salesforce

Named in most of its open postings, whatever the role.

96% of this description is written for the role. The rest is Lightfield's standard text, folded away below.

Compared with Lightfield's other open jobs.

The team: Engineering HIRES STEADILY

This role is one of 7 open in Engineering. 1 was posted in the last 30 days and the oldest in January: a team that hires all year rather than one being built.

WHAT THE TEAM WORKS WITH, ACROSS ITS POSTINGS

Salesforce (7 of 7), PostgreSQL (6 of 7), JavaScript (5 of 7), LLM (5 of 7), Node.js (5 of 7), TypeScript (4 of 7), GraphQL (3 of 7)

OTHER ROLES ON THIS TEAM

From the team and dates on Lightfield's own job board.

Similar jobs

More jobs like this

Is this your posting? Email [email protected] to have it removed.