Platform Engineer
About the role
- Required2–4 years of professional software engineering experience building production systems
- Strong Python skills, including packaging and distributing libraries
- Working familiarity with C++ (reading, modifying, and building C++ code in a cross-platform codebase)
- Experience designing and building APIs (REST, gRPC, or similar) and backend services
- Hands-on experience with AWS, containers, and CI/CDExperience working with large tabular datasets in pandas (data cleaning, transformation, aggregation, and performance at scale)
- Working familiarity with machine learning: you understand the model lifecycle and have helped deploy or integrate ML models in a product
- Strong communication skills and comfort working across engineering and research teams
- Experience building and shipping SDKs or libraries used by external developersSQL and database engineering (schema design, query optimization, PostgreSQL or similar)
- Kubernetes and infrastructure-as-code (Terraform or similar)
- Frontend experience (React or similar)
- Edge or on-device inference (ONNX Runtime, TensorRT, TFLite, Core ML, or similar)
- Python compilation or distribution tooling (Nuitka, Cython, pybind11, or similar)
- Exposure to time-series, sensor, or signal-processing data
- Interest in VR/AR, eye tracking, or human-computer interaction 1 year experience in a research setting (developing or working with ML research domains)
- Why Join UsRemote role with room to grow into automation, tooling, and AI-engineering work—not a pure manual-QA seat
- Direct exposure to a novel technical stack: real-time eye-tracking, ML pipelines, SDKs, and VR/AR integrations
- Tight feedback loop with senior engineering and leadership—the work you ship is felt across the company
- This position reports into the engineering team. We're looking for someone who pairs solid QA fundamentals with curiosity for automation and AI-assisted workflows.
- With your submission please attach: Your resume
- GitHub profile, portfolio, or links to relevant work (test suites, scripts, automations welcome)A short note on a bug you're proud of finding—or an automation/script that saved you or your team meaningful time
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
