寻找你的下一个职业机会

按职位、技能和地点搜索招聘信息。准备申请前,先仔细了解职位要求。

找到一个吸引人的职位名称只是求职的起点。请将工作职责、招聘要求和工作条件与你的实际经历进行比较。本指南帮助你筛选机会、准备有针对性的申请材料,并确认每份申请应该在哪里提交。

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

清除筛选

搜索结果: 14,064

← 返回搜索结果

Principle Systems Engineer

Altera Digital Health

远程工作

地点
Remote (India)
工作安排
Full Time
发布日期
2026年10月18日

申请前,请在雇主网站确认职位仍在招聘,并检查完整要求和条件。

职位描述

此界面为简体中文。雇主发布的职位名称和描述保留原文,可能为英文。

About the Role We are hiring a Principal Platform Engineer to help build and scale our Azure-native cloud platform as we migrate services from an on-premises data center to the cloud. This is a hands-on engineering role with a strong mentoring component -- you will design and build alongside the team while raising the technical bar for engineers earlier in their careers. You will work across infrastructure, deployment automation, observability, and security tooling, with exposure to both legacy automation modernization and net-new platform capability. This is an individual contributor role. You will not have direct reports, but you will be expected to mentor and provide technical guidance to junior and mid-level engineers on the team, including reviewing designs, pairing on complex problems, and setting technical direction by example. What You'll Do Design and build Azure infrastructure using a cloud native approach, leveraging managed services wherever they meet reliability and cost requirements. Lead technical execution of the migration of services from an on-premises data center to Azure, including dependency mapping, migration sequencing, and cutover risk management. Operate and extend our AKS-based platform, including GitOps deployment patterns, namespace isolation, and policy enforcement. Own and evolve reusable Terraform modules that other engineering teams consume, with clear interface contracts between platform-owned and application-owned infrastructure. Build and maintain observability coverage (metrics, logs, alerting) so that platform and application health are measurable and actionable, not just instrumented. Apply policy-as-code to enforce security, compliance, and operational standards across the platform, and reduce reliance on manual review gates. Design and review Identity and Access Management patterns, including workload identity, least-privilege access models, and secrets management -- with a clear bias away from static credentials. Participate in business continuity and disaster recovery planning for platform services, including failover design, RTO/RPO definition, and recovery testing. Contribute to CI/CD pipeline design and standards used across engineering teams building on the platform. Use AI-assisted engineering tools (e.g., Claude Code, GitHub Copilot, or equivalent) as part of the standard workflow, and evaluate where AI-driven platform capabilities (automated remediation, intelligent alerting, natural-language operational tooling) can be responsibly introduced into the platform itself. Mentor junior and mid-level engineers through code/design review, pairing, and informal technical coaching. Help less experienced engineers build sound judgment around idempotency, error handling, and migration candidacy when evaluating legacy automation. Required Qualifications 8+ years in platform, infrastructure, or site reliability engineering roles, with demonstrated Principal-level scope (technical leadership without formal management). Deep hands-on experience with Azure, building cloud native architectures using managed services rather than defaulting to IaaS. Production experience running and operating Kubernetes at scale, ideally AKS specifically. Strong GitOps experience (ArgoCD, Flux, or equivalent) -- all infrastructure and cluster changes should trace to a git commit as a matter of practice, not preference. Experience leading or significantly contributing to a data center-to-cloud migration, including business continuity and disaster recovery planning. Working fluency in policy-as-code tooling (Kyverno, OPA/Gatekeeper, or equivalent) for security and compliance enforcement. Strong Identity and Access Management background: workload identity federation, least-privilege IAM design, secrets management patterns that avoid static credentials. Experience building and maintaining an observability stack (Prometheus, Grafana, Thanos, or equivalent). Solid Terraform experience, including designing reusable modules consumed by other teams, not just single-project usage. Practical, current experience using AI-assisted development tools in daily engineering work. Demonstrated ability to mentor other engineers -- through review, pairing, or informal technical leadership -- without formal authority. Preferred Qualifications Experience designing or operating hub-and-spoke network architectures in Azure. Familiarity with CI/CD pipeline design for multi-team, multi-repo environments (e.g., GitHub Actions-based runner infrastructure). Exposure to evaluating or building genuinely AI-driven operational tooling (as distinct from rules-based automation mislabeled as AI). Experience presenting technical tradeoffs to both engineering and business stakeholders. Originally posted on Himalayas

查找职位、比较要求,再准备申请

从你希望从事的职位或运用的技能开始搜索。调整地点和职业筛选,打开职位比较工作职责。如果没有结果,可以使用更短的关键词,或逐一移除筛选条件。

区分必备要求和优先条件,检查已列出的工作安排、薪资和地点。远程职位也可能要求特定居住国家、工作许可或工作时间重合。请向雇主确认职位信息和完整条件。

选择能够回应职位要求的真实经历,说明你的贡献,只使用能够证实的数字。遵循雇主的申请说明,并在提交前检查联系方式、文档内容和 PDF。

提交申请前的检查清单

求职常见问题

为什么有些职位使用英文?

职位名称和描述由招聘企业撰写。为避免改变招聘要求或工作条件,我们保留原文。操作界面和本指南使用简体中文。如果中文搜索没有结果,可以尝试使用职位发布语言中的名称或技能,例如“software engineer”。搜索词不会自动翻译,界面语言也不代表企业要求的申请语言。

远程职位是否允许从任何国家工作?

不一定。企业可能对居住国家、工作许可或工作时段有要求。请查看原始招聘页面中的具体条件。如果未说明,应先向企业确认,再判断能否从你所在的地区工作。“远程”标签本身并不代表没有地点限制。

搜索没有结果时应该怎么办?

尝试更通用的职位名称或单个技能,并逐一移除筛选条件。不同企业可能用不同名称描述相似工作。如果某个职位已经消失,请在企业招聘页面搜索其职位编号。扩大搜索范围不会让已经关闭的职位重新开放。

申请会通过 ResumizeAI 直接提交吗?

申请按钮会打开外部网站。请按照企业或招聘服务的说明,在该网站完成并确认提交。在 ResumizeAI 中准备简历并不等于已经申请职位。如果链接只打开企业网站,请先找到对应职位,再继续申请流程。

如何针对职位调整简历和求职信?

将招聘要求与能够解释清楚的项目、任务和成果联系起来。突出相关经历,不要添加未经实际掌握的技能或虚构成绩。在求职信中用具体例子说明申请动机,并遵守企业要求的语言和文件格式。提交前检查两份文件,确保内容准确、联系方式正确、链接可用。