PhysicsX · posted · checked
Platform Support Engineer
KubernetesLinuxOn-site · Singapore
Who can apply
On-site · Singapore
Location: Singapore
About us
Re-architecting Engineering for the Age of Intelligence
PhysicsX is the physics AI company for industrials. The company’s mission is to accelerate hardware innovation by overhauling what industrial engineering and manufacturing look like today. PhysicsX is building a new simulation software stack to deliver deep physics AI enablement across the entire engineering lifecycle. The company partners with leading organisations in aerospace & defence, automotive, semiconductors, materials, and energy & renewables, supporting them on some of their most critical and complex challenges. PhysicsX is headquartered in the United Kingdom, with offices in London, New York, and Singapore and an expanding presence in the Bay Area.
The role
Platform Support Engineers are PhysicsX’s first technical responders for enterprise customers and internal users of the Platform. You’ll own the path from intake to resolution: triage, first-pass investigation, customer updates, and, where you can’t fix it yourself, a high-quality escalation to Product, SRE, FDSE or Deployment Engineering. This isn’t a service desk. You’re building the repeatable front door into PhysicsX’s deeper technical capability.
What you’ll do
Own it, investigate it, fix it where you can. You’re the first engineer on every issue, and you own it until it’s closed, whether you resolve it yourself or bring in Product, SRE, FDSE or Deployment Engineering. Your goal is to resolve a growing share of issues without escalation, and to hand over a root-cause diagnosis rather than a symptom when you do escalate.
Triage incoming issues, classify severity, and run the first-pass investigation across product, platform, infrastructure and customer environment to find where the problem most likely lies.
Resolve what you can. When you can’t, hand over with the logs, events, config, timeline, what you’ve already tried, and a recommended next step.
Work within a structured incident process: response targets, clean handovers, and post-mortems.
Debug inside the platform.
Navigate Kubernetes (EKS, AKS and others): inspect workloads, ingress, permissions and cluster health, read events and logs, and work out what’s failing and why. You don’t need to be a cluster admin, but you do need to know when to hand over.
Use Linux, container and Helm knowledge, monitoring signals (logs, metrics, alerts, Prometheus-style) and cloud fundamentals (networking, compute, storage, IAM) to tell whether a symptom points at the application, the cluster or the cloud layer.