Cloud Engineer — Cloud & Platform Engineering, Signisys

Build and run the cloud infrastructure our clients bet their business on. You’ll design landing zones, migrate workloads, automate everything you touch, and keep production systems fast, secure, and cost-efficient across AWS and Azure. If you’d rather ship well-engineered infrastructure than talk about it, this is the seat for it.

About the Role

• You’re the engineer clients and account teams call when infrastructure needs to be designed right the first time — not patched later.
• Your week moves between architecture, hands-on build, and troubleshooting — often across two or three client environments at once.
• No two engagements look the same. One week it’s a landing zone for a new client; the next, a migration cutover, a cost-optimization sprint, or a 2 a.m. production incident.
• You’ll work directly with senior architects and, as you grow, start owning client-facing design conversations yourself.
• This is a practice-building role. Strong performers move into Senior Cloud Engineer or Cloud Architect within 18–24 months.

What You’ll Do

• Design and build cloud infrastructure — landing zones, VPC/VNet architecture, IAM, networking, and security baselines on AWS and Azure.
• Own migrations end-to-end. Take a client’s on-prem or legacy cloud estate and move it to a modern, well-architected environment with minimal downtime.
• Automate the environment. Write Infrastructure-as-Code (Terraform, CloudFormation, ARM/Bicep) so nothing gets built by hand twice.
• Build and maintain CI/CD pipelines that get client teams shipping faster without breaking things.
• Run FinOps basics — right-sizing, reserved capacity, tagging hygiene — so client cloud bills reflect actual usage, not sprawl.
• Handle production support and incident response for managed clients, including root-cause write-ups the account team can hand to the customer.
• Document architecture decisions clearly enough that another engineer — or the client’s own team — can pick up where you left off.
• Contribute to proposals and SOWs when pre-sales needs a technical voice on scoping and estimation.

What You Bring

Must-Haves

• 2–4 years building and operating production infrastructure on AWS and/or Azure.
• Solid Infrastructure-as-Code experience — Terraform preferred, CloudFormation or ARM/Bicep acceptable.
• Comfortable in Linux, networking fundamentals (VPC/VNet, DNS, load balancing), and at least one scripting language (Python or Bash).
• CI/CD pipeline experience — GitHub Actions, GitLab CI, Azure DevOps, or similar.
• Clear writing. You can turn an architecture decision into a doc a client’s IT lead will actually read.
• Comfortable owning a problem without a playbook — client environments rarely match the diagram.

Nice-to-Haves

• AWS or Azure certification (Solutions Architect, DevOps Engineer, or equivalent).
• Exposure to Kubernetes/container orchestration.
• Prior consulting or systems-integrator experience, where you’ve worked across multiple client stacks.
• Familiarity with cost-management tooling (AWS Cost Explorer, Azure Cost Management, CloudHealth, or similar).

Why Join Us

What you’ll get

• Real ownership — you’ll be the engineer of record on client environments, not a ticket-queue resource.
• Breadth most single-company roles can’t match: multiple industries, both major clouds, greenfield and legacy work.
• Cash, meaningful learning budget, and a clear path to Senior Engineer / Architect.
• Small team. Low politics. Your work is visible from week one.

What to expect

• On-call rotation for managed clients — that’s part of the job, not an exception.
• Context-switching across client environments, sometimes within the same day.
• Deadline-driven weeks around migrations and cutovers.
• Occasional client-site travel.

Growth & Career Path

• Months 0–3: Ramp on Signisys delivery standards, shadow a senior engineer on live client work, take ownership of a scoped workstream.
• Months 4–12: Own a client environment end-to-end — architecture, automation, and support — and start joining client design conversations directly.
• Months 12–24: Move into Senior Cloud Engineer or Cloud Architect, or specialize deeper into a practice area (FinOps, DevOps/SRE, or a specific cloud).

Location & Working Style

Based out of Signisys’s primary office, in person by default with room for focused work-from-home days.

How to Apply

Send us a one-page note and your CV. The note matters more than the CV — tell us about a piece of infrastructure you built or fixed: what you did, what worked, what you’d do differently. We reply within a week.