2

Remote Wiki Jobs in Georgia (NOW HIRING)

Remote Wiki information

What is the difference between Remote Wiki vs Remote Content Writer?

AspectRemote WikiRemote Content Writer
Primary RoleCreating and maintaining collaborative knowledge bases and internal documentationProducing written content for websites, blogs, and marketing materials
Required SkillsKnowledge management, technical writing, collaboration toolsWriting, editing, SEO, research
Work EnvironmentOnline platforms, collaborative tools, internal teamsFreelance or in-house, client or company websites
Common CertificationsTechnical writing certifications, knowledge management coursesContent marketing, SEO certifications, writing courses

Remote Wiki and Remote Content Writer roles both involve strong writing skills and online work environments. However, Remote Wiki focuses on creating and managing internal or public knowledge bases, while Remote Content Writers produce marketing and web content. Understanding these differences helps job seekers target the right opportunities in the remote work landscape.

What are some common challenges faced by remote wiki editors and how can they overcome them?

Remote wiki editors often encounter challenges such as maintaining clear communication with team members and ensuring content consistency across distributed contributors. To overcome these issues, it's important to establish regular check-ins, use collaborative tools (like shared documents and messaging platforms), and adhere to well-defined style guides. Setting up version control and review processes also helps minimize conflicts and ensures quality. Staying organized and proactive in communication makes remote collaboration more efficient and enjoyable.

What are Remote Wiki jobs?

Remote Wiki jobs involve creating, editing, and managing content on online wiki platforms from a remote location. These roles often require strong research, writing, and collaboration skills since the work typically involves gathering accurate information and presenting it clearly for a wide audience. Remote Wiki professionals may work for organizations maintaining internal knowledge bases or contribute to public wikis like Wikipedia. The flexibility of remote work allows contributors to collaborate with global teams and manage their own schedules.

What are the key skills and qualifications needed to thrive as a Remote Wiki Editor, and why are they important?

To thrive as a Remote Wiki Editor, you need strong research abilities, excellent writing skills, and familiarity with wiki markup or content management systems, usually supported by experience in content creation or editing. Proficiency in tools like MediaWiki, Confluence, or other collaborative documentation platforms is typically required. Attention to detail, self-motivation, and effective communication are crucial soft skills for excelling in a remote and collaborative environment. These skills ensure accurate, well-organized, and up-to-date information is maintained, supporting team productivity and knowledge sharing.
What are the most commonly searched types of Wiki jobs in Georgia? The most popular types of Wiki jobs in Georgia are:
Infographic showing various Remote Wiki job openings in Georgia as of July 2026, with employment types broken down into 85% Full Time, 10% Part Time, 1% Temporary, and 4% Contract. Highlights an 50% Physical, 4% Hybrid, and 46% Remote job distribution.

Google Cloud Platform - Engineering Manager

Huntington

Atlanta, GA โ€ข On-site, Remote

$53.75 - $71.75/hr

Other

Medical, Life, Retirement, PTO

Posted 2 days ago


Job description

Description Job Summary The Cloud Engineering Manager provides technical leadership and people management for a team responsible for designing, building, and operating scalable, secure, and highly available cloud platforms. This role combines handson cloud architecture expertise, Infrastructure as Code, and DevSecOps practices with strong coaching, mentoring, and delivery leadership. The Cloud Engineering Manager partners closely with application teams, security, and enterprise architecture to ensure cloud solutions align with organizational standards, targetstate architecture, and business outcomes.

Key Responsibilities Technical Leadership & Architecture Define and evolve cloud architecture standards, patterns, and reference implementations across public, private, and hybrid environments. Lead the design and review of cloudnative solutions across IaaS, PaaS, and containerized platforms. Ensure platforms and applications are designed for high availability, resilience, scalability, and disaster recovery.

Act as a subjectmatter expert for cloud networking, provisioning, automation, and platform services. Evaluate new cloud services, tools, and architectural approaches, providing clear recommendations with tradeoffs. Cloud Engineering & DevSecOps Lead the adoption and governance of Infrastructure as Code using tools such as Terraform, ARM, CloudFormation, or equivalent.

Drive DevSecOps practices, including CI/CD pipelines, automated testing, security scanning, and policyascode. Ensure secure handling of credentials, certificates, encryption, and key rotation. Partner with security teams to embed riskbased controls and compliance into cloud platforms.

Partner with risk, security, compliance, and audit teams to support internal and external exams. Guide costefficient cloud usage, including monitoring, optimization, and financial transparency. People Management & Mentorship Manage, mentor, and develop a team of cloud platform and Site Reliability engineers.

Foster a culture of technical excellence, ownership, and continuous improvement. Provide coaching, career development guidance, and regular performance feedback. Build and maintain a highperforming, collaborative engineering team.

Strategy & Collaboration Align cloud engineering initiatives with enterprise architecture and business strategy. Partner with application, product, and infrastructure teams to support mergers, migrations, modernization, and new product delivery. Communicate architectural decisions, standards, and roadmaps clearly to both technical and nontechnical stakeholders.

Contribute to the organization's longterm cloud vision and platform roadmap. Required Qualifications Bachelor's degree in Computer Science, Engineering, or a related field (or equivalent experience). 10+ years of experience across multiple IT disciplines such as cloud architecture, application development, infrastructure, or operations.

Handson experience designing and operating workloads on at least one major public cloud platform. Strong experience with Infrastructure as Code and automated cloud provisioning. Design and governance of reusable IaC modules published via private registries and consumed through CI/CD pipelines.

Experience leading or contributing to DevSecOps toolchains and practices. Solid understanding of cloud networking, security, identity, and access management. Proven ability to lead teams and influence across organizational boundaries.

Preferred Qualifications Google Cloud Platform (GCP) as the primary cloud provider. Terraform or OpenTofu as the standard InfrastructureasCode tools. Harness Software Delivery Platform used for CI/CD, infrastructure provisioning.

GitHub as the primary source code repository. Azure DevOps Services (ADO) boards, wiki, etc. Cloud architecture or engineering certifications.

Experience in regulated or financialservices environments. Knowledge of containers, Kubernetes, and serverless architectures. Experience with application and infrastructure monitoring and observability tools.

Background in application modernization, migration strategies, or platform engineering. Prior experience as a technical lead or engineering manager. What Success Looks Like Cloud platforms are reliable, secure, scalable, and easy for application teams to consume.

Engineering teams deliver faster through automation and standardized patterns. Cloud costs, security posture, and operational health are transparent and wellmanaged. Engineers are growing, engaged, and aligned with the organization's cloud strategy.

Exempt Status: (Yes = not eligible for overtime pay) (No = eligible for overtime pay) Yes Workplace Type: Office Our Approach to Office Workplace Type Certain positions outside our branch network may be eligible for a flexible work arrangement. We're combining the best of both worlds: in-office and work from home. Our approach enables our teams to deepen connections, maintain a strong community, and do their best work.

Remote roles will also have the opportunity to come together in our offices for moments that matter. Specific work arrangements will be provided by the hiring team. Compensation Range: 93,000.00 - 189,000.00 USD Annual The compensation range represents the anticipated low and high end of the base compensation range for this position

Actual compensation will vary based on various factors including but not limited to location, experience, and education. Colleagues in this position are also eligible to participate in an applicable incentive compensation plan. In addition, Huntington provides a variety of benefits to colleagues, including health insurance coverage, wellness program, life and disability insurance, retirement savings plan, paid leave programs, paid holidays and paid time off (PTO).

Huntington is an Equal Opportunity Employer. Tobacco-Free Hiring Practice: Visit Huntington's Career Web Site for more details. Note to Agency Recruiters: Huntington will not pay a fee for any placement resulting from the receipt of an unsolicited resume.

All unsolicited resumes sent to any Huntington colleagues, directly or indirectly, will be considered Huntington property. Recruiting agencies must have a valid, written and fully executed Master Service Agreement and Statement of Work for consideration. Apply.