R Systems
Website:
rsystems.com
Job details:
Position Summary
PowerPlan is looking for a Cloud Engineer to join our Cloud Engineering (CloudOps/SRE) team. This is an entry-level, hands-on role focused on resolving day-to-day operational cases escalated from our Service Ops and Professional Services teams across our AWS and Azure environments. You will provision and manage access to customer environments, execute cutovers, and troubleshoot infrastructure alerts, while building the platform knowledge needed to grow into more advanced cloud engineering and SRE work.
This role is a strong fit for someone early in their cloud career who wants structured, mentored exposure to production AWS and Azure environments in a multi-product SaaS company, with a clear path toward automation, observability, and site reliability engineering.
Core Responsibilities
Case Resolution & Customer Environment Support
- Serve as a front-line responder for cases submitted by Service Ops and Professional Services, spanning access requests, cutovers, and infrastructure alerts.
- Provision, modify, and revoke customer environment access (IAM roles/policies, temporary credentials, VPN or bastion access) following least-privilege and documented approval processes.
- Execute customer environment cutovers (e.g., DNS updates, connection string changes, certificate swaps, environment promotions) using established runbooks.
- Triage infrastructure and application alerts across AWS and Azure, determine likely root cause, and apply the appropriate documented remediation or escalate with clear context.
- Track all case work in Salesforce (or the designated ticketing system), keeping status, notes, and resolution steps current for handoff and audit purposes.
- Escalate complex, ambiguous, or high-risk issues to senior engineers promptly, with a clear summary of what has been checked and ruled out.
Cloud Infrastructure Operations
- Perform routine operational tasks across core AWS services (e.g., EC2, RDS, S3, IAM) and Azure services (e.g., VMs, Azure SQL, Storage, Azure AD) under existing runbooks and standards.
- Assist with monitoring and observability tooling (e.g., CloudWatch, Azure Monitor, Coralogix/StackGen) to confirm alerts are correctly scoped and resolved.
- Support basic environment health checks, credential rotations, and access reviews as directed.
- Maintain and improve internal documentation for recurring case types, keeping runbooks accurate as environments change.
Learning & Continuous Improvement
- Develop working proficiency in scripting (Python, PowerShell, or Bash) to reduce manual steps in repetitive case work.
- Identify recurring, high-volume manual tasks and flag them to senior engineers as automation candidates.
- Participate in knowledge-sharing sessions and shadow senior team members on more complex incidents and cutovers.
- Build growing familiarity with PowerPlan's product portfolio (Classic, AIO, WPA, TFA, NXT, Datahub, Integration Hub) and how each maps to underlying cloud infrastructure.
Required Qualifications
- 1–3 years of experience in a cloud engineering, DevOps, systems administration, or related IT support role.
- Working knowledge of core AWS and/or Azure services (compute, storage, networking, and identity/access management).
- Basic scripting ability in Python, PowerShell, or Bash, or strong motivation to develop it quickly.
- Comfort following detailed technical runbooks precisely, while recognizing and flagging when a situation doesn't match the documented steps.
- Strong troubleshooting instincts and the ability to methodically isolate the cause of an issue.
- Clear written and verbal communication, including the ability to document case work for both technical and non-technical audiences.
- Ability to manage a queue of concurrent cases with varying priority and respond within SLA expectations.
Preferred Qualifications
- Cloud certification such as AWS Certified Cloud Practitioner, AWS SysOps Administrator – Associate, or Microsoft Certified: Azure Fundamentals/Administrator Associate.
- Exposure to Infrastructure-as-Code tools such as Terraform.
- Familiarity with observability or monitoring platforms (e.g., Grafana, Coralogix, CloudWatch, Azure Monitor).
- Basic SQL skills for reviewing data or diagnosing database-related cases.
- Experience supporting a multi-tenant SaaS or enterprise software product.
- Familiarity with ticketing/case management systems such as Salesforce Service Cloud.
What Success Looks Like
First 30 Days
- Complete onboarding, including access provisioning, security training, and introductions to Service Ops, Professional Services, and the Cloud Engineering team.
- Shadow senior engineers on live cases to learn common case types, tools, and escalation paths.
- Develop working familiarity with the core AWS and Azure environments and at least one PowerPlan product line.
First 60 Days
- Independently resolve standard case types (access requests, routine cutovers, common alert patterns) within SLA.
- Demonstrate consistent, accurate case documentation with minimal rework needed from reviewers.
- Identify at least one recurring manual task and propose it as an automation candidate.
First 90 Days
- Handle the full range of standard case types independently, escalating only genuinely complex or novel issues.
- Contribute meaningfully to runbook and documentation improvements based on cases handled.
- Begin contributing basic scripts or tooling that reduce manual effort on at least one recurring case type.
- Be recognized as a reliable point of contact for at least one product area or case category.
Terraform,AWS,Aws Cloud Engineer,Cloud Support,Azure Active Directory,Azure VM
What Success Looks Like
First 30 Days
- Complete onboarding, including access provisioning, security training, and introductions to Service Ops, Professional Services, and the Cloud Engineering team.
- Shadow senior engineers on live cases to learn common case types, tools, and escalation paths.
- Develop working familiarity with the core AWS and Azure environments and at least one PowerPlan product line.
First 60 Days
- Independently resolve standard case types (access requests, routine cutovers, common alert patterns) within SLA.
- Demonstrate consistent, accurate case documentation with minimal rework needed from reviewers.
- Identify at least one recurring manual task and propose it as an automation candidate.
First 90 Days
- Handle the full range of standard case types independently, escalating only genuinely complex or novel issues.
- Contribute meaningfully to runbook and documentation improvements based on cases handled.
- Begin contributing basic scripts or tooling that reduce manual effort on at least one recurring case type.
- Be recognized as a reliable point of contact for at least one product area or case category.
Click on Apply to know more.
