Senior Cloud Infrastructure Engineer

Job Description

Purpose of This Role

iDENTIFY's ability to deliver secure, reliable data platforms to banking and fintech clients depends on the foundation underneath them. The Senior Cloud Infrastructure Engineer builds and owns that foundation.

This is a delivery role, not support. You design cloud environments from the ground up, automate everything that can be automated, and operate what you build with a security-first mindset—because our clients are regulated institutions where infrastructure failures aren't just operational problems, they're compliance events.

At the senior level, you operate with minimal supervision from design through production. You anticipate infrastructure needs before they're asked for, set standards other engineers work within, and own the reliability of what ships.

Apply here:

Builder + Operator + Security Owner. If the infrastructure fails, the data platform fails. This role doesn't let that happen.

What This Role Owns

Cloud Architecture and Environment Design

iDENTIFY operates across AWS and Azure. Our banking and credit union clients have non-negotiable security and isolation requirements. Architecture decisions must hold up under client security reviews and audit.

• Designs, implements, and maintains cloud infrastructure across AWS and Azure aligned with banking security requirements. Decisions are documented and defensible.
• Builds and manages multi-account, multi-region environments with strong isolation and governance.
• Implements and manages networking components end-to-end: VPCs, subnets, routing, load balancers, private connectivity.
• Anticipates infrastructure requirements for upcoming client engagements and raises them before they become delivery blockers.

Infrastructure as Code and Automation

Manual infrastructure is a liability at iDENTIFY. Every environment must be reproducible, auditable, and maintainable by someone other than the person who built it.

• Develops and maintains Terraform modules for repeatable, auditable infrastructure provisioning—built for reuse across engagements, not just the project in front of you.
• Automates infrastructure lifecycle management. If something is done by hand more than twice, it should be automated.
• Ensures all IaC follows best practices for versioning, reuse, and security. Code is reviewed, not just functional.
• Establishes and documents IaC standards that other engineers build within.

Platform and DevOps Enablement

Infrastructure doesn't exist in isolation. You work directly with data engineers, solution architects, and client DevOps teams to keep the platform solid without slowing them down.

• Builds and supports CI/CD pipelines using GitHub Actions (and GitLab where applicable), treated as production infrastructure.
• Supports containerized workloads and orchestration using Kubernetes (EKS)—comfortable operating them, not just provisioning them.
• Develops event-driven and serverless solutions in Python to support automation, monitoring, and platform integrations.
• Serves as the infrastructure point of contact for engineering and architecture teams during delivery. Proactively surfaces constraints affecting timelines.

Security, IAM, and Compliance

Our clients are regulated financial institutions. Security is the baseline every environment is built to—not a feature added on top.

• Implements and manages IAM roles, policies, and access controls. Least-privilege is the default.
• Configures security best practices: secrets management, encryption at rest and in transit, centralized logging, and anomaly alerting.
• Supports secure data access patterns for Snowflake and related cloud services with the same rigor applied to network controls.
• When a client's security team asks how something is configured, this role can answer precisely.
• Proactively identifies security gaps in existing infrastructure and drives remediation—in client environments and iDENTIFY's own platform.

Operations and Reliability

Building infrastructure is half the job. Keeping it running—and improving it over time—is the other half.

• Monitors infrastructure health using CloudWatch and related observability services. Alerting thresholds are configured thoughtfully, not left at defaults.
• Troubleshoots and resolves infrastructure, deployment, and performance issues with urgency when client environments are affected.
• Participates in incident response and root cause analysis. Fix it, understand it, prevent recurrence.
• Leads post-incident reviews and drives resulting action items to completion. Reliability improvements don't stall after the incident closes.

Client and Team Collaboration

You work directly with client DevOps and engineering teams. Technical credibility must be matched by communication clarity.

• Represents iDENTIFY's infrastructure practice with professionalism and technical authority.
• Raises conflicts between infrastructure requirements and delivery schedules early—before work starts, not after.
• Takes ownership from design through production with minimal supervision.

What We Expect

Experience and Background

This role requires someone who has operated real infrastructure in high-stakes environments—not just built labs or contributed to tickets.

• 8+ years in cloud infrastructure or platform engineering with demonstrated ownership of production environments.
• Deep, hands-on experience with both AWS and Azure—fluent, not familiar. Able to design and troubleshoot complex multi-account environments on either platform without significant ramp time.
• Strong proficiency in Terraform as the default mode of working.
• Solid experience with CI/CD pipeline design, Kubernetes (EKS), and Python-based automation.
• A genuine security mindset: IAM, secrets management, encryption, and logging in regulated or compliance-sensitive environments. Banking or financial services experience is a significant advantage.
• Experience leading infrastructure as the primary owner in client-facing or consulting-style engagements.

How This Person Operates

• Builds for the next engineer. Terraform is readable. Architecture is documented. The person who inherits the work isn't starting from scratch.
• Treats security as their own responsibility. Doesn't wait for a compliance checklist to notice something is misconfigured—notices it and fixes it.
• Communicates constraints clearly and early. When a delivery plan requires something infrastructure can't support safely, says so before work starts.
• Owns incidents through to resolution. Closes the ticket when the underlying cause is understood and addressed—not when the service comes back up.
• Makes the platform more reliable over time. Every incident and near-miss is an opportunity to improve. They take it.

Weekly Rhythm

These are recurring, non-optional commitments:

• Review tasks against timelines; surface blockers to project leads before they escalate.
• Review infrastructure health across active client environments; plan remediation for reliability or security concerns.
• Review open incidents and post-incident action items; ensure nothing stalls after initial resolution.
• Update infrastructure documentation and architecture diagrams in the Data Team Wiki.
• Document and share Lessons Learned from incidents, near-misses, or client discoveries.

A Note on Seniority

The distinction between a Cloud Infrastructure Engineer and a Senior Cloud Infrastructure Engineer at iDENTIFY is about what happens when no one is watching.

A Cloud Infrastructure Engineer executes well-defined work with quality and reliability. A Senior Cloud Infrastructure Engineer identifies what needs to be built before being asked, enforces standards others depend on, and is accountable for the security and reliability posture of what they own—not just the tickets they close.

Our clients are banks and credit unions. When their infrastructure has a problem, it's not just a service interruption—it can be a regulatory event. The stability and security of what you build isn't an engineering metric. It's a client trust metric. Own it.