> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-open-source-committee/about/paid-open-source-model-posm/maintainer-retainer/interview-reports.md).

# Interview Reports

Round 1 Interviews: 8 of 15 Applicants selected for various 'Core' and Community Projects.

#### Open Source Committee Interview Report Summary

Following a careful review of the 15 applicants in the first round of the Maintainer Retainer Program (MRP), the Open Source Committee (OSC) selected 8 individuals for onboarding. This selection process included separate interviews with project teams (when required) to ensure strong alignment and cohesion. Overall, the committee evaluated an exceptionally strong cohort of candidates, characterized by deep technical expertise within the Cardano ecosystem, and a consistent commitment to collaborative, professional open-source contribution.

{% file src="/files/oh3H8fjPvff3UVhfIdqp" %}

Round 2 Interviews: 8 of 11 Applicants selected for various 'Core' and Community Projects.

#### Open Source Committee Interview Report Summary

Following a careful review of the 11 applicants in the second round of the Maintainer Retainer Program (MRP), the Open Source Committee (OSC) selected all 11 individuals for onboarding. During the contract phase, 3 Maintainers chose to step away from the program for personal reasons. This selection process included separate interviews with project teams (when required) to ensure strong alignment and cohesion. Overall, the committee evaluated an exceptionally strong cohort of candidates, characterized by deep technical expertise within the Cardano ecosystem, and a consistent commitment to collaborative, professional open-source contribution.

{% file src="/files/bnmCMXZMHGRDKkWEHoTw" %}

Round 3 Interviews: 7 of 10 Applicants selected for various 'Core' and Community Projects.

#### Open Source Committee Interview Report Summary

Following a careful review of the 10 applicants in the third round of the Maintainer Retainer Program (MRP), the Open Source Committee (OSC) selected 7 individuals for onboarding. The 3 Maintainers that were not selected, were unable to adequately answer interview questions, additionally it was difficult to prove ties to and experience within the Cardano ecosystem. This selection process included separate interviews with project teams (when required) to ensure strong alignment and cohesion. The final round of interviews featured a cohort of candidates that presented unique technical expertise inside and outside of the Cardano ecosystem. The selections reflect a focused approach to support desirable community projects and fulfillment of a mission to expand the reach of the Maintainer Retainer Program.<br>

{% file src="/files/z4H9Rs4TkUyDEIXmX83V" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/about/paid-open-source-model-posm/maintainer-retainer/interview-reports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
