> Markdown version of [/jobs/ext/3960936-open-source-engineer](https://www.wearedevelopers.com/jobs/ext/3960936-open-source-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Open Source Engineer

- **Company:** SIDEGUIDE TECHNOLOGIES INC.
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Salary:** $235,000 - $260,000
- **Contract:** Permanent contract
- **Skills:** Computer-Aided Design, Artificial Intelligence, Code Review, Github, Open Source Technology, Juniper, Computer-augmented Design and Manufacturing, Api Design
- **Published:** October 27, 2026
- **Apply:** https://www.careerbuilder.com/job-details/open-source-engineer-san-francisco-ca--b03f3acd-a93d-4d40-ac8c-d7a858b7e7dc

## About the Role

Open Source, Open Source, Code Reviews, CAD/CAM (Computer-Aided Design/Computer-Aided Manufacturing), GitHub, Juniper Networks M-Series, Artificial Intelligence (AI), Data Collection, Customer Relations, Problem Solving Skills, * Someone who wants community work to substitute for shipping code

 * Someone who needs a mapped-out roadmap before they'll make a scope call
 * Someone who's used open source but never maintained or owned a repo of real scale

## Description

Firecrawl is looking for a high-agency engineer to own our open source work. That starts with the main Firecrawl repo (180k+ stars and counting, top 50 repositories of all time), which should stay the easiest thing in the category to self-host. It extends to the context primitives we're open sourcing now, starting with anydoc, our document parsing engine. You'll keep the core repo healthy and growing, build out the primitives, and think about what makes each one spread on its own.

This is not a developer relations role. We want an engineer who ships the code, reviews the PRs, and makes the repos better every week. Community instincts help, but engineering quality, shipping velocity, and a track record of work people actually use matter most., * Own the main Firecrawl repo end to end: triage issues, review PRs, cut releases, write docs

 * Keep the self-host experience easy: clone it, run it, keep it running, no surprises
 * Build out new context primitives, starting with anydoc, our document parsing engine
 * Make the calls on scope and API design for what belongs in a primitive and what doesn't
 * Think about what makes an open source project spread on its own, and build toward that
 * Ship code and review PRs every week. This is an engineering seat, not a community seat, * A real open source track record: maintaining a popular repo, or landing significant contributions to one
 * You care about the self-host experience and know what makes a repo easy to clone, run, and keep running
 * Comfortable owning a repo end to end, from triaging issues and reviewing PRs to cutting releases and writing docs
 * You've built parsers, crawlers, browser tooling, or developer libraries, and have taste in what belongs in a primitive and what doesn't
 * You understand how open source turns into adoption and pay attention to why some projects take off
 * High agency. Happy to make calls on scope, API design, and what gets merged
 * Often a maintainer, ex-founder, early startup engineer, or builder with impressive public work