Cloud Infrastructure & DevOps Engineer

OptionMetrics•New York, NY

1d•$100,000 - $150,000•Onsite

About The Position

OptionMetrics, headquartered in New York, NY, is a dynamic and innovative technology company and a trusted provider of financial information and research derived from the option markets. We are at the forefront of developing solutions that empower businesses. Our commitment to excellence, coupled with a collaborative, forward-thinking culture, has made us the preferred choice for top-tier talent. Our data and analytics models are utilized by over 350 investment banks, hedge funds, asset management firms, and academic institutions globally, solidifying our position as a leader in the industry. Are you ready to own the cloud foundation behind a market-leading financial data business? At OptionMetrics, we're looking for a Senior Cloud Infrastructure & DevOps Engineer to own our multi-account AWS environment, our client-facing file-delivery platform, the deployment pipelines and scheduled workflows that ship our data, and the security controls around all of it. Our clients and internal teams depend on this infrastructure every day. You'll keep it reliable, automate how it runs, and leave it better documented than you found it. You'll report to the Head of IT Operations and work closely with Engineering, Product, Sales and Customer Support.

Requirements

6+ years in cloud or infrastructure engineering, including 4+ years running production AWS.
Deep AWS experience: VPC, Transit Gateway, Client VPN, IAM, SSO, Organizations, ELB/ALB/NLB, ACM, EC2 Auto Scaling, S3, AWS Config and CloudTrail.
Strong Linux administration skills.
Hands-on DevOps experience: CI/CD pipelines, release management, and supporting development teams through deployments.
Experience running a job scheduler or workflow automation platform (Stonebranch/OpsWise, Control-M, Airflow or similar) and troubleshooting failed pipelines.
Production experience with Terraform and CI/CD in GitHub Actions, including OIDC.
Solid grounding in TLS/PKI, DNS (Route53 and external providers) and file transfer over FTP, FTPS, SFTP, SSH and HTTP/HTTPS.
A security mindset: least privilege, WAF and rate limiting, and incident response.
Scripting in Python or Bash.
Clear written and verbal communication: change notices, runbooks and Jira write-ups others can act on.
A track record of delivering on commitments in an environment with frequent interruptions.

Nice To Haves

AWS Certification (Solutions Architect, SysOps or Security).
SRE or platform engineering experience, including SLOs, observability and on-call practice.
Experience with TeamCity, Site24x7 or Opsgenie.
Containers and orchestration (Docker, ECS).
Experience with CrushFTP or other managed file-transfer platforms.
Cloudflare experience (WAF, Turnstile, access rules).
Building AI tooling for operations, such as Claude skills or agents for runbooks and audits.
Experience with CrowdStrike and Active Directory.
Leading a multi-account AWS migration from start to finish.
Experience in financial data or fintech.

Responsibilities

Design, build and operate highly available AWS infrastructure across dev, test, prod and DMZ accounts.
Plan and run production changes with a published change notice covering scope, impact, rollback and confirmation.
Perform and oversee deployments to production and non-production environments, with a release plan, a rollback path and a Jira record for each.
Build, maintain and troubleshoot CI/CD pipelines, and help development teams ship safely and repeatably.
Monitor and tune business-critical scheduled workflows, troubleshoot failures, and drive failed jobs to root cause through the weekly failure review.
Build monitoring, alerting, consolidated metrics and logs that give stakeholders a clear view of system and workflow health.
Respond to infrastructure and security incidents: contain first, then find the root cause and document it in Jira.
Turn repeated manual work into automation using scripts, GitHub Actions, Infrastructure as Code and AI tooling.
Apply least privilege to every access request: expiring SSO roles, and no long-lived keys without a documented use case.
Write and maintain runbooks, architecture and network diagrams, and Confluence standards for everything you own, including legacy systems.
Keep Jira current: every ticket you own shows a status, a blocker or a next step, updated at least every two weeks.
Take ad-hoc requests from Sales, Support and Product. Clarify the need, commit to a date, and deliver.
Coach junior engineers and hand off repeatable work to them with written runbooks.