Remote Information Security Engineer jobs can offer experienced cybersecurity professionals the opportunity to protect software products, strengthen development processes, reduce vulnerabilities and help engineering teams build security into technology from the beginning.
Important vacancy update: The original Advanced Information Security Engineer vacancy connected with this page was published in June 2025 and may no longer be accepting applications. This page has been rebuilt as an evergreen application guide for people pursuing current remote Information Security Engineer, Product Security Engineer, Software Security Engineer and Cybersecurity Engineer roles.
The historical Zebra Technologies vacancy advertised annual compensation of $120,400–$180,600, plus potential incentives. That range applied to one specific position and should not be treated as the standard salary for every security engineering role. Current compensation can vary according to employer, location, experience, specialization, responsibilities and work arrangement.
This guide explains what Information Security Engineers do, how product security differs from other cybersecurity paths, which technical skills employers may expect and how to determine whether your experience is suitable before applying.
Find Current Remote Cybersecurity Opportunities
Search active WorkinVirtual listings for remote information security, product security, application security, cloud security and cybersecurity engineering roles. Always verify location eligibility and application details in the current vacancy.
Search Current Remote JobsContents
- What an Information Security Engineer Does
- Product and Software Security Work
- Common Security Engineering Responsibilities
- Technical Skills Employers May Require
- Experience, Education and Eligibility
- How to Prepare Your Security Resume
- Interview and Technical Assessment Preparation
- How to Find Current Remote Security Jobs
- Practical Next Steps
What Does an Information Security Engineer Do?
An Information Security Engineer helps protect an organization’s technology, software, systems and data from security threats. The role can involve designing safeguards, reviewing technical risks, investigating vulnerabilities, improving security controls and working with engineering teams to prevent weaknesses from reaching customers.
The exact responsibilities depend on the employer. Some Information Security Engineers focus on corporate infrastructure, identity, networks and cloud environments. Others specialize in product security, application security, DevSecOps, vulnerability management or secure software development.
Common related job titles include:
- Information Security Engineer
- Cybersecurity Engineer
- Product Security Engineer
- Software Security Engineer
- Application Security Engineer
- DevSecOps Engineer
- Cloud Security Engineer
- Security Automation Engineer
- Vulnerability Management Engineer
- Security Architecture Engineer
These titles can overlap, but they should not be treated as identical. A Cloud Security Engineer may concentrate on cloud architecture and configuration, while a Product Security Engineer may work more closely with software developers, product teams and release processes.
Read the complete job description before applying. A position may require secure coding, threat modelling or software-development experience even when the title appears broad.
What Is Product and Software Security?
Product security focuses on protecting the technology that an employer creates, sells or provides to customers. This may include software applications, connected devices, operating platforms, mobile technology, cloud services or enterprise systems.
A Product Security Engineer works with development and product teams to identify risks before and after release. Instead of waiting for a security incident, the engineer helps introduce security requirements, testing and controls throughout the development lifecycle.
This can involve:
- Reviewing product designs for security weaknesses
- Helping developers use secure coding practices
- Identifying vulnerabilities in code and dependencies
- Improving security checks within CI/CD pipelines
- Supporting threat modelling and risk analysis
- Reviewing third-party components and software libraries
- Coordinating vulnerability disclosure and remediation
- Helping teams prepare secure product releases
Zebra Technologies develops digitized and automated solutions used across industries such as retail, healthcare, manufacturing and logistics. Its official careers information presents the company as a global technology employer building intelligent solutions for operational environments. A security engineer working in this type of organization may need to consider software, devices, cloud services and customer environments rather than one isolated application. :contentReference[oaicite:0]{index=0}
You do not need experience with every possible Zebra product to pursue similar roles. However, product security applicants should understand how security decisions can affect reliability, customers, engineering schedules and product delivery.
Applicant note: Product security is different from general security operations. A Security Operations Center role may focus on monitoring and responding to threats, while a product security role usually works more directly with software, engineering and release teams.
Common Information Security Engineer Responsibilities
Job descriptions vary, but remote security engineer roles often combine technical analysis with cross-functional communication. Employers may expect the engineer to identify risks and also help other teams resolve them.
Secure software development
Security Engineers may help integrate security into the software development lifecycle. This can include defining coding standards, reviewing architecture, supporting security testing and advising developers before software reaches production.
Strong applicants should be able to explain how security can be incorporated without stopping development unnecessarily. Employers often value professionals who can prioritize risk and recommend practical improvements.
Vulnerability management
Vulnerability management involves discovering, assessing, prioritizing and tracking security weaknesses. Engineers may use automated scanners, manual review, penetration-testing results, bug reports or external disclosures.
The work is not complete when a vulnerability is found. The engineer may need to validate the issue, assess severity, identify affected systems, recommend remediation and confirm that the correction works.
Security automation and CI/CD protection
Modern development teams release software frequently. Security Engineers may help introduce automated checks into continuous integration and continuous delivery pipelines.
These checks can include:
- Static application security testing
- Dynamic application security testing
- Dependency and open-source component scanning
- Secret detection
- Container-image scanning
- Infrastructure configuration checks
- Security policy enforcement
The goal is not simply to add more tools. Effective security automation produces useful results, reduces unnecessary alerts and helps developers correct problems before release.
Security policy and governance support
Security Engineers may help translate internal policies, customer expectations or regulatory requirements into technical controls. They may also provide evidence during audits, review exceptions or support risk decisions.
This does not always make the role a governance position. In a technical engineering role, policy work is usually connected to implementing or validating security requirements.
Cross-functional leadership
Product security professionals often work with developers, quality assurance teams, product managers, architects, legal teams, compliance specialists and senior leaders.
The ability to explain risk clearly is essential. A technically correct recommendation can still fail when it does not consider business impact, delivery timing or the needs of the people expected to implement it.
Technical Skills Employers May Require
The strongest skill combination depends on the specific role. Applicants should not add every cybersecurity term to their resume. Concentrate on the technologies and responsibilities supported by your actual experience.
Programming and secure code review
Some Information Security Engineer roles require the ability to read or write code. Employers may mention languages such as C, C++, Java, Python, JavaScript, C# or Go.
A security engineer may not work as a full-time software developer, but programming knowledge can help with:
- Reviewing insecure coding patterns
- Understanding application logic
- Building security automation
- Validating vulnerabilities
- Creating testing tools or scripts
- Communicating effectively with developers
Application and product security testing
Relevant knowledge may include static and dynamic testing, software composition analysis, manual code review, penetration testing, API security and mobile or embedded product testing.
Tool familiarity is useful, but employers also assess whether the candidate can interpret results. A scanner may produce hundreds of findings, and the engineer must decide which represent genuine risk.
Vulnerability assessment and risk prioritization
Applicants should understand how severity, exploitability, exposure, customer impact and available mitigations affect remediation priorities.
Simply listing CVSS knowledge is not enough for a senior role. Prepare to discuss how you would handle a severe vulnerability when development teams have competing priorities and an immediate fix is not available.
DevSecOps and pipeline security
DevSecOps connects security practices with development and operations workflows. Relevant experience may include CI/CD platforms, source control, automated testing, containers, infrastructure as code and cloud deployment processes.
Employers may look for candidates who can introduce security checks without creating excessive friction. This requires technical ability, judgement and collaboration.
Cloud, systems and network knowledge
Even product-focused roles may require understanding of operating systems, authentication, networks, APIs, cloud services, encryption and access control.
The required depth varies. A software security role may prioritize code and application design, while an infrastructure security position may demand stronger network and cloud architecture experience.
Experience, Education and Eligibility
The historical Zebra vacancy described a senior-level opportunity and requested substantial cybersecurity, vulnerability-management and software-security experience. Current roles may use different requirements, so applicants must rely on the active job description.
Employers commonly look for a combination of:
- Professional information security or cybersecurity experience
- Software development or engineering knowledge
- Application, product or cloud security experience
- Vulnerability assessment and remediation work
- Experience using security tools
- Understanding of secure development practices
- Ability to communicate with engineering teams
- Experience leading or coordinating security initiatives
- Relevant degree, training or equivalent practical experience
Do you need a cybersecurity degree?
Some employers request a bachelor’s degree in cybersecurity, computer science, engineering or a related discipline. Others accept equivalent professional experience.
A degree can help, but experienced applicants may also demonstrate readiness through software-development work, security engineering projects, recognized certifications, vulnerability research or practical product-security experience.
Do certifications help?
Certifications can support an application when they match the role, but they rarely replace hands-on experience for senior engineering positions.
Depending on the specialization, employers may recognize certifications connected with information security, cloud security, application security, ethical hacking or secure software development. Only include current certifications you have actually earned.
Can experience from another cybersecurity area transfer?
Security operations, penetration testing, cloud security, software engineering, quality assurance and infrastructure engineering can provide transferable experience.
Your application should explain the connection. For example:
- A software engineer may emphasize secure coding and code review.
- A penetration tester may highlight vulnerability validation and remediation guidance.
- A cloud engineer may show experience protecting deployment pipelines and infrastructure.
- A security analyst may demonstrate vulnerability management and incident knowledge.
Do not assume the recruiter will automatically understand how your previous title relates to product security. Make the relationship clear through achievements and examples.
End of Part 1A: Continue with Part 1B for resume preparation, interview guidance, current job-search steps, Zebra’s official careers pathway and the closing application plan.
How to Prepare an Information Security Engineer Resume
A strong security engineering resume should show how you reduced risk, improved development practices and worked with technical teams. A long list of tools is not enough. Recruiters need to understand what you protected, which problems you solved and how your work affected software, systems or customers.
Write a focused professional summary
Your opening summary should identify your security specialization, level of experience and strongest relevant capabilities. For example, a product security applicant might emphasize secure software development, vulnerability management, application security testing and collaboration with engineering teams.
Avoid generic statements such as “cybersecurity professional seeking a challenging opportunity.” Use the summary to explain why you match the specific vacancy.
Show measurable security outcomes
Where accurate and appropriate, include achievements such as:
- Reduced the number of critical vulnerabilities reaching production
- Improved remediation time for high-risk findings
- Integrated security testing into development pipelines
- Reviewed applications, products or codebases for security weaknesses
- Reduced false positives from automated security tools
- Created secure coding guidance used by engineering teams
- Supported successful product releases or security assessments
- Automated repetitive vulnerability-management tasks
- Coordinated remediation across multiple development teams
Numbers can strengthen an achievement when they are truthful and do not reveal confidential information. For example, “introduced dependency scanning across 20 repositories and reduced unresolved critical findings” provides more context than “responsible for vulnerability scanning.”
Connect tools to practical work
Security resumes often contain long tool lists. Instead of relying only on a skills section, connect important tools to actual achievements.
Rather than writing only “SAST, DAST and SCA,” explain how you configured, evaluated or integrated those capabilities. Employers may want to know whether you can operate a tool, interpret its findings and help developers resolve confirmed risks.
Highlight software and engineering collaboration
Product security work requires influence. Include examples showing how you worked with software engineers, architects, DevOps professionals, product managers or quality-assurance teams.
Useful evidence may include:
- Leading threat-modelling sessions
- Reviewing product architecture
- Advising developers about secure design
- Creating remediation guidance
- Supporting security champions
- Introducing security gates into release processes
- Explaining risk to technical and non-technical stakeholders
Tailor the resume to the specialization
A resume for a Product Security Engineer should not be identical to one submitted for a Security Operations Engineer or Governance, Risk and Compliance role.
Prioritize the experience most relevant to the active job description. For a software-security position, this may include code review, application testing, secure development and CI/CD controls. For a cloud-security role, architecture, identity, configuration and infrastructure automation may deserve greater emphasis.
Use keywords accurately
Relevant phrases may include application security, product security, secure software development lifecycle, vulnerability management, DevSecOps, CI/CD security, threat modelling and secure coding.
Only use terms that reflect your experience. Keyword stuffing may help a resume contain more phrases, but it can weaken credibility when the candidate cannot discuss those skills during a technical interview.
Make Your Cybersecurity Experience Discoverable
Create or update your WorkinVirtual resume with accurate security skills, technical projects, certifications and measurable achievements. Make your location and remote-work eligibility clear.
Upload Your ResumeInterview and Technical Assessment Preparation
Information Security Engineer interviews may include recruiter screening, technical discussions, scenario-based questions, coding or scripting exercises and conversations with software or product teams.
The exact format depends on the employer and specialization. Prepare to explain both technical decisions and how you work with other people.
Prepare a vulnerability-management example
Choose a situation in which you identified or received a security finding, assessed its severity and helped coordinate remediation.
Explain:
- How the issue was discovered
- How you confirmed whether it was genuine
- How you assessed risk and business impact
- Which teams needed to participate
- How remediation was prioritized
- How you verified the final correction
A strong response demonstrates judgement rather than simply naming the scanner used.
Expect secure-development questions
An interviewer may ask how you would introduce security into a development team that releases software frequently. Discuss practical controls such as design review, developer education, automated testing, code review and risk-based release decisions.
Avoid suggesting that every finding must stop every release. Employers often assess whether you can distinguish critical risks from lower-priority issues and recommend proportionate action.
Prepare to discuss false positives
Automated security tools can produce inaccurate or low-value results. Be ready to explain how you validate findings, tune tools, document decisions and prevent developers from losing confidence in the security process.
Review coding and application-security fundamentals
Depending on the position, technical interviews may cover:
- Authentication and authorization
- Input validation
- Injection vulnerabilities
- API security
- Encryption and key management
- Dependency risk
- Secrets management
- Logging and monitoring
- Secure session handling
- Threat modelling
Senior candidates should be able to connect these concepts with practical engineering decisions rather than provide definitions only.
Possible interview questions
- How would you prioritize several critical vulnerabilities across different products?
- How do you introduce security into a CI/CD pipeline?
- Tell us about a disagreement with a development team over a security risk.
- How do you determine whether a scanner finding is exploitable?
- What steps would you take after receiving an external vulnerability disclosure?
- How do you balance product deadlines with security requirements?
- How would you improve secure coding practices across multiple teams?
- What information do you need before assigning severity to a vulnerability?
Questions to ask the employer
- Which products or systems will this role support?
- How is product security organized within the company?
- Which development teams will the engineer work with?
- What security testing is already integrated into the pipeline?
- How are vulnerabilities prioritized and tracked?
- Is the role primarily advisory, hands-on or both?
- What does success look like during the first six months?
- What location, travel or working-hour requirements apply?
How to Find Current Remote Information Security Engineer Jobs
Do not rely on the original vacancy’s application button. Search for current openings and confirm every opportunity through the employer’s official recruitment source.
Search related titles
Employers use different names for overlapping security responsibilities. Search for:
- Remote Information Security Engineer
- Remote Cybersecurity Engineer
- Product Security Engineer
- Software Security Engineer
- Application Security Engineer
- DevSecOps Engineer
- Cloud Security Engineer
- Vulnerability Management Engineer
Combine the role with your specialization
More focused searches may include remote product security jobs, application security engineer remote, secure software development jobs, DevSecOps security jobs and vulnerability management engineer remote.
Verify what “remote” means
A remote vacancy may still be limited to particular states, countries or time zones. Some roles may require occasional office attendance, customer travel or participation in an on-call schedule.
Before applying, confirm:
- Eligible hiring locations
- Work-authorization requirements
- Required working hours or time-zone overlap
- Travel or office expectations
- On-call responsibilities
- Whether the role is fully remote or hybrid
Evaluate the required seniority
Job titles such as “Advanced,” “Senior,” “Lead” and “Principal” can represent different expectations at different employers. Review the responsibilities, decision-making authority and required experience rather than relying on the title alone.
A senior product security role may require the ability to lead programs, influence engineering teams and make risk decisions. Someone with limited direct experience may be better aligned with an associate, professional or mid-level opening.
Visit Zebra Technologies’ official careers page
Zebra Technologies’ official careers site organizes opportunities across areas including engineering and technology, corporate functions, sales, services, supply chain and operations. Applicants interested in Zebra should use that source to confirm whether a relevant security role is currently open. :contentReference[oaicite:0]{index=0}
Visit Official Zebra Technologies Careers
Review compensation carefully
The historical vacancy advertised $120,400–$180,600 annually, but that range should not be generalized to every remote cybersecurity job.
Compensation may depend on:
- Job level
- Hiring location
- Technical specialization
- Years of relevant experience
- Leadership responsibilities
- Bonus or equity eligibility
- Employer size and industry
Review the active salary disclosure where available and ask the recruiter whether the stated range represents base salary, total cash compensation or total compensation.
Practical Next Steps
Remote Information Security Engineer jobs can be a strong fit for cybersecurity professionals who combine technical depth with the ability to influence software, product and engineering decisions.
Before applying:
- Confirm that the vacancy remains active on the official employer site.
- Determine whether the role focuses on product, application, cloud or infrastructure security.
- Check location, work-authorization and remote-work requirements.
- Compare your experience with the essential qualifications.
- Tailor your resume around relevant security outcomes.
- Prepare examples involving vulnerabilities, secure development and cross-functional work.
- Review the employer’s products and technical environment.
- Apply through a verified recruitment portal.
Applicants without a formal cybersecurity title should focus on relevant experience from software development, cloud engineering, penetration testing, quality assurance, infrastructure or security operations.
Applicants who are not yet ready for a senior product-security position may consider Security Analyst, Junior Application Security Engineer, Vulnerability Analyst, DevSecOps Engineer or Software Engineer roles with security responsibilities as realistic progression routes.
Continue Your Remote Cybersecurity Job Search
Browse current WorkinVirtual opportunities and compare each employer’s technical requirements, location rules and official application process before submitting your resume.
Explore Remote Career OpportunitiesEditorial note: WorkinVirtual does not represent Zebra Technologies and cannot confirm that the original Advanced Information Security Engineer vacancy remains available. Current jobs, compensation, benefits, locations and work arrangements may change. Always verify information through the employer’s official careers portal before applying.