Frequently asked questions

As a Software Engineer, what are the benefits of joining? 

By volunteering to guide researchers or contribute to our blog, you gain valuable mentoring and writing experience. Additionally, you will receive a testimonial for each successful project you complete, showcasing your contributions and impact. The experience in systems design you gain can help you advance your career and move up to more senior role.

How can I become a community member of Engineers for Science?

To become a member of Engineers for Science, simply sign up for our newsletter on our website. You will receive updates on ongoing projects and opportunities to support researchers. If you are interested in personalized notifications for engineers or researchers, sign up on the respective pages.  

What is the possible involvement of a software engineer in a project with a researcher?

The level of involvement of a software engineer in a project with a researcher can vary depending on their collaboration agreement. The engineer can offer mentoring and guidance to the researcher by having a coffee meeting, providing feedback on ideas, and possibly reviewing code. However, the software engineer does not write code for the researcher. The duration of the project can also vary depending on the complexity of the challenge and the availability of both parties. Some projects may be completed in a single meeting, while others may take several weeks. In the end, the team can summarize their learnings and create an optional testimonial to document their experience. Overall, the goal is to help the researcher become more efficient in coding and best practices.

We support challenges related to software engineering in research projects across all fields. These challenges can range from data analysis to software development. A typical project would be to publish the code written for a publication as open-source repository, such that others can reproduce the findings and build upon them. The software engineer can guide the researcher with challenges like package management, handling virtual environments, or using tools to automatically create and publish a documentation.

How can I support Engineers for Science if I'm not a software engineer or researcher?

You can support Engineers for Science by sharing our initiative with your network, making a donation to help cover operating costs of the website, or volunteering your time to help with administrative tasks.

How do I know if a project is a good fit for me as an engineer?

We provide detailed information about each project, including the field, challenge, and desired collaboration, to help you determine if it's a good fit for your skills and interests. We encourage you to ask any questions or express any concerns before committing to a project.

Do I have to pay as a Researcher for the mentoring?

No, all mentoring and guidance provided is completely free. We believe in a community-driven approach as lived by StackOverflow or FreeCodeCamp.  

How can this initiative simplify my life as a Researcher?

You can leverage the expertise of experienced software engineers to improve the quality of your code and learn how to apply best practices from our blog. This not only saves you time, but also leads to more reproducible and reliable findings. In addition, publishing your work as open-source code within the community can make it easier for other researchers to use and build upon your work, leading to a bigger impact. Finally, you can build connection with the industry, which can lead to collaboration opportunities and potential funding for your research.

What types of challenges are eligible for support?