Principal Product Manager at Trust In SODA
lancashire, Lancashire - England, United Kingdom -
Full Time


Start Date

Immediate

Expiry Date

03 Feb, 27

Salary

55000.0

Posted On

05 Nov, 26

Experience

5 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

No

Skills

Industry

Retail & E-Commerce

Description


  • The roleYou'll own the product side of the hardware and infrastructure lifecycle, from new kit arriving in a data centre to it running in the platform. A lot of the job is making that path work across support, customer, data centre ops and platform teams, and building the internal tooling behind it.Own strategy, roadmap and delivery for internal tooling, CMDB, service catalogues and operational workflows
  • Set up reliable sources of truth for infrastructure, services, customers, environments and configuration
  • Work with SRE, infrastructure, security and support to cut operational friction and give teams more self-service
  • Make build vs buy calls on third-party tools
  • Sit alongside your engineers, challenge architecture and understand how things are built


  • What we're looking forYou'll be a subject matter expert in infrastructure operations rather than a generalist PM. That usually means time somewhere that runs a lot of its own hardware: a hyperscaler, a hedge fund, an exchange or any business with a large on-prem estate. AI experience isn't needed.An engineering background counts for more than PM credentials. You'll be comfortable with APIs, Kubernetes and cloud, inventory and dependency data, automation, observability and security, and able to hold your own in technical design discussions.You'll have pulled support, customer, DC ops and platform teams together to get things fixed or shipped, and you'll enjoy ambiguity and speed. This is a principal role that stays close to the technical detail, so it won't suit someone who has moved well away from hands-on work. If you've stepped back from a Head or Lead role and want to build a function from scratch, that's welcome.Nice to have: NetBox, ServiceNow, Terraform, Grafana or similar, and a good grasp of distributed systems failure handling (retries, idempotency, eventual consistency).

How To Apply:

Incase you would like to apply to this job directly from the source, please click here

Responsibilities


  • The roleYou'll own the product side of the hardware and infrastructure lifecycle, from new kit arriving in a data centre to it running in the platform. A lot of the job is making that path work across support, customer, data centre ops and platform teams, and building the internal tooling behind it.Own strategy, roadmap and delivery for internal tooling, CMDB, service catalogues and operational workflows
  • Set up reliable sources of truth for infrastructure, services, customers, environments and configuration
  • Work with SRE, infrastructure, security and support to cut operational friction and give teams more self-service
  • Make build vs buy calls on third-party tools
  • Sit alongside your engineers, challenge architecture and understand how things are built


  • What we're looking forYou'll be a subject matter expert in infrastructure operations rather than a generalist PM. That usually means time somewhere that runs a lot of its own hardware: a hyperscaler, a hedge fund, an exchange or any business with a large on-prem estate. AI experience isn't needed.An engineering background counts for more than PM credentials. You'll be comfortable with APIs, Kubernetes and cloud, inventory and dependency data, automation, observability and security, and able to hold your own in technical design discussions.You'll have pulled support, customer, DC ops and platform teams together to get things fixed or shipped, and you'll enjoy ambiguity and speed. This is a principal role that stays close to the technical detail, so it won't suit someone who has moved well away from hands-on work. If you've stepped back from a Head or Lead role and want to build a function from scratch, that's welcome.Nice to have: NetBox, ServiceNow, Terraform, Grafana or similar, and a good grasp of distributed systems failure handling (retries, idempotency, eventual consistency).
Loading...