1

Home Based Scientific Software Developer Jobs in Massachusetts

Software Developer II

Worcester, MA · On-site

$90 - $130/hr

Experience with Git/GitHub and CI/CD-based deployment* Comfortable using AI-assisted development ... Bachelor's degree in computer science or a related field, or equivalent professional experience*

Senior Software Developer

Boston, MA · On-site +1

$147K - $198K/yr

Wilson Sonsini is the premier legal advisor to technology, life sciences, and other growth ... The compensation for this position may include a discretionary year-end merit bonus based on ...

Showing results 41-60

Home Based Scientific Software Developer information

What is a home based scientific software developer?

A Home Based Scientific Software Developer is a professional who designs, develops, and maintains software tools used for scientific research and analysis, while working remotely from home. They often collaborate with scientists, researchers, and engineers to create programs that process data, simulate experiments, or visualize scientific phenomena. This role requires strong programming skills, knowledge of scientific principles, and the ability to work independently using remote communication tools. Home based roles offer flexibility, allowing developers to contribute to research projects and software solutions from anywhere. These professionals are essential in fields like bioinformatics, physics, chemistry, and environmental science.

What are the key skills and qualifications needed to thrive as a home based scientific software developer?

A Home Based Scientific Software Developer needs strong programming skills (often in Python, C++, or MATLAB), a solid background in mathematics or a scientific discipline, and typically at least a bachelor's degree in computer science, engineering, or a related field. Familiarity with scientific computing libraries, version control systems like Git, and experience with cloud-based or distributed computing platforms are commonly required. Excellent problem-solving abilities, self-motivation, and effective remote communication are vital soft skills for success in a home-based setting. These competencies ensure the developer can build reliable, efficient scientific software, collaborate virtually with researchers, and deliver solutions that advance scientific discovery.

What are some common challenges for home based scientific software developers and how can they be addressed?

Home-based scientific software developers often face challenges such as maintaining clear communication with research teams, managing time effectively without in-person supervision, and ensuring access to necessary computing resources. Overcoming these challenges typically involves using collaborative tools like version control systems (e.g., Git), regular video meetings, and cloud-based platforms for code sharing and testing. Establishing a structured daily routine and staying updated with scientific advancements also helps developers stay productive and connected with their team.

What is the difference between Home Based Scientific Software Developer vs Scientific Software Engineer?

AspectHome Based Scientific Software DeveloperScientific Software Engineer
CredentialsBachelor's or Master's in Computer Science, Physics, or related fieldsBachelor's or Master's in Computer Science, Engineering, or related fields
Work EnvironmentRemote, home-based setupTypically office or lab environment, but may include remote work
Industry UsageResearch institutions, academia, biotech, environmental agenciesResearch labs, industry R&D, government agencies
Common Search/ComparisonYesYes

The main difference is that a Home Based Scientific Software Developer primarily works remotely on scientific software projects, often in academia or research settings, while a Scientific Software Engineer may work in more traditional office or lab environments within industry or government. Both roles require similar educational backgrounds and skills, but their work settings and typical employers differ.

What are the most commonly searched types of Scientific Software Developer jobs in Massachusetts?

The most popular types of Scientific Software Developer jobs in Massachusetts are:

Infographic showing various Home Based Scientific Software Developer job openings in Massachusetts as of June 2026, with employment types broken down into 1% As Needed, 82% Full Time, 15% Part Time, and 2% Contract. Highlights an 77% Physical, 1% Hybrid, and 22% Remote job distribution.

Full-time

Medical, Dental, Vision, Retirement, PTO

Re-posted 28 days ago


Harvard University rating

8.5

Company rating: 8.5 out of 10

Based on 12 frontline employees who took The Breakroom Quiz

81st of 620 rated colleges and universities


Job description

Company Description

By working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise. We are dedicated to creating a diverse and welcoming environment where everyone can thrive.

Why join Harvard Medical School?

Harvard Medical School's mission is to nurture a diverse, inclusive community dedicated to alleviating suffering and improving health and well-being for all through excellence in teaching and learning, discovery and scholarship, and service and leadership.

You'll be at the heart of biomedical discovery, education, and innovation, working alongside world-renowned faculty and a community dedicated to improving human health. This is more than a job - it's an opportunity to shape the future of medicine.

Job Description

The SBGrid Consortium at Harvard Medical School supports a large international research community by curating and distributing a scientific software platform used across structural biology, cryo-EM, and related fields. The platform includes approximately 650 software titles and 6,000 versions across macOS and Linux and is deployed across laptops, workstations, HPC clusters, and cloud environments. We are hiring a Scientific Platform Engineer to help lead the modernization, security, reliability, and engineering evolution of this platform. This is a platform engineering role with substantial independent responsibility for CI pipelines, reproducible packaging, deterministic installation, release engineering, runtime hardening, observability, and software supply-chain integrity. The role is designed to be primarily engineering and platform-development work, not routine support, and it directly impacts software delivery and platform reliability across a globally distributed scientific infrastructure.

What You Will Work On: This is an engineering-heavy role - expect 90%+ project/building time vs break-fix. 

Build & Test Automation 

  • Design and implement CI pipelines for scientific software across macOS and Linux.
  • Develop regression and smoke test harnesses for packaged software.
  • Catch failures before distribution rather than after client installation.
  • Support fast-moving development branches (e.g., nightly builds) safely.

Reproducible Packaging 

  • Help define and enforce a canonical build contract.
  • Improve dependency tracking and version control.
  • Enable deterministic rebuilds across environments.
  • Contribute to artifact integrity and metadata tracking (e.g., SBOM readiness).

Runtime Platform Hardening 

  • Add tests and versioning discipline to SBGrid's runtime wrapper system ("capsules").
  • Introduce feature flags and safer rollout mechanisms.
  • Improve logging, observability, and error classification. Internal Tooling & Observability.
  • Develop dashboards and structured signals around build failures and common error states.
  • Reduce reliance on tribal knowledge by encoding workflows into systems.

Technologies You'll Use (and can help shape): 

Core platforms 

  • Linux (expert-level): shells, process model, filesystems, toolchains, debugging, perf basics
  • macOS (strong): building, testing, and release workflows across Intel + Apple Silicon

Build/release + automation 

  • CI/CD: GitLab CI (or equivalent CI systems and concepts)
  • Scripting and automation: Bash + Python (primary)
  • Performance-oriented implementation as needed: Go and/or Rust (selectively, for the hot paths)

Packaging and reproducibility 

  • Current + future packaging direction: evaluating/adopting Nix/Spack/Homebrew-style approaches
  • Dependency management, artifact metadata, caching, provenance, reproducible builds Execution environments
  • Containers and virtualization: Docker/Podman, VMs, and orchestration concepts (framework-agnostic; Kubernetes/OpenShift not required)
  • (Nice-to-have) Apptainer/Singularity in scientific/HPC contexts

Version control + engineering hygiene 

  • Git, code review workflows, testing discipline, documentation-first habits

Nice-to-have context 

  • Research/HPC exposure (Slurm, shared filesystems, scientific software stacks)
  • AWS familiarity (useful, not required)

"You Don't Need to Know Everything" 

We expect this job description to match people coming from different directions including Unix/HPC/research computing admins who like building durable automation, build/release engineers who want harder problems than a typical web app pipelines, and developers with systems instincts who are comfortable close to the OS and tooling.

If you're strong in either the systems/ops side or the programming/build tooling side, and you want to grow into the other half, we want to hear from you.

Qualifications

Basic Qualifications:

  • Minimum of five years' post-secondary education or relevant work experience.


Additional Qualifications and Skills (Preferred):

  • Bachelor's degree in computer science, engineering, or a related technical field. 
  • Minimum of 5 years of relevant experience in platform engineering, systems engineering, DevOps, build/release engineering, research computing infrastructure, or a closely related area. 
  • Two or more years of professional software development experience.
  • Experience with CI/CD systems (e.g., GitLab CI, GitHub Actions, similar).
  • Experience with an Infrastructure-as-Code tool (e.g. Ansible, Puppet, Chef, Terraform, etc).
  • Comfortable with Linux internals and scripting in Bash.
  • Experience debugging cross-platform build or runtime issues.
  • Solid programming skills in at least one interpreted language (Python preferred, Javascript, Ruby, etc).
  • Comfort working in a remote, documentation-driven environment.
  • Experience with HPC environments or research computing.
  • Familiarity with containerization (Docker, Singularity/Apptainer, similar).
  • Experience with artifact signing or supply-chain tooling.
  • Experience working in regulated or compliance-sensitive environments.
  • Interest in scientific research software ecosystems.
  • Strong engineering discipline and curiosity matter.
Additional Information
  • Term: This is a 1-year term position from the date of hire, with the possibility of extension, contingent upon work performance and continued funding to support the position.
  • Standard Hours/Schedule: 35 hours per week. Remote candidates must be available to work during Eastern Standard Time (EST) business hours.
  • Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this position.
  • Pre-Employment Screening: Identity
  • Other Information: Please note that we are currently conducting a majority of interviews and onboarding remotely and virtually. We appreciate your understanding. 
  • Staying Informed About Your Application: Due to the high volume of applications, we may not always be able to reach out right away, but you can track your status anytime through the Careers@Harvard portal. 

#LI-DK1

Work Format Details

This position has been determined by school or unit leaders that the duties and responsibilities can effectively be performed fully remotely at a non-Harvard location. Employees in fully remote positions must work all scheduled hours in a Harvard registered state in compliance with the University's Policy on Employment Outside of Massachusetts. At the discretion of the department, fully remote employees may occasionally be required on site at a Harvard location. Certain visa types and funding sources may limit work location. Individuals must meet work location sponsorship requirements prior to employment.

Salary Grade and Ranges

This position is salary grade level 058. Please visit Harvard's Salary Ranges to view the corresponding salary range and related information. 

Benefits

Harvard offers a comprehensive benefits package that is designed to support a healthy work-life balance and your physical, mental and financial wellbeing. Because here, you are what matters. Our benefits include, but are not limited to: 

  • Generous paid time off including parental leave 
  • Medical, dental, and vision health insurance coverage starting on day one 
  • Retirement plans with university contributions 
  • Wellbeing and mental health resources 
  • Support for families and caregivers 
  • Professional development opportunities including tuition assistance and reimbursement 
  • Commuter benefits, discounts and campus perks 

Learn more about these and additional benefits on our Benefits & Wellbeing Page. 

EEO/Non-Discrimination Commitment Statement

Harvard University is committed to equal opportunity and non-discrimination. We seek talent from all parts of society and the world, and we strive to ensure everyone at Harvard thrives. Our differences help our community advance Harvard's academic purposes.

Harvard has an equal employment opportunity policy that outlines our commitment to prohibiting discrimination on the basis of race, ethnicity, color, national origin, sex, sexual orientation, gender identity, veteran status, religion, disability, or any other characteristic protected by law or identified in the university's non-discrimination policy. Harvard's equal employment opportunity policy and non-discrimination policy help all community members participate fully in work and campus life free from harassment and discrimination.


What Harvard University employees say

Pay

Benefits

Hours and flexibility

Workplace

Get the full story on Breakroom