FSOSD: FINOS Financial Services Certified Open Source Developer
Browse certifications
Exam Resources
Official learning paths, exam details, skills measured, and community resources to supplement your study.
About this study guide
The FINOS Financial Services Certified Open Source Developer (FSOSD) certification assesses how developers work with open source software in financial institutions. The scope includes community conduct, licensing, dependency risk, contribution approvals and the effect of regulation on public collaboration.
This is an independent Guided study resource, not issuer training or exam content. Its hypothetical questions are original, not recalled or reconstructed exam items. The Linux Foundation and FINOS own their respective certification names and marks. Guided is not affiliated with or endorsed by either organization and uses no official logo or badge.
Exam facts
| Detail | Published information |
|---|---|
| Certification identifier | FSOSD |
| Format | Online, proctored multiple-choice exam |
| Duration | 90 minutes |
| Actual exam question count | Not stated on the current certification page |
| Passing score | Not stated on the current certification page |
| Prerequisites | None stated |
| Validity | Two years |
| Official page | FSOSD certification details and enrollment |
| Status checked | Enrollment available on 1 November 2026; no retirement notice found on the current certification page |
Check the current multiple-choice exam instructions and candidate handbook before booking. Delivery details and program terms can change.
Domains and practice coverage
The practice bank contains 250 original questions allocated to the five published domain weights. That is the Guided practice count, not the issuer’s exam length.
| Official domain | Weight | Practice questions |
|---|---|---|
| Ethics and Behavior | 10% | 25 |
| Open Source Licensing | 18% | 45 |
| Consuming Open Source | 26% | 65 |
| Contributing to Open Source | 28% | 70 |
| Regulatory Impact on Open Source | 18% | 45 |
| Total | 100% | 250 |
Ethics and Behavior
Understand how to engage respectfully with maintainers and communities, choose the appropriate channel and handle an escalation. Distinguish community conduct from your firm’s internal decision-making authority. A public issue is not the place to publish confidential evidence merely to explain a problem.
Open Source Licensing
Identify the software, applicable license and use case before deciding what obligations are triggered. Distinguish a license identifier from the license text, copyright permissions from ownership, and contribution certification from assignment. A Developer Certificate of Origin sign-off is not a copyright transfer; the effects of a contributor agreement depend on its actual terms.
Consuming Open Source
Study dependency identity, inventory, provenance, vulnerability identification, maintenance and approval evidence. Assess both direct and transitive dependencies in the context of a financial firm’s operational needs. A software bill of materials, security score or project badge supplies evidence; none guarantees that software is safe or that all obligations have been met.
Contributing to Open Source
Work through contribution risks and benefits, employer and project permissions, publication review and the boundaries between firm and personal projects. Consider code, data, logs, documentation and third-party material separately. An open source program office can coordinate engineering, security, Legal and Compliance without replacing their authority.
Regulatory Impact on Open Source
Understand why business communications, public posts and contribution records may fall within a firm’s supervisory procedures. Separate an organization’s stated policy from a legal requirement. FINRA guidance applies to its specified member-firm and activity context, not automatically to every bank or jurisdiction.
For data and intellectual-property questions, check the relevant facts, policy and authorized advice. Do not infer that public availability, anonymization, personal time or an open source license alone permits publication.
A practical study plan
- Map the five domains. Give each competency its own notes and identify the decisions it requires.
- Read primary evidence. Start with the FINOS open source compliance handbook and contribution requirements.
- Examine a dependency. Identify its version, license, source, maintenance activity and known-risk evidence without installing it into a production system.
- Review a hypothetical contribution. Separate code ownership, third-party permissions, sensitive material and publication approval.
- Keep regulatory scope explicit. Note which entity, jurisdiction, activity and firm policy each example assumes.
Give contribution and consumption the largest share of preparation time: together they account for 54% of the published blueprint.
Independent practice
Guided Financial Services Open Source Study Practice contains 250 original selected-response questions. Twenty questions are free; full practice access is US$9 for one year. Explanations, incorrect-option feedback, hints and public source links support review.
This resource is not legal advice, an official exam voucher, authorized training or a promise of complete exam coverage or a passing result. FINOS practical guidance is not universally binding law, and organizational controls in hypothetical scenarios are stated assumptions.