Senior Computational Specialist
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, duplicated lines. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes Benefits with salary range. So we can have Benefits section with salary range. Pay? The salary range is part of Benefits; maybe we can treat Pay as separate? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting includes "Annual base salary range of USD $120,000–$140,000." That's pay info. Could put under Benefits or Pay. Since they ask to have Pay section if posting actually states them. It does state salary range, so we can have Pay section. Benefits also includes other bullet points. We'll separate: Pay section with salary range. Benefits section with other benefits (opportunity to work..., collaborative environment..., etc). Also maybe include "Schedule"? Not mentioned, so omit.
We need to preserve all substantive information. Let's extract content.
First paragraph: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Computational Specialist based in the United States. This role provides advanced computational support to researchers using large-scale research computing and high-performance computing (HPC) infrastructure. You will work directly with scholars to solve complex computational challenges, design algorithms, develop applications, and improve research performance. The position combines hands-on technical expertise with consulting, training, documentation, and customer support across HPC and AI technologies. You will contribute to the design and development of next-generation research computing services, helping expand capabilities, capacity, and collaboration opportunities. The role also involves benchmarking, testing, troubleshooting, and maintaining computing resources and software in partnership with technical teams. You will work across programming, cloud computing, containers, GPUs, big data, parallel computing, and AI-enabled research workflows. This is an opportunity to make a direct impact on scientific research while continuously exploring emerging technologies in a highly collaborative environment."
That's about the role. We'll put under
About the role
with containing that prose (maybe split into multiple paragraphs? but we can keep as one
).
Next: "Accountabilities" list bullet points. Those are responsibilities. We'll put under
Responsibilities
with - each bullet.
List:
- Provide advanced computational consultation to researchers, helping solve technical problems, design algorithms, develop applications, and optimize computational workflows.
- Advise researchers on system configurations, development practices, and technical policies that can improve application performance and research productivity.
- Support scholars and collaborators in effectively using HPC technologies, AI tools, research computing infrastructure, and related services.
- Design, build, test, and help deploy new research computing services and capabilities for next-generation infrastructure.
- Contribute to ongoing benchmarking, testing, troubleshooting, maintenance, and technical support for HPC resources, applications, and software.
- Develop training materials, conduct technical training sessions, and create clear online documentation for research computing users.
- Work with technical teams to evaluate computing resources, monitor system health and usage, and improve infrastructure reliability and performance.
- Support computational research involving programming, big data, parallel computing, GPU technologies, cloud infrastructure, and data analytics.
- Develop and support API-based access to computational services and research infrastructure.
- Help researchers adopt effective workflows for data transfer, data sharing, resource management, and high-performance computing.
- Stay current with emerging technologies and contribute ideas that expand research computing capabilities and improve the overall user experience.
- Communicate complex technical concepts clearly through consultations, demonstrations, proposals, presentations, documentation, and customer support.
Now Requirements: after "Requirements" heading in text.
We need to capture all requirements bullet points.
Paragraph: "Master’s degree or equivalent in Computer Science, Physics, Engineering, or a related field with a strong scientific computing emphasis is required; a doctoral degree in Computer Science or equivalent experience is preferred."
Then bullet list:
- At least 5 years of experience working with HPC programming, job scheduling, compilers, performance libraries, and related research computing technologies is required, with 7+ years preferred.
- Strong programming experience in high-level languages such as C++, Fortran, Python, Java, or MATLAB.
- Proven experience with HPC infrastructure workflows, resource managers, usage and system-health monitoring, and data transfer and sharing tools.
- Experience working with Big Data and familiarity with big data infrastructure and structured and unstructured data.
- Excellent programming, mathematical, analytical, and problem-solving skills, with a strong quantitative background in areas such as probability or statistics preferred.
- Proven expertise with Linux and Bash scripting, along with experience programming API access.
- Knowledge of CPU and GPU technologies and HPC and AI offerings from public cloud providers such as GCP.
- Hands-on experience designing, building, and deploying containers such as Docker and Singularity in HPC environments.
- Experience with GPU programming, parallel programming models such as OpenMP, MPI, and CUDA, and parallelizing serial computational applications is preferred.
- Experience supporting computational research in an academic or research environment, with demonstrated success programming, architecting, deploying, and using HPC applications preferred.
- Strong interpersonal, written, verbal, presentation, documentation, and customer-support skills, with the ability to explain complex technical concepts clearly to diverse audiences.
- Ability and willingness to continually expand technical knowledge and stay current with emerging developments and trends in HPC, AI, cloud computing, and scientific computing.
- Desire and ability to create technical content such as blogs or white papers on relevant computational and research technology topics is preferred.
We could separate into Requirements and Qualifications and Skills sections as per allowed headings. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can split the requirements into those categories. But we must not invent sections lacking content. We have content for Requirements (education, experience). Qualifications could be similar; maybe we can treat "Requirements" as education and experience, "Qualifications" as technical skills, "Skills" as soft skills. But we need to ensure we don't create filler. Let's see if we can meaningfully split.
We have:
Education: Master’s degree or equivalent ... doctoral degree preferred.
Experience: At least 5 years ... 7+ years preferred.
Technical skills: programming languages, HPC infrastructure, big data, Linux/Bash, CPU/GPU, containers, GPU programming, parallel models, API access, etc.
Soft skills: interpersonal, communication, ability to expand knowledge, create technical content.
Thus we can have:
Requirements
with education and experience bullets.
Qualifications
with technical qualifications (programming languages, HPC infrastructure, big data, Linux/Bash, CPU/GPU, containers, GPU programming, parallel models, API access, academic research experience).
Skills
with soft skills (interpersonal, communication, continual learning, technical content creation).
We must ensure not to repeat content. Let's extract.
Education bullet: Master’s degree or equivalent in Computer Science, Physics, Engineering, or a related field with a strong scientific computing emphasis is required; a doctoral degree in Computer Science or equivalent experience is preferred.
Experience bullet: At least 5 years of experience working with HPC programming, job scheduling, compilers, performance libraries, and related research computing technologies is required, with 7+ years preferred.
Now Qualifications bullets:
- Strong programming experience in high-level languages such as C++, Fortran, Python, Java, or MATLAB.
- Proven experience with HPC infrastructure workflows, resource managers, usage and system-health monitoring, and data transfer and sharing tools.
- Experience working with Big Data and familiarity with big data infrastructure and structured and unstructured data.
- Proven expertise with Linux and Bash scripting, along with experience programming API access.
- Knowledge of CPU and GPU technologies and HPC and AI offerings from public cloud providers such as GCP.
- Hands-on experience designing, building, and deploying containers such as Docker and Singularity in HPC environments.
- Experience with GPU programming, parallel programming models such as OpenMP, MPI, and CUDA, and parallelizing serial computational applications is preferred.
- Experience supporting computational research in an academic or research environment, with demonstrated success programming, architecting, deploying, and using HPC applications preferred.
Skills bullets:
- Excellent programming, mathematical, analytical, and problem-solving skills, with a strong quantitative background in areas such as probability or statistics preferred.
- Strong interpersonal, written, verbal, presentation, documentation, and customer-support skills, with the ability to explain complex technical concepts clearly to diverse audiences.
- Ability and willingness to continually expand technical knowledge and stay current with emerging developments and trends in HPC, AI, cloud computing, and scientific computing.
- Desire and ability to create technical content such as blogs or white papers on relevant computational and research technology topics is preferred.
Now Benefits: The posting includes "Benefits Annual base salary range of USD $120,000–$140,000. Compensation is determined based on factors including responsibilities, experience, education and training, skills, internal equity, market conditions, and organizational considerations. The stated salary range represents base pay only and excludes potential incentives, bonuses, or other additional compensation. Opportunity to work at the intersection of scientific computing, HPC, AI, cloud infrastructure, big data, and advanced research. Opportunity to directly support scholars and research teams while contributing to next-generation research computing services. Collaborative environment involving researchers, technical specialists, and IT teams. Opportunities to develop training, documentation, technical content, and new computational capabilities. Exposure to emerging technologies and opportunities to continually expand expertise across HPC, AI, GPUs, cloud computing, containers, and parallel computing. Commitment to equal employment opportunity and an inclusive recruitment and hiring environment. Opportunity to contribute to sustainability-focused initiatives within a major urban research environment."
We need to separate Pay and Benefits. Pay: salary range. Benefits: other bullet points.
Thus:
Pay
with Annual base salary range of USD $120,000–$140,000. Compensation is determined based on factors including responsibilities, experience, education and training, skills, internal equity, market conditions, and organizational considerations. The stated salary range represents base pay only and excludes potential incentives, bonuses, or other additional compensation.
Benefits
with - each bullet:
- Opportunity to work at the intersection of scientific computing, HPC, AI, cloud infrastructure, big data, and advanced research.
- Opportunity to directly support scholars and research teams while contributing to next-generation research computing services.
- Collaborative environment involving researchers, technical specialists, and IT teams.
- Opportunities to develop training, documentation, technical content, and new computational capabilities.
- Exposure to emerging technologies and opportunities to continually expand expertise across HPC, AI, GPUs, cloud computing, containers, and parallel computing.
- Commitment to equal employment opportunity and an inclusive recruitment and hiring environment.
- Opportunity to contribute to sustainability-focused initiatives within a major urban research environment.
We should omit EEO boilerplate? The line "Commitment to equal employment opportunity and an inclusive recruitment and hiring environment." is part of benefits; it's okay to keep as it's substantive. The instruction says remove EEO/equal-opportunity boilerplate. However that line is a benefit statement; but it's essentially EEO statement. Might be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove that line. Also "Opportunity to contribute to sustainability-focused initiatives within a major urban research environment."
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, duplicated lines. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes Benefits with salary range. So we can have Benefits section with salary range. Pay? The salary range is part of Benefits; maybe we can treat Pay as separate? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting includes "Annual base salary range of USD $120,000–$140,000." That's pay info. Could put under Benefits or Pay. Since they ask to have Pay section if posting actually states them. It does state salary range, so we can have Pay section. Benefits also includes other bullet points. We'll separate: Pay section with salary range. Benefits section with other benefits (opportunity to work..., collaborative environment..., etc). Also maybe include "Schedule"? Not mentioned, so omit. We need to preserve all substantive information. Let's extract content. First paragraph: "This position is listed on behalf of a partner company, who manages all applications and next steps. Our partner is looking for a Senior Computational Specialist based in the United States. This role provides advanced computational support to researchers using large-scale research computing and high-performance computing (HPC) infrastructure. You will work directly with scholars to solve complex computational challenges, design algorithms, develop applications, and improve research performance. The position combines hands-on technical expertise with consulting, training, documentation, and customer support across HPC and AI technologies. You will contribute to the design and development of next-generation research computing services, helping expand capabilities, capacity, and collaboration opportunities. The role also involves benchmarking, testing, troubleshooting, and maintaining computing resources and software in partnership with technical teams. You will work across programming, cloud computing, containers, GPUs, big data, parallel computing, and AI-enabled research workflows. This is an opportunity to make a direct impact on scientific research while continuously exploring emerging technologies in a highly collaborative environment." That's about the role. We'll put under
About the role
withcontaining that prose (maybe split into multiple paragraphs? but we can keep as one
). Next: "Accountabilities" list bullet points. Those are responsibilities. We'll put under
Responsibilities
with- each bullet.
List:
- Provide advanced computational consultation to researchers, helping solve technical problems, design algorithms, develop applications, and optimize computational workflows.
- Advise researchers on system configurations, development practices, and technical policies that can improve application performance and research productivity.
- Support scholars and collaborators in effectively using HPC technologies, AI tools, research computing infrastructure, and related services.
- Design, build, test, and help deploy new research computing services and capabilities for next-generation infrastructure.
- Contribute to ongoing benchmarking, testing, troubleshooting, maintenance, and technical support for HPC resources, applications, and software.
- Develop training materials, conduct technical training sessions, and create clear online documentation for research computing users.
- Work with technical teams to evaluate computing resources, monitor system health and usage, and improve infrastructure reliability and performance.
- Support computational research involving programming, big data, parallel computing, GPU technologies, cloud infrastructure, and data analytics.
- Develop and support API-based access to computational services and research infrastructure.
- Help researchers adopt effective workflows for data transfer, data sharing, resource management, and high-performance computing.
- Stay current with emerging technologies and contribute ideas that expand research computing capabilities and improve the overall user experience.
- Communicate complex technical concepts clearly through consultations, demonstrations, proposals, presentations, documentation, and customer support.
Now Requirements: after "Requirements" heading in text.
We need to capture all requirements bullet points.
Paragraph: "Master’s degree or equivalent in Computer Science, Physics, Engineering, or a related field with a strong scientific computing emphasis is required; a doctoral degree in Computer Science or equivalent experience is preferred."
Then bullet list:
- At least 5 years of experience working with HPC programming, job scheduling, compilers, performance libraries, and related research computing technologies is required, with 7+ years preferred.
- Strong programming experience in high-level languages such as C++, Fortran, Python, Java, or MATLAB.
- Proven experience with HPC infrastructure workflows, resource managers, usage and system-health monitoring, and data transfer and sharing tools.
- Experience working with Big Data and familiarity with big data infrastructure and structured and unstructured data.
- Excellent programming, mathematical, analytical, and problem-solving skills, with a strong quantitative background in areas such as probability or statistics preferred.
- Proven expertise with Linux and Bash scripting, along with experience programming API access.
- Knowledge of CPU and GPU technologies and HPC and AI offerings from public cloud providers such as GCP.
- Hands-on experience designing, building, and deploying containers such as Docker and Singularity in HPC environments.
- Experience with GPU programming, parallel programming models such as OpenMP, MPI, and CUDA, and parallelizing serial computational applications is preferred.
- Experience supporting computational research in an academic or research environment, with demonstrated success programming, architecting, deploying, and using HPC applications preferred.
- Strong interpersonal, written, verbal, presentation, documentation, and customer-support skills, with the ability to explain complex technical concepts clearly to diverse audiences.
- Ability and willingness to continually expand technical knowledge and stay current with emerging developments and trends in HPC, AI, cloud computing, and scientific computing.
- Desire and ability to create technical content such as blogs or white papers on relevant computational and research technology topics is preferred.
We could separate into Requirements and Qualifications and Skills sections as per allowed headings. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can split the requirements into those categories. But we must not invent sections lacking content. We have content for Requirements (education, experience). Qualifications could be similar; maybe we can treat "Requirements" as education and experience, "Qualifications" as technical skills, "Skills" as soft skills. But we need to ensure we don't create filler. Let's see if we can meaningfully split.
We have:
Education: Master’s degree or equivalent ... doctoral degree preferred.
Experience: At least 5 years ... 7+ years preferred.
Technical skills: programming languages, HPC infrastructure, big data, Linux/Bash, CPU/GPU, containers, GPU programming, parallel models, API access, etc.
Soft skills: interpersonal, communication, ability to expand knowledge, create technical content.
Thus we can have:
Requirements
with education and experience bullets.Qualifications
with technical qualifications (programming languages, HPC infrastructure, big data, Linux/Bash, CPU/GPU, containers, GPU programming, parallel models, API access, academic research experience).Skills
with soft skills (interpersonal, communication, continual learning, technical content creation). We must ensure not to repeat content. Let's extract. Education bullet: Master’s degree or equivalent in Computer Science, Physics, Engineering, or a related field with a strong scientific computing emphasis is required; a doctoral degree in Computer Science or equivalent experience is preferred. Experience bullet: At least 5 years of experience working with HPC programming, job scheduling, compilers, performance libraries, and related research computing technologies is required, with 7+ years preferred. Now Qualifications bullets: - Strong programming experience in high-level languages such as C++, Fortran, Python, Java, or MATLAB. - Proven experience with HPC infrastructure workflows, resource managers, usage and system-health monitoring, and data transfer and sharing tools. - Experience working with Big Data and familiarity with big data infrastructure and structured and unstructured data. - Proven expertise with Linux and Bash scripting, along with experience programming API access. - Knowledge of CPU and GPU technologies and HPC and AI offerings from public cloud providers such as GCP. - Hands-on experience designing, building, and deploying containers such as Docker and Singularity in HPC environments. - Experience with GPU programming, parallel programming models such as OpenMP, MPI, and CUDA, and parallelizing serial computational applications is preferred. - Experience supporting computational research in an academic or research environment, with demonstrated success programming, architecting, deploying, and using HPC applications preferred. Skills bullets: - Excellent programming, mathematical, analytical, and problem-solving skills, with a strong quantitative background in areas such as probability or statistics preferred. - Strong interpersonal, written, verbal, presentation, documentation, and customer-support skills, with the ability to explain complex technical concepts clearly to diverse audiences. - Ability and willingness to continually expand technical knowledge and stay current with emerging developments and trends in HPC, AI, cloud computing, and scientific computing. - Desire and ability to create technical content such as blogs or white papers on relevant computational and research technology topics is preferred. Now Benefits: The posting includes "Benefits Annual base salary range of USD $120,000–$140,000. Compensation is determined based on factors including responsibilities, experience, education and training, skills, internal equity, market conditions, and organizational considerations. The stated salary range represents base pay only and excludes potential incentives, bonuses, or other additional compensation. Opportunity to work at the intersection of scientific computing, HPC, AI, cloud infrastructure, big data, and advanced research. Opportunity to directly support scholars and research teams while contributing to next-generation research computing services. Collaborative environment involving researchers, technical specialists, and IT teams. Opportunities to develop training, documentation, technical content, and new computational capabilities. Exposure to emerging technologies and opportunities to continually expand expertise across HPC, AI, GPUs, cloud computing, containers, and parallel computing. Commitment to equal employment opportunity and an inclusive recruitment and hiring environment. Opportunity to contribute to sustainability-focused initiatives within a major urban research environment." We need to separate Pay and Benefits. Pay: salary range. Benefits: other bullet points. Thus:Pay
withAnnual base salary range of USD $120,000–$140,000. Compensation is determined based on factors including responsibilities, experience, education and training, skills, internal equity, market conditions, and organizational considerations. The stated salary range represents base pay only and excludes potential incentives, bonuses, or other additional compensation.
Benefits
with- each bullet: - Opportunity to work at the intersection of scientific computing, HPC, AI, cloud infrastructure, big data, and advanced research. - Opportunity to directly support scholars and research teams while contributing to next-generation research computing services. - Collaborative environment involving researchers, technical specialists, and IT teams. - Opportunities to develop training, documentation, technical content, and new computational capabilities. - Exposure to emerging technologies and opportunities to continually expand expertise across HPC, AI, GPUs, cloud computing, containers, and parallel computing. - Commitment to equal employment opportunity and an inclusive recruitment and hiring environment. - Opportunity to contribute to sustainability-focused initiatives within a major urban research environment. We should omit EEO boilerplate? The line "Commitment to equal employment opportunity and an inclusive recruitment and hiring environment." is part of benefits; it's okay to keep as it's substantive. The instruction says remove EEO/equal-opportunity boilerplate. However that line is a benefit statement; but it's essentially EEO statement. Might be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove that line. Also "Opportunity to contribute to sustainability-focused initiatives within a major urban research environment."