# Can we collaborate on a discourse thread or article about 'How to write a job posting that gets results'
**URL:** https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599
**Category:** Design Lounge
**Created:** [July 5, 2021, 9:00pm UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599 "2021-07-05T21:00:31Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Erioldoesdesign](https://discourse.opensourcedesign.net/u/Erioldoesdesign)
#### Post date: [July 5, 2021, 9:00pm UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/1 "2021-07-05T21:00:31Z")
Hey y’all,
So while working on the re-design proposals for the jobs page it was suggested that an article or perhaps a discourse thread (or maybe a category) around ‘How to ask for OSS design work and have the engagement be successful’
Suggestions in the Figma comments included:
“You’ll attract more UX help if you post more open ended job requests. We’d suggest starting off with a user study or a journey map so your team can identify more impactful UX work for your project.”
---
### Author:  [@jdittrich](https://discourse.opensourcedesign.net/u/jdittrich)
#### Post date: [July 8, 2021, 12:53pm UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/2 "2021-07-08T12:53:12Z")
What comes to my mind:
- Target group description for the product or feature
- Usage scenario if it is a feature (usability questions, testing, review), broad goal of the product if it is something more overaching (UI style, website, logo)
- Technological limitations (e.g. sticking with a particular toolkit, keeping the website static…)
- Link to past conversations about this (in case they exist)
---
### Author:  [@jwf](https://discourse.opensourcedesign.net/u/jwf)
#### Post date: [July 8, 2021, 11:30pm UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/3 "2021-07-08T23:30:18Z")
> [@Erioldoesdesign](#):
>
> So while working on the re-design proposals for the jobs page it was suggested that an article or perhaps a discourse thread (or maybe a category) around ‘How to ask for OSS design work and have the engagement be successful’
I am curious what kind of questions designers have entering an Open Source-oriented role for the first time. I don’t have a lot of experience shadowing with designers in my work, so it feels hard for me to know where to start. I am curious to know more what kinds of questions designers ask when they first start a new role or position. How do you learn??
---
### Author:  [@Toria](https://discourse.opensourcedesign.net/u/Toria)
#### Post date: [July 10, 2021, 5:44am UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/4 "2021-07-10T05:44:00Z")
I think this is me too. How do i know how to contribute, what to contribute too and if i can work with someone to teach while we contribute together, it would be awesome.
---
### Author:  [@nim](https://discourse.opensourcedesign.net/u/nim)
#### Post date: [August 5, 2021, 9:43am UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/5 "2021-08-05T09:43:42Z")
- I think something as self-driven as open source requires the contributors to have a fair bit of context. Especially for us designers we need to know about how a feature/interface fits in with the rest of the software (and not just looking at a piece of code in isolation and fixing it). So maybe a chance to familiarise yourself with the software and existing designs can be helpful to see if it’s a good fit for the designer or not?
- Many designers turn to open source because of how welcoming it is as a community, and to gain some real world experience, so especially if a job posting is not paid, I think it’s important to mention that it’s a learning process for everyone.
- General job posting info about time commitments, company culture if applicable, etc
What do you think? Did anyone have different experiences?
---
### Author:  [@jwf](https://discourse.opensourcedesign.net/u/jwf)
#### Post date: [December 12, 2021, 9:45am UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/6 "2021-12-12T09:45:57Z")
In the [SustainOSS Design & UX working group](https://sustainoss.org/working-groups/design-and-ux/), we are exploring a publishing mechanism to share best practices across a range of topics, which could include a how-to article from content in this thread. This is a follow-up for our next meeting on Tuesday, 14 December at 17:00 UTC:
>
>
> \# Summary
>
> Develop a list of key themes about design in open source and map ou…t new content fitting into those themes
>
>
> \# Background
>
> In the \[SustainOSS Design & UX Working Group\](https://sustainoss.org/working-groups/design-and-ux/), we have been talking for a while about documenting our learnings, conversations, and experiences in a more visible medium. I offered the UNICEF O.S. Inventory as a possible home for this documentation. We made a few steps towards collecting data for this documentation, like an open form for \[anyone to submit their favorite design resources\](https://forms.gle/JZZGC16BAQ69cfJe6). But as we discussed today, it would help to take a step back and look at our goal and purpose with documentation, and develop some key themes we want to explore first.
>
> By defining themes, it will be easier for us to build and map out the content we actually want to share and publish. As @Memo-Es said, we all have resources, links, guides, and more that we always try to dig up, but they can be hard to find in the moment when we need them most! So, by developing some common themes, we can use this as a framing for what content we gather and build out.
>
>
> \# Details
>
> I propose these next steps:
>
> 1. @jwflory to create a first-pass list of themes based on content we have discussed in previous WG meetings and from the form submissions
> 2. Review list of themes in our next WG meeting (or asynchronously in this issue)
> 3. Map sub-topics or specific content we wish we had, or things we know of from others, that fit within the list of themes
> 4. Regroup on strategy for creating the content fitting into the identified themes
>
> When we regroup, we can get more specific into answering questions like, "What article or knowledge do we want to share? Do we write it ourselves or create a list of other resources? What gaps exist in the O.S. design space that we could begin filling?"
>
>
> \# Outcome
>
> Path forward on documenting and sharing our learnings becomes more clear. It becomes easier to take first steps of creating new content.
>
> \---
>
> CC: @Erioldoesdesign @Memo-Es @Nolski @mantas @georgiamoon @RichardLitt @jeepurs
---
### Author:  [@Erioldoesdesign](https://discourse.opensourcedesign.net/u/Erioldoesdesign)
#### Post date: [April 30, 2024, 10:52am UTC](https://discourse.opensourcedesign.net/t/can-we-collaborate-on-a-discourse-thread-or-article-about-how-to-write-a-job-posting-that-gets-results/2599/7 "2024-04-30T10:52:41Z")
Update to this thread :DDDDD
We had a really great contribution to an issue re. giving guidance on job posting and I really recommend everyone takes a look 🙂 [Written guidance on how to make a job on OSD successful · Issue #393 · opensourcedesign/opensourcedesign.github.io · GitHub](https://github.com/opensourcedesign/opensourcedesign.github.io/issues/393)