次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 14,274

← 検索結果に戻る

Staff Infrastructure Platform Engineer

Gridsight

リモート勤務

勤務地
Remote (Australia)
勤務時間
Full Time
掲載日
2026年10月15日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

Electricity grids are undergoing the most significant transformation in a century. The shift to renewables, the proliferation of rooftop solar, batteries and EVs, and the increasing complexity of distribution networks are forcing utilities to operate their grids in fundamentally new ways. Gridsight's software platform uses data, ML and AI to help grid operators modernise their operations and unlock transformational new capabilities. We deliver visibility into the grid edge, faster renewable connections, and real-time orchestration of distributed energy. The opportunity is enormous ($1B+ ARR). We're embedded with over 50% of Australia's distribution networks, more than 30% in New Zealand, and have 1 of the top 5 utilities in the US as our lighthouse. Airtree led our Series A, Insight lead our Series B, we grew ARR 3.4x in the past 6 months, and we're on the path to build the first truly generational utility software company. We hold an exceptionally high talent bar, but if you’re talented, hungry and ambitious, come join us on our mission. Purpose Make it faster and safer for every Gridsight product team to ship, by solving shared infrastructure, reliability and developer experience problems once instead of in every team. Gridsight builds grid analytics software for electricity utilities in Australia, New Zealand and the US. Our customers run critical infrastructure, so the platform under our product has to be secure, observable and dependable. This role builds that platform. Where the role sits You'll be the first staff engineer (and first IC) on Gridsight's new Infrastructure Platform team. You'll collaborate with a Head of Platform (open role) to help set the team's technical direction, with support from engineering leadership. To start with you'll be a band of one: owning problems end to end across teams and functions, while we build the team out around you. The Infrastructure Platform team is a true platform team in Team Topologies terms: it builds and runs internal products that other teams self-serve. Your customers are our product teams (Grid Visibility, Flex, Connections, Grid Modelling Tooling) and our pillar teams (Data Platform and Grid Modelling Engine). It sits alongside our Experience Platform and Agentic Platform teams. Together these three own the shared foundations that product teams build on. Infrastructure Platform builds the substrate and building blocks for self serve: cloud infrastructure, compute, IAM, CI/CD, environments and observability. IT Ops owns our corporate IT and its compliance controls. You'll partner with them on SOC 2 and customer security reviews: they cover corporate controls, you cover production infrastructure, and together you make compliance evidence come straight from the platform. You'll join the on-call rotation and help shape how we run incidents as our incident management practice matures. Key accountabilities Observability. Build and run our metrics, tracing, logging and alerting platform, and set the patterns that let each team own its own observability over time. Delivery and environments. Evolve and consolidate our deployment pipelines, release management and infrastructure-as-code. Own environment management and test infrastructure, with the goal of shorter lead times and faster CI feedback. Secure, multi-region infrastructure. Design infrastructure that is secure by default, cost-effective and ready for multi-tenant, multi-region delivery across Australia, New Zealand and the US. Work with IT Ops to build SOC 2 controls and evidence into the platform, so teams meet compliance by default rather than by manual effort. Reliability practice. Help define SLOs and error budgets, improve how we respond to and learn from incidents, and take a turn on call. Developer experience. Treat internal engineers as customers. Seek out their friction, measure their satisfaction, and build tools and abstractions they choose to adopt. AI-assisted delivery. Leverage AI-assisted development tooling to accelerate delivery and raise the bar on what a small team can ship. Raising the bar. Mentor engineers across teams and shift how the organisation thinks about reliability, operability and developer experience. Run the platform as a product, with clear interfaces, docs and support, so teams self-serve rather than queue for help. What makes this a Staff role This is not a senior engineer with a bigger backlog. At Staff level we expect you to (in collaboration with engineering leadership): Help set technical direction for platform work across every team, and own a platform roadmap that runs over multiple quarters. Shape decisions you don't own, by writing clear proposals and bringing other teams with you. Find the highest-leverage problems yourself, rather than waiting for them to be handed to you. Define the systems and practices others work within, not just work within them well. Help shape the Infrastructure Platform team from day one, including its early roadmap and how it engages with product teams. How we'll know it's working Lead time, deployment frequency, change failure rate and time to restore are measured and improving. CI feedback is fast and reliable enough that engineers stop working around it. Product teams own their own dashboards and alerts, and on-call engineers find problems before customers do. Developer satisfaction with the platform is measured regularly and trending up. SOC 2 evidence comes straight from the platform, with no manual collection before an audit. Our infrastructure-as-code matches what's actually running, and the legacy estate is retired. Out-of-hours pages are measured per system and falling. What you'll bring ~8 or more years in software engineering, with recent work at Staff level (or clearly operating at it) in platform, infrastructure or SRE. Deep experience running cloud infrastructure in production, including compute, networking, storage, IAM and cost management, with strong infrastructure-as-code skills (AWS and Terraform preferred). A track record of building and operating observability platforms that teams actually rely on. Hands-on SRE practice: SLOs, error budgets, incident response and runbooks. Experience on a platform team in a product engineering organisation, running the platform as a product that teams adopt willingly. Strong software engineering fundamentals and a habit of setting direction and driving outcomes without close supervision. Fluency in the use of AI-assisted development tools - you're already using agentic coding tools, LLM-assisted workflows, or similar to accelerate your work. Nice to have Scaling observability at high data volumes. Building internal developer platforms or self-service tooling with a strong developer experience focus. Familiarity working with data intensive systems and environments Authentication and identity in multi-tenant SaaS (Auth0, Azure AD, SAML/SSO, OIDC). Security and compliance work such as SOC 2, or in highly regulated environments. Resilience practices such as chaos engineering or game days. Energy, utilities or other critical infrastructure domains. Open-source contributions, conference talks or technical writing. Technical knowledge Cloud architecture on AWS: networking, compute, storage, security and cost optimisation. Infrastructure-as-code design and lifecycle, ideally Terraform. Containers and orchestration (we use ECS), and the deployment patterns around them. CI/CD pipeline design and release strategies such as blue-green, canary and progressive delivery. Observability systems: metrics, distributed tracing, log aggregation and alerting. Security fundamentals: IAM, network segmentation and secrets management. Multi-tenant SaaS infrastructure patterns. Learn more Brendan Banfield (CEO at Gridsight) in conversation with James Cameron (Partner at Airtree) Gridsight's work with Endeavour Energy to deliver flexible exports The problem space we're tackling Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。