All remote jobs

Senior Software Engineer, Patch Engineering & Vulnerability Remediation

AI Summary
This senior engineering role builds secure release infrastructure and automation for software deployed in regulated and air-gapped customer environments. The engineer will own hardened container-image pipelines, vulnerability triage workflows, and remediation practices. Core work includes reproducible builds, SBOM and VEX generation, scanner evaluation, and patching upstream dependencies using Go or Python. The position has substantial technical ownership and requires clear evidence-based communication with auditors and customer security teams.
Remote from
Argentina
Salary
Undisclosed
Department
Cybersecurity
Employment
Full Time
Experience
Senior
Published
Apply before
13 Dec 2026
Listing views
46
Application actions
4
Application toolkit

Make your next move.

Prepare your resume, explore your fit, and draft a cover letter for this opportunity.

Opportunity details

About this role.

Who we are

At Domino, we build solutions that help the largest, highly regulated organizations adopt AI to accelerate mission-critical use cases. Our platform integrates a streamlined model and app development environment, advanced model, agent, and app hosting capabilities, and novel governance capabilities providing regulator-ready AI at scale. Our customers — like Johnson & Johnson, GSK, Bristol Myers, UBS, FINRA and the US Navy — are using our software to solve some of the most important challenges in the world, such as developing new medicines, securing our financial markets, or protecting our country. Backed by Sequoia Capital, Coatue Management, NVIDIA, Snowflake and other leading investors, we have been in business for over a decade but are still a small team operating with the spirit of a startup. In the world of AI today, we believe that the future is still being invented — and we want to be the ones building it. For more information, visit www.domino.ai

What we are building

The Release Engineering & Vulnerability Remediation team is building the infrastructure and automation that lets Domino ship hardened, auditable software to our most security-sensitive customers—federal agencies, financial institutions, and healthcare organizations operating in regulated or air-gapped environments.

Concretely, we are building:

  • A hardened release pipeline that produces container images meeting strict scan thresholds, with reproducible builds and minimal attack surface
  • An automated vulnerability triage system that ingests scanner output, deduplicates findings across images and releases, routes to owners, and tracks SLA compliance—without manual triage
  • Provenance and exploitability tooling that generates SBOMs and VEX statements on every release, so customer security questions are answered from standing artifacts rather than one-off investigations
  • A scalable remediation practice that uses AI and automation to keep pace with the volume of findings, rather than throwing engineers at each CVE individually

This is foundational work. The tooling and runbooks you build will define how Domino operates in regulated markets for years to come.

What your impact will be

In your first year, you will

  • In your first year, you will own the hardened image pipeline for our most demanding deployments and cut time-to-remediate for critical and high findings to a published, defensible SLA.
  • You will replace one-off vulnerability firefighting with an automated path from scan to fix, including SBOM and exploitability statements generated on every release.
  • You will make “we are not fixing this, and here is why” a documented engineering position backed by evidence, rather than a conversation repeated with every customer.
  • You will set the technical direction and tooling that the next engineers on this team build on.

What we look for in this role

  • Experience shipping and maintaining software or container images into regulated, on-premises, or air-gapped environments where you cannot simply redeploy to fix a problem
  • Deep fluency with container build systems, base image strategy, and reproducible builds, plus working knowledge of Kubernetes and Helm packaging
  • Hands-on experience with vulnerability scanning and provenance tooling, and the judgment to distinguish a real risk from scanner noise
  • Go and/or Python strong enough to build automation and to patch upstream open-source dependencies when no fix exists
  • Clear technical writing. You will produce evidence that external auditors and customer security teams read and act on
  • A bias toward removing whole classes of problems rather than closing tickets

What we value

  • We value a growth mindset. High-performing creative individuals who dig into problems and see the opportunities for success
  • We believe in individuals who seek truth and speak the truth and can be their whole selves at work
  • We value all of you that believe improving is always possible At Domino Everything is a work in progress – we can do better at everything
  • We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company
  • We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply

#LI-Remote

Apply now >

This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.

Role DNA

A quick view of the complexity, pace, ownership and collaboration implied by the job description.

Job Complexity

5/5
EasyHard

Pace & Pressure

4/5
RelaxedFast-paced

Autonomy Level

5/5
GuidedFull ownership

Communication Load

4/5
IndependentCollaborative
AI insightThe role combines senior software engineering with DevSecOps, supply-chain security, and regulated deployment constraints. It requires sound judgment about exploitability, durable automation design, and independently setting technical direction.

Salary analysis

Estimated compensation compared with the broader US market for similar roles.

Estimated job median (per year)Market rate
$95,000
US market range (per year)$75k–$125k
AI insightThe yearly pay period is inferred from the job context; it was not explicitly stated by the employer. No employer compensation was disclosed. The annual figures are estimated USD market compensation for a senior remote security and release-engineering specialist in Argentina and are not employer-provided pay.

Core skills

Skills and capabilities most closely associated with this opportunity.

Sample interview questions
How would you design an automated path from a container vulnerability finding to a verified fix?

I would ingest and normalize scanner findings, deduplicate them by package, image, and release, then enrich them with severity, reachability, exploitability, and ownership data. The workflow should create prioritized remediation work, verify rebuilt images through scanning and policy gates, and retain evidence linking the finding, decision, fix, and release.

What factors would you use to decide that a reported CVE does not require remediation?

I would review whether the affected package is present, whether the vulnerable code path is reachable, the deployed configuration, available mitigations, and the reliability of the scanner data. Any non-remediation decision should be time-bound where appropriate and documented in a VEX-style statement with evidence and a review owner.

How do reproducible builds improve security in regulated environments?

Reproducible builds make it possible to verify that an artifact corresponds to known source code and declared dependencies rather than an uncontrolled build environment. They reduce supply-chain uncertainty, support audits, and make it easier to investigate or recreate a released image when a vulnerability is discovered.

Describe how you would reduce vulnerability remediation backlog without simply adding more engineers.

I would first identify recurring root causes such as stale base images, unowned dependencies, noisy scanner rules, or manual handoffs. Then I would automate base-image updates, ownership routing, policy-driven prioritization, and evidence generation, while using dependency and exploitability data to focus effort on meaningful risk.

How would you communicate a security remediation decision to an external auditor or customer security team?

I would provide a concise statement of the finding, affected artifacts, severity context, exploitability assessment, mitigation or fix status, and supporting evidence. The documentation should be reproducible, traceable to a specific release, and written clearly enough that the reader can understand both the technical rationale and the accountable decision.

This analysis is generated from the job description. Salary estimates, role characteristics and sample answers are guidance, not employer-provided facts.
Next step

Apply now.

Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.

Did you apply?Let us know, and we’ll help you track your application.

Continue on the employer website

Protect your personal information and never pay to secure an interview or job offer. .

Log in to save
One quick step before you apply

Sign in to continue.

Sign in or create a free account to continue to the employer's application.

Add alert
Jobs Talent AI Tools Salaries
Menu