Mercor2 дня назад

Cloud Platform Engineer (SF)

Зарплата не указана

РЫНОК

15 167 ₽медиана по профессии

Cloud Engineer · 40 вакансий с указанной зарплатой

5 233половина предложений: 9 708–18 66472 708

Работодатель не указал зарплату — сравните с рынком сами.

Полная занятостьОфис

Обязанности

01Own Mercor's identity infrastructure — Okta configuration and provisioning — managed as code in Terraform rather than clicked through a console
02Design and implement SCIM integrations across our SaaS stack, automating user provisioning and deprovisioning
03Own identity planning and architecture as we scale: access models, group strategy, and how entitlements evolve from hundreds to thousands of employees
04Own cloud account structure, IAM roles, and permission boundaries across AWS, GCP, Azure, and Vercel, keeping access least-privilege as the org grows
05Build and maintain Terraform for internal platforms so environments are reproducible and every change is reviewable
06Build automation that cuts manual ticket volume for employee onboarding and offboarding
07Design and own secrets management, key rotation, and service-account lifecycle
08Troubleshoot identity and infrastructure issues, trace root causes, and implement systemic fixes
09Document platform architecture, runbooks, and automation so the team can operate and extend it
10Mentor future IT team members on infrastructure-as-code, automation practices, and systems thinking
11Help establish sustainable escalation procedures as the team grows

01Hands-on production experience with Terraform, managing real infrastructure as code
02Production experience with Okta and SCIM integrations — ideally managed declaratively
03Strong skills with IAM roles and permissions across at least two major cloud platforms — AWS, GCP, or Azure — with Vercel a plus
04Proficiency in at least one programming language with demonstrated understanding of core coding principles
05Experience building automated workflows across systems via APIs
06Strong incident management skills: triage, root-cause analysis, and systems thinking
07Strong documentation skills — able to write technical guides other team members can follow and learn from
08Clear communication skills — able to explain technical identity and infrastructure concepts to non-technical stakeholders
09A systems-thinking mindset that naturally traces dependencies and considers second-order effects