USRSE · TatsatJha · Dec 5, 2025 · Dec 11, 2025 · Dec 11, 2025 · Dec 11, 2025
diff --git a/_data/freelance.yml b/_data/freelance.yml
@@ -1,5 +1 @@
-- expires: 2025-12-31
-  location: The Verena Institute, Yale University, Remote
-  name: Full Stack Developer
-  posted: 2025-12-08
-  url: https://www.viralemergence.org/blog/were-hiring
+[]
diff --git a/_data/jobs.yml b/_data/jobs.yml
@@ -8,11 +8,6 @@
   name: Research Software Engineer
   posted: 2026-01-18
   url: https://jobs.lever.co/convergentresearch/8aa626d1-01fa-4473-a1b6-c160737148b2
-- expires: 2026-03-01
-  location: Lawrence Berkeley National Lab, Berkeley, CA
-  name: Data Science Engineer
-  posted: 2026-01-07
-  url: https://jobs.lbl.gov/jobs/data-science-engineer-7320
 - expires: 2026-03-31
   location: Princeton University, Princeton, NJ
   name: Lead Research Software Engineer
@@ -40,11 +35,6 @@
   name: Research Engineer / Research Scientist
   posted: 2025-12-08
   url: https://expensive-legume-bf0.notion.site/Research-Engineer-Research-Scientist-atmosphere-ocean-model-development-2bfeafcd086b803f92d3f08bc23ae9bf
-- expires: 2025-12-31
-  location: Rutgers University, Piscataway, NJ
-  name: Research Programmer
-  posted: 2025-11-20
-  url: https://jobs.rutgers.edu/postings/257384
 - expires: 2026-02-27
   location: Rosen Center for Advanced Computing, Purdue University, West Lafayette,
     IN
@@ -56,13 +46,3 @@
   name: Lead Research Software Engineer
   posted: 2025-07-30
   url: https://main-princeton.icims.com/jobs/19506/lead-research-software-engineer/job
-- expires: 2025-12-31
-  location: University of California, San Francisco, San Francisco, CA
-  name: Data scientist
-  posted: 2025-07-13
-  url: https://www.jeanfeng.com/joining#data-scientist-2-openings
-- expires: 2025-12-16
-  location: School of Computing, University of Wyoming, Laramie, WY
-  name: Research Scientist, Associate or Assistant (two openings)
-  posted: 2024-12-16
-  url: https://eeik.fa.us2.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1/job/243604/
diff --git a/_events/2025/2025-11-13-community-call.md b/_events/2025/2025-11-13-community-call.md
@@ -0,0 +1,28 @@
+---
+title: November 2025 Community Call
+expires: 2025-11-13
+event_date: "November 13, 2025"
+layout: event
+duration: 60
+repeated: false
+category: community-call
+time:
+    - - start: 2025-11-13T17:00:00Z
+        end: 2025-11-13T18:00:00Z
+---
+
+Our **November Community Call** will be about **Funding for Research Software Engineering!** on Thursday, November 13, 2025, 12pm ET/11am CT/10am MT/9am PT.
+
+It’s no secret—funding for RSEs and RSE work can sometimes feel like hunting for treasure without a map. In this month’s community call, we’re diving into the big questions: How do you find funding? How do you actually secure it? And perhaps the trickiest part—how do you convince funders that your project (or your role as an RSE) is worth investing in?
+
+But maybe grants aren’t the only answer. Are there other ways to keep a project alive and thriving? Have you found creative approaches to support your work when grants didn’t come through?
+
+We’d love for you to bring your stories—both the epic wins and the “learning experiences” (aka not-so-successful applications). Come swap tips, share laughs, and pick up ideas from others who are navigating the same unpredictable funding waters.
+
+The typical structure of a community call starts with an overview of recent US-RSE updates, followed by short presentations. After the presentations we will break out into smaller groups in which we discuss the call topic. Everyone is welcome to join the discussion or just hang back and listen in. If you prefer just to listen in, that is perfectly fine, but we encourage you to share your opinions and thoughts as you feel comfortable. If you want to switch to another group, this is also fine. Just go back to the main room and let the call organizers know.
+
+#### Registration details
+
+Information on how to register for the Zoom meeting will be sent via email
+and posted in the `#general` channel on Slack. The registration link can also be found in the pinned messages and channel description of the `#communitycalls` channel on Slack.
+
diff --git a/_events/2025/2025-12-community-call.md b/_events/2025/2025-12-community-call.md
@@ -11,7 +11,7 @@ time:
         end: 2025-12-12T18:00:00Z
 ---
 
-Our **December Community Call** will be about **RSE Careers: Hiring, Getting Hired, and Everything in Between** on Friday, December 12, 12pm ET/11am CT/10am MT/9am PT.
+Our **December Community Call** will be about **how RSEs do hardware, too!** on Friday, December 12, 12pm ET/11am CT/10am MT/9am PT.
 
 In spite of the title Research Software Engineer, a number of us are involved with hardware as well. Have you built, modified, worked with, or integrated hardware into a system for research? Have you built or maintained hardware-adjacent software? Come tell us about it! Are you just curious about how software engineers could ever end up working with circuits and mechanical bits? Join us to see some examples of projects by members of our community and discuss the unique challenges of integrating the physical with the digital.
 

diff --git a/_events/2026/2026-02-community-call.md b/_events/2026/2026-02-community-call.md
@@ -0,0 +1,27 @@
+---
+title: February 2026 Community Call
+expires: 2026-02-13
+event_date: "February 13, 2026"
+layout: event
+duration: 60
+repeated: false
+category: community-call
+time:
+    - - start: 2026-02-13T19:00:00Z
+        end: 2026-02-13T20:00:00Z
+---
+
+
+
+Our February Community Call will be all about Web and Mobile Apps as Research Software on Friday, February 13, at 2pm ET/1pm CT/12pm MT/11am PT.
+
+When you think of research software, is a web page or mobile app the first thing that comes to mind? Maybe not, but there are many members of our community who do this regularly! Come learn about how these web and mobile apps are contributing to research, the unique challenges involved in developing research code for these platforms, and the tools and techniques that make this possible.
+
+
+The typical structure of a community call starts with an overview of recent US-RSE updates, followed by short presentations. After the presentations we will break out into smaller groups in which we discuss the call topic. Everyone is welcome to join the discussion or just hang back and listen in. If you prefer just to listen in, that is perfectly fine, but we encourage you to share your opinions and thoughts as you feel comfortable. If you want to switch to another group, this is also fine. Just go back to the main room and let the call organizers know.
+
+#### Registration details
+
+Information on how to register for the Zoom meeting will be sent via email
+and posted in the `#general` channel on Slack. The registration link can also be found in the pinned messages and channel description of the `#communitycalls` channel on Slack.
+
diff --git a/_events/2026/2026-03-community-call.md b/_events/2026/2026-03-community-call.md
@@ -0,0 +1,23 @@
+---
+title: March 2026 Community Call
+expires: 2026-03-12
+event_date: "March 12, 2026"
+layout: event
+duration: 60
+repeated: false
+category: community-call
+time:
+    - - start: 2026-03-12T17:00:00Z
+        end: 2026-03-12T18:00:00Z
+---
+
+Our **March Community Call** will be all about **Legacy Code: Horrors and Successes on Thursday, March 12**, 12pm ET/11am CT/10am MT/9am PT.
+
+Have you had the “pleasure” of resurrecting or maintaining legacy code? Do you want to share your trauma? Or maybe it was one of the easiest things you ever did in your professional career? We want to hear from you! In this month’s community call, we will talk about all the dirty little secrets you found in 5-, 10-, or even 15-year-old code and how you made it all good again! From terrifying code smells to hard-won victories, this meetup explores the horrors and successes of legacy code—and how teams survive and even thrive with it
+
+
+#### Registration details
+
+Information on how to register for the Zoom meeting will be sent via email
+and posted in the `#general` channel on Slack. The registration link can also be found in the pinned messages and channel description of the `#communitycalls` channel on Slack.
+
diff --git a/_events/repeated/community-call-fridays.md b/_events/repeated/community-call-fridays.md
@@ -3,7 +3,7 @@ title: Even Months Community Call
 subtitle:
 location: Virtual
 expires: 2026-12-11
-event_date: "alternating 2nd Thursday (12:00-1:00pm ET) and 2nd Friday (2:00-3:00pm ET)"
+event_date: "2nd Friday (2:00-3:00pm ET)"
 layout: event
 category: community-call
 time:
@@ -17,7 +17,7 @@ repeated: true
 rrule:
 # second Friday of every other month
   - DTSTART;TZID=America/New_York:20220610T140000
-  - RRULE:UNTIL=20251211T120000;FREQ=MONTHLY;INTERVAL=2;BYDAY=+2FR
+  - RRULE:UNTIL=20261211T120000;FREQ=MONTHLY;INTERVAL=2;BYDAY=+2FR
   - RDATE;TZID=America/New_York:20220610T140000
 ---
 

diff --git a/_events/repeated/community-call-planning.md b/_events/repeated/community-call-planning.md
@@ -17,7 +17,7 @@ repeated: true
 rrule: 
   - DTSTART;TZID=America/New_York:20220127T120000
 # fourth Thursday of every month
-  - RRULE:UNTIL=20251225T120000;FREQ=MONTHLY;BYDAY=+4TH
+  - RRULE:UNTIL=20261225T120000;FREQ=MONTHLY;BYDAY=+4TH
   - RDATE;TZID=America/New_York:20220127T120000
 ---
 

diff --git a/_events/repeated/community-call.md b/_events/repeated/community-call.md
@@ -18,7 +18,7 @@ rrule:
 # second Thursday of every other month
   - DTSTART;TZID=America/New_York:20220714T120000
   - RDATE;TZID=America/New_York:20220714T120000
-  - RRULE:UNTIL=20251211T120000;FREQ=MONTHLY;INTERVAL=2;BYDAY=+2TH
+  - RRULE:UNTIL=20261211T120000;FREQ=MONTHLY;INTERVAL=2;BYDAY=+2TH
 ---
 
 The US-RSE community calls of each odd month (Jan, Mar, May, Jul, Sep, Nov) take place on the second Thursday of the month, 12:00-1:00pm ET on Zoom. Community call topics, agenda, and zoom registration announcements are posted to Slack and sent to the US-RSE email list.