The screen is mostly green and brown. In QGIS, a thin yellow polygon wraps a hillside where the topsoil has slipped, the old terraces have collapsed and only goat-cropped scrub holds on. The question on your desk is easy to ask and slow to answer: can this ground become a credited carbon project? That question sits behind most remote carbon project developer jobs, and this listing is one of them. It is full-time, fully remote, open worldwide and paid $80,000 per year (USD).
If you have wondered what a carbon project developer does, the short honest answer is this. You build the case, in maps, numbers and prose, that a piece of land or an activity will keep greenhouse gases out of the air compared with what would have happened anyway. Then you prove it to people paid to doubt you.
The rest of this page follows one hypothetical project, a degraded hillside to be restored with native trees, from first sketch to credit issuance. That sequence is the carbon project developer job description.
Every project starts in QGIS. You load satellite imagery, a land cover layer, slope and soil data, and whatever cadastral maps exist. Then you draw the boundary. It sounds clerical. It is not.
Anyone who has worked a forest range learns that a line on a map is a promise. Draw it around a patch that was already regrowing on its own and you have a problem. Include a strip the neighbour grazes his cattle on and you have another. At the screening stage you are asking:
The output: clean shapefiles, a land use history and a memo on whether the site deserves another month of your time.
Verra runs the Verified Carbon Standard, and under it sit methodologies: rulebooks for particular project types such as afforestation and reforestation, avoided deforestation, improved forest management or changes in agricultural practice. Our hillside points toward a restoration methodology, but the fit has to be checked line by line.
Reading a methodology the way you would read a contract, then tying each condition back to the polygons you drew, is what employers mean when they ask for QGIS and Verra methodologies in the same breath.
Credits come from a difference. The baseline scenario estimates the carbon story if nobody steps in: the slope keeps eroding, the scrub gets cut for firewood, the soil keeps losing carbon. The project scenario estimates stocks and emissions once planting and protection begin, minus what the project itself emits.
You will build both in spreadsheets or scripts, using growth models, allometric equations and default factors from the methodology. Conservative choices matter here. When a parameter is uncertain, the methodology usually expects the value that yields fewer credits, and a good developer picks it without being told twice.
All of this lands in the project design document, the PDD. It describes the site and its boundary, the chosen methodology and how each condition is met, the baseline and project calculations, the additionality argument, the risk and permanence assessment, the monitoring plan and the record of stakeholder consultation. A strong PDD reads as a single argument, with every number traceable to a source or a measurement.
Writing project design documents takes up a large share of desk time in this role. Expect drafts, tracked changes and rewording until a stranger could follow the logic without phoning you.
An independent validation and verification body reviews the PDD against the standard. Its auditors raise findings, and you answer them with evidence or revise the design.
In parallel you coordinate with landowners and community partners: confirming who benefits, how decisions are made and how complaints get heard. In forestry work, plantations tend to survive where the village understands why the fence is there. Once validation clears and monitoring shows real growth, verification follows and credits can be issued on the registry.
Most employers want a degree in environmental science, forestry or engineering. Forestry brings inventory methods and growth models; engineering suits energy or methane projects. Alongside the degree, this role asks for three or more years spent developing carbon projects.
The working skills, in plain terms:
A carbon project developer resume should show these as outcomes: the projects you worked on, the methodology used, the stage each one reached and which sections you personally wrote or calculated.
Learning how to become a carbon project developer is mostly a matter of stacking experience. Common starting points are forest inventory, GIS analysis, environmental consulting and monitoring or verification work.
No single carbon project developer certification is required. A carbon project developer course on carbon accounting or on one standard can teach you the vocabulary, and reading published PDDs and validation reports on the Verra registry costs nothing and teaches a great deal. A frank word for anyone searching for carbon project developer jobs no experience required: this listing asks for three years, so newcomers are better served by entry-level analyst or GIS roles as a stepping stone.
For carbon project developer interview questions, be ready to talk through a boundary decision, defend a conservative parameter and explain how you would answer an auditor's finding.
The carbon project developer salary per year here is $80,000 (USD), full-time. That figure applies to this listing only; it is not a survey of the market.
Carbon project developer jobs remote worldwide, like this one, are mainly screen work: QGIS, spreadsheets, documents and video calls across time zones. People searching for carbon project developer work from home jobs should know that field site visits may be part of some roles in this line of work, for scoping, consultation or audits. This listing does not promise travel. If you do go, pack for rain.
A carbon credit broker sits on the selling side. Brokers match buyers with credits that already exist, negotiate terms and handle transactions. A developer works upstream, creating the project those credits come from.
Organisations such as South Pole are examples of the kind of firm that develops projects. They are named here only to show the type of organisation active in this field, not as the employer and not as a claim that they are hiring.
Are carbon offset projects legitimate, or greenwashing? Some are solid and some have not held up to scrutiny. Anyone in this work should be able to name the weak points:
The developer is the first person who can get these right or quietly get them wrong. Pick conservative baselines, draw honest boundaries and write the uncertainty down where an auditor can see it. That is the part of the job worth signing your name to.