Cloud Architect II

Job Description

About the Company

\n

Headquartered in Hillside, IL, Cognesense is a worldwide environmental technology company built through the combination of heritage brands, including L&J Technologies, Shand & Jurs, Varec, Sonitus Systems, Petrel, Ex-tech, Pyroban, and Pyropress, that together represent over a century of domain expertise. Under the positioning “Measure. Monitor. Protect.,” Cognesense delivers measurement and instrumentation, safety equipment, automation, and software (including its Clairvoyance and FuelsManager® platforms) to customers in over 100 countries across energy production and storage, chemicals and pharmaceuticals, water and wastewater, aviation fuel, aerospace and defense, food and beverage, and other regulated, high-stakes end markets.

\n

\n

About the Role

\n

The Cloud Architect II owns the AWS architecture behind Clairvoyance, Cognesense's IoT platform, from device connectivity on AWS IoT Core through data ingestion into the lakehouse. You decide how our products are deployed, secured, scaled, and operated in the cloud, and you are the primary point of technical authority on AWS decisions and trade-offs. The outcome the business needs: the current product runs reliably, securely, and cost-effectively on AWS today, and the next-generation platform is cloud-native from the start, with a security and compliance posture that enterprise and government customers can trust.

\n

\n

Position Responsibilities

\n

Cloud Architecture and Roadmap

\n

\n
• Own the AWS cloud architecture and roadmap for Clairvoyance, including device connectivity on AWS IoT Core and data ingestion into the lakehouse.

\n

• Lead the deployment, enhancement, and ongoing operation of the existing product on AWS, including migration and re-platforming, so it performs reliably at scale.

\n

• Shape the cloud architecture of the next-generation platform so sound cloud-native design is built in from the start, not retrofitted.

\n

• Act as the primary technical authority on AWS decisions, laying out trade-offs clearly so engineering, product, and leadership can decide with confidence.

\n

\n

Security, Identity, and Compliance

\n

\n
• Own and evolve landing zones, networking, identity, and security architecture on AWS, aligned to least-privilege and defense-in-depth principles.

\n

• Set a security and compliance posture appropriate for enterprise and government customers, partnering with Security on controls, audits, and customer requirements.

\n

\n

Automation and Delivery

\n

\n
• Establish Infrastructure-as-Code, CI/CD, and automated deployment pipelines so every release is repeatable and auditable.

\n

• Champion an AI-assisted, automation-first approach across cloud delivery and operations, removing manual steps wherever they add risk or delay.

\n

\n

Reliability, Operations, and Cost

\n

\n
• Own cloud reliability and operations, including observability, monitoring, incident response, backup and disaster recovery, and Well-Architected reviews.

\n

• Drive cloud cost management and optimization through right-sizing, scaling strategy, and FinOps practices, so spend tracks the value it delivers.

\n

\n

Technical Leadership and Collaboration

\n

\n
• Provide hands-on technical leadership and mentorship to engineers, raising the team's cloud skills through pairing, guidance, and example.

\n

• Review designs and implementations against cloud standards, catching risk early and explaining the why behind each standard.

\n

• Collaborate across engineering, product, and operations so cloud decisions support product goals and customer commitments.

\n

\n

\n

How We Measure Success

\n

In your first year, great performance looks like this:

\n

\n
• Platform reliability: Clairvoyance cloud services meet agreed availability and performance targets, with incidents detected early and resolved quickly.

\n

• Cloud roadmap delivery: A documented AWS architecture and roadmap is in place, with migration and re-platforming milestones for the existing product delivered on plan.

\n

• Automated, auditable releases: Infrastructure is defined as code and production deployments run through automated CI/CD pipelines, with manual changes trending toward zero.

\n

• Security and compliance posture: Landing zones, identity, and network controls meet least-privilege standards, and enterprise and government customer security reviews pass without major findings.

\n

• Cloud cost efficiency: Cloud spend is visible by service and product, and cost per unit of workload trends down quarter over quarter.

\n

• Resilience: Backup and disaster recovery plans are documented and tested, and Well-Architected review findings are tracked to closure.

\n

• Team capability and trust: Engineers and product partners seek out your guidance, and the team's cloud skills and design quality visibly improve.

\n

\n

\n

Required Qualifications

\n

\n
• Bachelor's degree in computer science, IT, or a related discipline, with 10+ years of software or infrastructure experience, including significant time as a cloud or solutions architect.

\n

• Deep, hands-on AWS expertise designing, deploying, and operating production workloads across core services: compute, storage, networking, databases, identity, and security.

\n

• Proven experience deploying and operating enterprise applications on AWS, including migrating or re-platforming existing applications to the cloud.

\n

• Background with .NET / C# application environments, with the credibility to architect cloud solutions for, and alongside, product engineering teams.

\n

• Infrastructure-as-Code expertise (e.g., Terraform, CloudFormation, or CDK) and mature CI/CD practices.

\n

• Containerization and orchestration on AWS (Docker, ECS and/or EKS).

\n

• Cloud networking, identity, and security: VPC design, IAM, secrets management, and encryption.

\n

• Cloud reliability and operations: observability, monitoring, incident response, and backup/disaster recovery.

\n

• Cloud cost management: right-sizing, scaling strategy, and FinOps discipline.

\n

• Experience embedding with delivery teams in an Agile environment.

\n

• Excellent communication skills, with the ability to align engineering, product, security, and leadership around cloud decisions and trade-offs.

\n

\n

\n

Preferred Qualifications

\n

\n
• AWS & cloud depth: AWS IoT Core experience (MQTT, device provisioning, fleet management) or similar device-telemetry platforms.

\n

• AWS & cloud depth: high-volume streaming and time-series data on AWS (Kinesis, Lambda, Timestream, or similar).

\n

• AWS & cloud depth: data lakehouse platforms, including feeding operational data into analytics and AI.

\n

• AWS & cloud depth: AWS certifications such as Solutions Architect Professional, DevOps Engineer, or Security Specialty.

\n

• AWS & cloud depth: AWS Well-Architected Framework reviews and remediation.

\n

• AWS & cloud depth: hybrid and on-prem-to-cloud architectures and migration patterns.

\n

• AWS & cloud depth: database experience on AWS, including RDS/PostgreSQL, SQL Server, and data migration.

\n

• AWS & cloud depth: event-driven and messaging patterns on AWS and in modern platforms.

\n

• AWS & cloud depth: DevSecOps and compliance automation, including policy-as-code and security scanning in pipelines.

\n

• AI-assisted delivery: experience leading AI-assisted, automation-first delivery and operations (e.g., Claude Code, GitHub Copilot, and agentic workflows).

\n

• Domain & security: industrial / OT domain exposure such as SCADA, IIoT, fuel or bulk-liquids management, or similar.

\n

• Domain & security: government or regulated-industry cloud experience, such as AWS GovCloud, FedRAMP, or similar compliance regimes.

\n

• Domain & security: an active IAM Level II (or higher) compliant IA certification, such as CISSP, CASP+ CE, CISM, CCISO, or equivalent per DoD 8570/8140.

\n

• Domain & security: awareness of OT/industrial security standards (e.g., IEC 62443) and secure-by-design practices.

\n

\n

\n

How You Work

\n

\n
• You take ownership of the platform end to end and act before problems reach customers.

\n

• You explain technical trade-offs in plain language and build trust across engineering, product, security, and leadership.

\n

• You stay hands-on and lift the people around you through mentorship and thoughtful design review.

\n

• You are curious about AI and automation and look for ways to remove manual work from delivery and operations.

\n