Originally posted November 10, 2026 by the employer.
About the role
AMD is seeking a research engineer to advance life sciences computing across computational biology, AI, and high-performance computing. Areas of technical focus include genomics, biological foundation models, protein and molecular modeling, and computational drug discovery on AMD platforms.
What you'll do
- Investigate life sciences workloads to determine computational requirements, algorithms, and practical performance limitations.
- Develop, implement, and evaluate algorithms and AI methods for applications in genomics, biomolecular modeling, or related domains.
- Profile and optimize scientific applications and AI workflows on AMD platforms, addressing computation, memory, data processing, and communication bottlenecks.
- Explore algorithmic reformulations, parallelization strategies, numerical precision, and GPU acceleration while maintaining scientific validity.
- Build reproducible benchmarks to measure end-to-end performance, scalability, resource utilization, and scientific outcomes.
- Contribute reusable software, optimized operators, and improvements to open-source life sciences projects.
What you'll need
- Computational expertise in a life sciences domain such as computational genomics, bioinformatics, protein modeling, computational chemistry, or molecular simulation.
- Hands-on experience implementing scientific algorithms or developing machine learning models for biological applications.
- Strong programming skills in Python alongside experience with C++ or another language used for high-performance scientific computing.
- Solid grounding in algorithms, data structures, numerical methods, and experimental evaluation.
- Experience profiling, debugging, and improving computational software.
Nice to have
- Experience with biological foundation models, protein structure prediction or design, molecular generative models, or genomic sequence modeling.
- Knowledge of scientific AI architectures, including transformers, geometric deep learning, graph neural networks, or diffusion models.
- GPU programming and optimization using HIP, CUDA, Triton, or comparable technologies.
- Hands-on experience with deep learning frameworks such as PyTorch, including custom operators or distributed training and inference.
- Familiarity with parallel algorithms, multi-GPU computing, or large-scale scientific workflows.
- Experience contributing to established open-source life sciences software ecosystems.
Skills: HIP, CUDA, PyTorch, GPU Acceleration, HPC
More semiconductor jobs: AMD jobs
First seen in our index 5 days ago, well below the 47-day median for Infrastructure/Platform Software roles.
Infrastructure/Platform Software · GPU Software Stack
|
Open roles in category
338
|
Median days since first seen
47 d
|
Category median salary (all employers)
$220k
|
See the full market breakdown ▾Category comparison, skills in demand, and who else is hiring
| Metric | AMD | All employers we track in this specialty (338 roles · 24 employers) |
|---|---|---|
| Open roles in this specialty | 74 | 338 |
| Open roles in the wider Software, Firmware & Systems family | 381 | 6787 · 180 employers |
| Median days since first seen | 22 d | 47 d (+25 d vs this employer) |
| Median salary (USD postings) | n/a | $220k |
Skills observed across this category: HIP, CUDA, PyTorch, GPU Acceleration, HPC
Who's hiring in this category
- NVIDIA · 167 open roles · median 75 d
- AMD (this employer) · 74 open roles · median 26 d
- Intel Corporation · 29 open roles · median 27 d
- Qualcomm · 25 open roles · median 68 d
- Arm Holdings · 10 open roles · median 19 d
- Ampere Computing · 5 open roles · median 14 d
How we counted: 338 open Infrastructure/Platform Software (GPU Software Stack) roles from 24 employers tracked in the SemiconductorJobs index, counted 16 Nov 2026. Specialty figures count only roles carrying this exact specialty label, so an employer's related work in neighbouring specialties is not included there, and is counted in the wider Software, Firmware & Systems family row. Days are counted from when our index first saw each posting, not from the employer's original posting date.