1

Platform Engineer Backstage Jobs in Michigan (NOW HIRING)

Technical Product Manager

Dearborn, MI · On-site

$153K - $177K/yr

Experience working with **platform engineering teams** or internal developer portals (e.g., Backstage/RHDH) * Comfortable working in code-centric environments (docs in markdown, everything automated ...

Platform Engineer Backstage information

What is the difference between Platform Engineer Backstage vs DevOps Engineer?

AspectPlatform Engineer BackstageDevOps Engineer
CredentialsRelevant engineering degrees, cloud certificationsSimilar certifications, cloud and automation skills
Work EnvironmentFocus on developer portals, tooling, and platform integrationsFocus on CI/CD pipelines, automation, and infrastructure
Industry UsageUsed in tech companies building developer platformsCommon across software development and IT operations

Platform Engineer Backstage primarily focuses on building and maintaining developer portals and internal platforms, enhancing developer experience. DevOps Engineers concentrate on automating deployment pipelines and infrastructure management. While both roles require cloud and automation skills, their core responsibilities differ, with Platform Engineers Backstage emphasizing developer tools and DevOps Engineers focusing on deployment and operations.

What are the typical responsibilities of a Platform Engineer working with Backstage, and how does this role collaborate with development teams?

As a Platform Engineer specializing in Backstage, you will be responsible for building, maintaining, and enhancing the internal developer platform using Backstage as the core framework. Your daily tasks often include developing custom plugins, integrating third-party tools, automating workflows, and ensuring the platform is reliable and user-friendly for internal teams. You will work closely with software developers, DevOps engineers, and product managers to understand their needs, gather feedback, and deliver solutions that improve developer productivity. Collaboration and communication are key, as you’ll frequently participate in cross-functional meetings and support teams in adopting new platform features.

What is a Platform Engineer Backstage?

A Platform Engineer Backstage is a software engineer who specializes in developing, maintaining, and optimizing internal developer portals using Backstage, an open-source platform created by Spotify. Their role involves building self-service tools, integrating various development and deployment systems, and improving the developer experience within an organization. They work to streamline workflows, enhance automation, and ensure that engineering teams have the infrastructure and tools needed to deliver software efficiently. Platform Engineers using Backstage help organize infrastructure, documentation, and services in a centralized portal, promoting productivity and consistency.

What are the key skills and qualifications needed to thrive as a Platform Engineer Backstage, and why are they important?

To thrive as a Platform Engineer specializing in Backstage, you need strong expertise in software engineering, DevOps practices, and experience with Backstage.io as well as cloud infrastructure, often supported by a degree in computer science or related field. Familiarity with tools such as Kubernetes, Docker, CI/CD pipelines, and Backstage plugins is typically required, along with knowledge of programming languages like TypeScript or JavaScript. Excellent problem-solving abilities, collaboration, and clear communication are vital soft skills for this role. These skills ensure efficient platform development, smooth developer experiences, and the reliable operation of internal developer portals in complex technical environments.
What are popular job titles related to Platform Engineer Backstage jobs in Michigan? For Platform Engineer Backstage jobs in Michigan, the most frequently searched job titles are:
Technical Product Manager

Technical Product Manager

JS Consulting

Dearborn, MI • On-site

$153K - $177K/yr

Contractor

Posted 29 days ago


Job description

Job Title- Technical Product Manager

Project Location – Dearborn, MI (4 days a week onsite, 1 days remote) (Local highly preferred)

Duration- 12+ months contract

Visa- USC/ GC

Job Description:

  • We are seeking a **Technical Product Manager (TPM)** to partner with our platform engineering and operations team in delivering the **Cloud Platform (FCP) and GCP 3.0 - a unified developer platform built with zero-trust security, automation, and code-first principles.
  • This role bridges engineering, security, operations, and executive stakeholders to ensure alignment, secure buy-in, and drive adoption of our internal platform tools, processes, and standards.
  • You will work closely with a deeply technical team and should have enough technical fluency to grasp concepts like Kubernetes, GitOps, Terraform, CI/CD pipelines (e.g., Tekton), and Workload Identity Federation.
  • The Cloud Platform runs across cloud, on-premises, and edge environments, with a strong foundation in **Google Cloud Platform (GCP)** and integration with identity services such as Entra ID.
  • Your primary focus will be managing priorities, aligning roadmaps, advocating for platform capabilities across the org, and helping streamline communication and planning using modern Agile practices, including helping the team manage Jira.

Skills Required:

  • Cloud Architecture
  • Cloud Computing
  • Cloud Infrastructure
  • Google Cloud Platform
  • Microsoft Azure
  • Agile Software Development
  • Jira

 Experience Required:

  • Senior Specialist Exp: 10+ years in IT
  • Complex Global Programs TECHNICAL PROGRAM / PROJECT MANAGEMENT
  • Large complex projects
  • Familiarity with **cloud-native infrastructure** (Kubernetes, CI/CD, Terraform, GitOps, identity management)
  • Working knowledge of **Google Cloud Platform (GCP)** and how it integrates with identity, networking, and automation patterns
  • Strong understanding of **Agile methodologies** and experience using **Jira** to manage epics, stories, and sprints
  • Ability to **communicate technical concepts** to non-technical stakeholders and vice versa
  • Experience working with **platform engineering teams** or internal developer portals (e.g., Backstage/RHDH)
  • Comfortable working in code-centric environments (docs in markdown, everything automated via pipelines)
  • Experience managing **cross-team collaboration**, approvals, and stakeholder alignment
  • Organized, clear communicator, capable of **project planning without micromanaging** developers

Experience Preferred:

  • Prior hands-on experience with cloud infrastructure, scripting, or API development (e.g., Go, Python, YAML, Terraform)
  • Familiarity with Entra ID, GitHub APIs, Tekton, Red Hat OpenShift, and workload identity in hybrid environments
  • Experience writing user docs, onboarding guides, or internal wikis
  • Strong instinct for **when to standardize, when to simplify**, and how to advocate for platform usage internally

Education Required: Bachelor's Degree

Education Preferred: Master's Degree

Additional Information:

  • Act as a **liaison** between the platform engineering team and stakeholders (security, compliance, infra, app teams, executive sponsors)
  • Translate technical concepts and infrastructure strategy into **clear roadmaps and justifications** for stakeholders
  • Own and manage the **platform roadmap**, backlog, and priorities
  • Work with the team in an **Agile** setting to maintain backlogs, define user stories, and run planning ceremonies
  • Collaborate with engineering to define and document **use cases, requirements, and goals** for features like platform profiles, app registrations, and `cldctl` enhancements
  • Drive **adoption strategies** for tooling like Red Hat Developer Hub (Backstage), `cldctl`, and workload scaffolding
  • Coordinate **buy-in and approvals** from peer engineering teams and leadership to support platform tooling and adoption
  • Ensure that documentation, internal marketing, and onboarding flows are complete, understandable, and kept up to date
  • Participate in and sometimes lead demos, sprint reviews, and team planning meetings