Senior Platform Engineer (Remote US)

- United States - original posting ->
Status
Open
Remote policy
Remote
Employment type
Not stated
Salary
Not stated
Categories
Platform-Engineering, Site-Reliability-Engineering, Production-Support, Cloud-Engineer, DevOps, Senior-Platform-Engineer, Senior-Platform-Engineering, Senior-DevOps-Platform-Engineer, Senior-Developer-Platform-Engineer, Senior-Cloud-Platform-Engineer, Platform-Engineer
Source
himalayas
First observed
2026-08-14 05:53 UTC
Last seen
2026-08-14 05:53 UTC
Source claims posted
2026-08-14 04:45 UTC
Consecutive misses
4 of 10

What the posting says

We are seeking a Senior Platform Engineer to provide US-hours production support and platform engineering for the Product Catalog application. This role focuses on diagnosing and resolving connection, latency, and stability issues across the AWS-based Product Catalog stack, including Apigee, Rancher/Kubernetes, and the C# services.

The engineer will work closely with existing offshore resources and key stakeholders to ensure application reliability and performance during US business hours.

Requirements

AWS Cloud

Hands-on experience troubleshooting production workloads in AWS

Familiarity with core services backing an enterprise app (e.g., compute, database, networking, load balancing, monitoring)

Apigee / API Gateway

Experience with Apigee / Apigee X (or similar API gateway) in a production environment

Ability to debug API failures, timeouts, policy issues, and routing problems

Rancher / Kubernetes

Strong working knowledge of Kubernetes concepts (pods, deployments, services, scaling)

Experience using Rancher (or comparable tooling) for cluster and workload management

Ability to diagnose pod instability, restarts, resource constraints, and related performance issues

C# / Application Services

Proficiency in C# and .NET, especially for API and service‑oriented architectures

Strong debugging and troubleshooting skills in distributed systems

Rules / SQL (Nice-to-Have but Important)

Experience with rules engines or rule-based business logic

Strong SQL skills for performance analysis and data troubleshooting

Willingness and aptitude to learn Product Catalog's rules model and support rules work similar to our Senior Engineers over time

General

Proven track record providing production support for complex, multi‑tier applications

Strong analytical and problem‑solving skills; comfortable owning issues end‑to‑end

Good communication skills for working with both technical teams and business stakeholders during active incidents with the team.

Responsibilities

Provide US-hours production support for Product Catalog, focusing on connection, latency, and general performance issues.

Triage and troubleshoot issues across the AWS, Apigee, Rancher/Kubernetes, C# services, and database layers.

Investigate and resolve problems with API calls, including timeouts, missing logs, and routing/connection failures.

Collaborate with offshore teams who implemented the AWS migration to stabilize and optimize the current environment.

Work with Product Catalog stakeholders to identify root causes and drive sustainable fixes, not just workarounds.

Support and optimize the C# codebase that powers Product Catalog and its API integrations.

Develop proficiency in Product Catalog's rules engine and SQL-based rules storage, gradually taking on non‑production rules work to offload Sr Support Engineers.

Participate inknowledge sharing and documentation to reduce single‑point‑of‑failure risk within the Product Catalog team.

Working conditions

Cover US Business Hours: 9:00 AM – 6:00 PM EST

Why work with us?

Our Culture

Open communication and a focus on psychological safety;

Recognition of achievements and contributions;

Collaboration across multicultural teams;

Less bureaucracy, more focus on results.

Hiring Process

Intro call

Technical Interview

Manager Interview

Client Interview

Pre-offer stage + Reference Check (if requested)

Official Offer

Originally posted on Himalayas

Quality

Completeness: 50%
Honesty: 100%

Based on 5 observation(s).

Timeline

  1. *
    #56773 2026-08-14 05:53 UTC
    Published
  2. o
    #58861 2026-08-14 07:53 UTC
    Not seen
    Miss 1 in a row
  3. o
    #60753 2026-08-14 09:53 UTC
    Not seen
    Miss 2 in a row
  4. o
    #62562 2026-08-14 11:53 UTC
    Not seen
    Miss 3 in a row
  5. o
    #64095 2026-08-14 13:53 UTC
    Not seen
    Miss 4 in a row