We invite you to contribute to the FSE 2024 program by submitting to one or more tracks. Each track of FSE 2024 has its own submission site and submission deadlines. Please refer to each page for the details. Please also carefully read the policies for submissions and accepted contributions at the end of this page.

Track NameTrack DescriptionSubmission Link
Research PapersThe latest innovations in theoretical, empirical, conceptual, and experimental software engineering research, from both industry and academia.https://fse2024.hotcrp.com/
Industry PapersA venue for outstanding real-world application of software engineering techniques, tools, methods, processes, and practices. https://fse2024-industry.hotcrp.com
Ideas, Visions and Reflections PapersThe goal of this track is to present radical, innovative, thought-provoking new ideas, and research directions, as well as lessons learned from the past. https://fse2024-ivr.hotcrp.com
Student Research CompetitionA great opportunity for undergraduate and graduate students to experience the research world, present their research results to conference attendees, and compete for prizes. tbd
DemonstrationsA highly interactive venue for researchers and practitioners to present and discuss the most recent advances, experiences, and challenges in the field of software engineering supported by live presentations of new research tools, data, and other artifacts. https://fse2024-demo.hotcrp.com/
WorkshopsWorkshops are an interactive forum for exchanging views, advancing ideas, and discussing preliminary results in various areas of software engineering research and applications. https://fse24workshops.hotcrp.com/
TutorialsAn opportunity for conference participants to gain new insights, knowledge, and skills in a broad range of areas of software engineering. https://fse2024-tutorials.hotcrp.com
Journal First Presentations of papers published recently in prestigious software engineering journals. https://fse2024-journal-first.hotcrp.com
ArtifactsThe artifact evaluation track aims to review, promote, share, and catalog the research artifacts of accepted software engineering papers. https://easychair.org/conferences/?conf=artifactsfse24

Submission Policies

Papers submitted for consideration to FSE should not have been already published elsewhere and should not be under review or submitted for review elsewhere during the reviewing period. Specifically, authors are required to adhere to the ACM Policy and Procedures on Plagiarism and the ACM Policy on Prior Publication and Simultaneous Submissions.

To prevent double submissions, the chairs might compare the submissions with related conferences that have overlapping review periods. The double submission restriction applies only to refereed journals and conferences, not to unrefereed forums (e.g. arXiv.org). To check for plagiarism issues, the chairs might use external plagiarism detection software.

All publications are subject to the ACM Author Representations policy.

All authors and co-authors are subject to ACM Publications Policies, including ACM’s new Publications Policy on Research Involving Human Participants and Subjects.

Possible violations to any of the above policies will be reported to ACM for further investigation. Please see the ACM Publications Policies.

Submission Format

All submissions must be in English and in PDF format. Papers must not exceed the page limits that are listed for each call for papers. The ACM styles have changed recently, and all authors should use the official “ACM Primary Article Template”, as can be obtained from the ACM Proceedings Template page. For Microsoft Word users, please still use the “Interim Template” and not the New Workflow for ACM Publications. To that end, the following LaTeX code can be placed at the start of the LaTeX document:

Research Papers Track (PACMSE):


All other Tracks:


All submissions please use:

\acmBooktitle{Companion Proceedings of the 32nd ACM Symposium on the Foundations of Software Engineering (FSE '24), July 15--19, 2024, Porto de Galinhas, Brazil}

Double-Anonymous Review Process

Please note that the Double-Anonymous Review process is not employed by all tracks. Check in the call for papers whether it is used or not.

In order to ensure the fairness of the reviewing process, the FSE Research Papers Track will continue to employ a double-anonymous review process where external reviewers do not know the identity of authors, and authors do not know the identity of external reviewers. The papers submitted must not reveal the authors’ identities in any way:

  • Authors should leave out author names and affiliations from the body of their submission.
  • Authors should ensure that any citation to related work by themselves is written in third person, that is, “the prior work of XYZ” as opposed to “our prior work”.
  • Authors should not include URLs to author-revealing sites (tools, datasets). Authors are still encouraged to submit replication packages, see the FSE Open Science Policy for details.
  • Authors should anonymize author-revealing company names but instead provide general characteristics of the organisations involved needed to understand the context of the paper.
  • Authors should ensure that paper acknowledgements do not reveal the origin of their work.

The double-anonymous process used this year is “heavy”, i.e., the paper anonymity will be maintained during all reviewing and discussion periods. In case of major revision, authors must therefore maintain anonymity in their response letter and must provide no additional information that could be author-revealing.

To facilitate double-anonymous reviewing, we recommend the authors to postpone publishing their submitted work on arXiv or similar sites until after the notification. If the authors have uploaded to arXiv or similar, they should avoid specifying that the manuscript was submitted to FSE 2024.

Authors with further questions on double-anonymous reviewing are encouraged to contact the program chairs by email. Papers that do not comply with the double-anonymous review process (for the tracks that employ this process) will be desk-rejected.