---
# System prepended metadata

title: URSSI Interview Prep

---

# URSSI Interview Prep

### Writing samples - 

Code Review Blogpost - https://sarahlrstevens.info/coderev/
Reproducible Research Talk - go.wisc.edu/z6367j

<details>
  <summary>Pre-interview Task Info</summary>

#### Pre-interview Task Description

    You’re URSSI’s new community manager and excited to get started in your new role. Please put together a document, spreadsheet, or short presentation (5 slides or less) about what you imagine the first 90 days in your role might look like. Please revisit the job advert (https://www.codeforsociety.org/jobs/community-manager) look around the website (https://urssi.us/), and the URSSI plan (https://plan.urssi.us/) for information to help you.


You should:

Include timelines/timescales for specific projects
Describe expected deliverables/outputs and how you might evaluate success.
This task is not intended to take more than a couple of hours. You will present your plan for the first 15 minutes of your interview.


#### Job Described Activities

- Monthly Community Calls
- Plan Collaborative writing / hackathons
- Plan Working Group Meetings <!--- unclear what these working groups are -->
- On-board new members
- Documentation
- Code of Conduct Team
- Email Communications
</details>
    
    
### Pre-interview Task


#### Goals for the First 90 Days:
1. Describe the previous URSSI activities and the goals and strategies for the URSSI Strategic plan
5. Create Community page with curated on-boarding information
3. Recruit Code of Conduct Team Members
4. Host Code of Conduct Team Meeting
6. Create list of topics for Community Calls and Hackathons
8. Organize community calls once every other month for the first 6 months of calls
9. Host first Community Call on a topic from previous discussions and also recruit ideas for additional topics


#### Strategies for Each Goal
1. Describe the previous URSSI activities and the goals and strategies for the URSSI Strategic plan
	- Interview URSSI team
	- Review documentation from all previous workshops
	- Review documentation from previous newsletters
	- Review strategic plan and discuss with URSSI team
5. Create Community page with curated on-boarding information
    - Create sections for newsletter, community activites, and how to get involved
    - Assess the need for additional on-boarding sections based on outputs from goal 1
	- Include shared calendar page with events from at least URSSI, US-RSE, ADSA, CaRCC, RDA, SSI (to help avoid conflicts in scheduling and provide a portal the shows all events - different colors for URSSI events vs outside events)
	- Form to suggest new items for the calendar
3. Recruit Code of Conduct Team Members
	- Email current lists from previous workshops/events
	- Email through URSSI channels, US-RSE channels, ADSA, CaRCC, and other collaborator channels
	- Fill gaps in expertise by asking individuals suggested by URSSI Team and own contacts
4. Host Code of Conduct Team Meeting
	- Review other sources for CoC creation
	- Discuss what we would like to see included based on other Community CoC's
	- Review the current CoC to see how this matches with items identified in discussion
	- Fill gaps by adding to or editing the current CoC
	- Make plan for reoccurring meetings to finish above tasks and address any CoC issues
	- Write a blogpost about the updated CoC seeking community feedback (address at meeting 2)
6. Create list of topics for Community Calls and Hackathons
    - Review previous workshop materials to identify suggested topics
    - Review current research software engineering literature for inspirational topics
    - Email the current communtity lists and possibly other collaborator communication channels asking for suggestions
    - Brainstorm topics myself and with the URSSI team
    - For each topic, identify possible speakers, panelists, hosts for the calls/hackatons
8. Organize community calls once every other month for the first 6 months of calls
    - Identify a topics from goal 5 that will be of general interest to the RSE audience - ideally, first event should be a big draw
    - Find possible times which don't overlap with collaborator events
    - Reach out to the identified individuals who may be interested in participating in an event on the topic choosen - flexible about time for the first sessions based on contributor availability
    - Schedule time and send out via communication channels (URSSI and collaborator channels) with RSVP option
    - Check RSVPs two weeks in advance and do a marketing push
    - Schedule reminder emails to individuals who have RSVPed at 1 week/1 day prior to event
9. Host first Community Call on a topic from previous discussions and also recruit ideas for additional topics
    - Create shared note document for sign-in, links and notes
    - Host first communitiy calls on choosen topics (introduce, moderate, facilitate)
    - Get feedback from individuals who attended first few calls about their preferences for future calls/hackathons.

#### Timelines


| Goal | Start                      | Progress Check-in                                     | Next Steps                                                         |
| ---- | -------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------ |
| 1    | Day 1                      | solid by Day 30                                       | on-going                                                           |
| 2    | Day 1                      | draft by Day 30                                       | ongoing updates with revaluation at 6 months and year              |
| 3    | Day 14                     | inital group by Day 60                                | plan for on-going recruitment by Day 60                            |
| 4    | Schedule meeting on Day 44 | 2 hr first meeting by Day 60                          | reoccurring meeting every 2-4 weeks with team to continue progress |
| 5    | Day 1                      | solid draft and on-going plan for new ideas by Day 30 | on-going                                                           |
| 6    | Day 14-30                  | schedule for months 3, 5, 7                           | after first 6 months of calls, adjust frequency based on feedback  |
| 7    | Day 60-90                  | host on months 3, 5, 7                                | after first 6 months of calls, adjust format based on feedback     |

### Success Metrics

1. Describe the previous URSSI activities and the goals and strategies for the URSSI Strategic plan
    - Recieve feedback from URSSI team on my understanding
5. Create Community page with curated on-boarding information
    - Created a community webpage that includes info on joining the community
    - Generally positive feedback from URSSI team and collaborators review
3. Recruit Code of Conduct Team Members
    - Recruited 6-8 members to serve on CoC Team
    - Created plan for off-boarding and on-going recruitment of CoC Team members
4. Host Code of Conduct Team Meeting
    - Hosted first CoC Team Meeting to brainstorm CoC and update existing CoC
    - Created plan for on-going efforts of the CoC to update it and respond to any issues that may arise
6. Create list of topics for Community Calls and Hackathons
    - Created a list of 10-15 community calls and 3-5 hackatons topics
8. Organize community calls once every other month for the first 6 months of calls
    - Scheduled calls for months 3, 5, 7
9. Host first Community Call on a topic from previous discussions and also recruit ideas for additional topics
    - Host calls with with 50+ participants
    - Generally positive feedback from the post surveys 



