Back to jobs
Stryker10K+ employees

Staff Cloud DevSecOps Engineer

Orlando, FLSalary not listedPosted 3 days ago

Immigration summary

Visa sponsorship

LikelyMedium confidence

This employer has recently sponsored work like this.

72 recent H-1B filings

View visa evidence

Green card sponsorship

Strong historyHigh confidence

This employer has recently sponsored green cards at scale.

25 recent certified PERM filings · 7 similar-role filings

View green card evidence

Job description

Work Flexibility: Remote

What You Will Do:

The Cloud DevSecOps Engineer is responsible for keeping our multi-cloud platform fast, reliable, and transparent. This position will own the monitoring stack, automate incident response, and drive performance and cost optimization across production AWS/GCP workloads. Acting as the bridge between engineering, product, and compliance teams, the Cloud Operations and Observability Engineer will surface actionable insights and ensure compliance with relevant SOC 2 controls.

  • Design and maintain secure cloud foundations and shared platform services, including landing zones, IAM/service accounts, workload identity/OIDC, secrets management, network/security controls, and reusable Terraform modules.
  • Partner with DevOps and application teams to enable secure golden-pipeline deployments, troubleshoot infrastructure blockers, and ensure cloud services are provisioned through standardized, repeatable patterns.
  • Implement and maintain cloud security guardrails and policy-as-code, including controls such as Cloud Armor/WAF, least-privilege IAM, secrets rotation, vulnerability remediation, and infrastructure configuration standards.
  • Design, deploy, and maintain observability stacks (Prometheus/Grafana, CloudWatch, Stackdriver, Datadog, or similar)
  • Build and manage CI/CD pipelines and infrastructure-as-code (Terraform, CloudFormation, Pulumi)
  • Automate incident response with runbooks, chat-ops, and auto-remediation scripts (e.g., Lambda, Cloud Functions)
  • Ensure logging, alerting, and backup configurations meet SOC 2 / ISO 27001 controls
  • Document evidence for audit requests (access reviews, vulnerability scans, disaster-recovery drills)
  • Participate in weekly on-call rotation (pager duty) and drive blameless incident retrospectives

What You Will Need:

Required Qualifications:

  • Bachelor’s degree in Computer Science, Engineering, or related field
  • 4+ years professional experience in cloud operations, SRE, or DevOps roles
  • Hands-on experience with at least one major cloud provider (AWS, GCP, or Azure)
  • Proficiency in scripting or programming (Python, PowerShell, Bash, or similar)
  • Experience deploying and supporting monitoring/alerting platforms (Prometheus, Datadog, Grafana, New Relic, etc.)

Preferred Qualifications:

  • Experience with enterprise IAM, workload identity/OIDC, secrets management, cloud security controls, and Terraform-based landing-zone/platform engineering.
  • Certifications: AWS SysOps Administrator, Google Cloud DevOps Engineer, or Azure Administrator Associate
  • Familiarity with Kubernetes, service mesh, and distributed tracing (Jaeger, OpenTelemetry)

United States of America Pay Ranges:

  • USN: $102,600 - $171,000 USD Annual
  • US5: $107,700 - $179,600 USD Annual
  • US10: $112,900 - $188,100 USD Annual
  • US15: $118,000 - $196,600 USD Annual
  • US20: $123,100 - $205,200 USD Annual
  • US30: $133,400 - $222,300 USD Annual

View the U.S. work location and transparency guide to find the pay range for your location.

Travel Percentage: 10%

Stryker Corporation is an equal opportunity employer. Qualified applicants will receive consideration for employment without regard to race, ethnicity, color, religion, sex, gender identity, sexual orientation, national origin, disability, or protected veteran status. Stryker is an EO employer – M/F/Veteran/Disability.

Stryker Corporation will not discharge or in any other manner discriminate against employees or applicants because they have inquired about, discussed, or disclosed their own pay or the pay of another employee or applicant. However, employees who have access to the compensation information of other employees or applicants as a part of their essential job functions cannot disclose the pay of other employees or applicants to individuals who do not otherwise have access to compensation information, unless the disclosure is (a) in response to a formal complaint or charge, (b) in furtherance of an investigation, proceeding, hearing, or action, including an investigation conducted by the employer, or (c) consistent with the contractor’s legal duty to furnish information.

Sponsorship evidence

Why Openbound reached the conclusions above.

Visa sponsorship evidence

Current posting

Silent on sponsorship

Employer H-1B history

72
recent certified H-1B filings
27
new-hire petitions
0
filings for similar roles
51
so far in FY2026

Filed titles like this role: software engineer · quality engineer · software test engineer · advanced quality engineer

More evidence details
  • 25 certified H-1B filings for closely related roles, though none for this exact title
  • 72 recent certified H-1B filings across the employer
  • Still filing this year — 51 filings in FY2026
  • 34 USCIS H-1B new-employment approvals, counted separately from LCA filings
  • Some filing activity in FL
  • 176 further USCIS approvals for extensions or transfers
  • The supporting filings are for related work, not for this exact role
  • The posting says nothing about sponsorship either way

Some filing activity in FL.

Green card sponsorship evidence

Employer PERM history

25
recent certified PERM filings
7
filings for similar roles
2
filings in this location
Certified PERM filings by fiscal year
202324
202413
202533
202615YTD

Filing history reflects past employer behavior; it isn't a promise for this opening.

All open roles at Stryker
How Openbound evaluates sponsorship

Visa history uses official U.S. Department of Labor H-1B LCA disclosure data and USCIS H-1B petition history. Green card history uses DOL PERM disclosure data. Each is read for the employer as a whole, for roles like this one, and for this location, weighted toward the most recent fiscal years.

An employer is matched to its filing entities by verified legal name and reviewed aliases; a match is never made on a name resemblance alone. Where no verified entity can be matched, the page says so and draws no conclusion from the absence. 140 filing titles were examined for this employer.

What this posting states outranks history in both directions, and an employer's published policy outranks past filings. Filing history reflects past behavior; it is not a promise of sponsorship for this opening, and none of this is legal advice.