1. LandOffer
  2. Blog
  3. All articles
  4. Climate Draft vs. ClimateTechList: VC Portfolio Coverage or Company-Site Tracking?

Job search

Climate Draft vs. ClimateTechList: VC Portfolio Coverage or Company-Site Tracking?

Compare venture-portfolio discovery with company-career-page tracking under the same engineering and location constraints; public totals alone do not establish useful coverage.

10 min readLandOffer team

Climate Draft is worth exploring when you want a map of venture-backed climate startups and their investor portfolios. ClimateTechList is a practical starting point when you want to search jobs collected from company careers pages and investigate what those companies build. For our October 13, 2026 session, ClimateTechList's title and location filters worked; Climate Draft's linked job board returned a not-found page. Start with the accessible source, while treating that failure as a dated observation rather than a verdict on its future availability.

The portfolio frame describes which employers Climate Draft focuses on. Company-site tracking describes how ClimateTechList collects vacancies. Venture-backed companies can appear in a careers-page aggregator too. Neither description establishes which source contains more jobs you can actually take. Compare the additional relevant employers each introduces under your location, experience and technical constraints.

LandOffer publishes this comparison and offers job-search tools. You can also browse recent roles on LandOffer.ai, then verify a promising role with its employer. This review uses public pages and browser observations; we did not create accounts, subscribe, submit applications or test recruiting outcomes. The reader cases below are fictional.

A venture portfolio tree and a company careers index lead into a shared climate employer map, illustrating two overlapping discovery frames

Portfolio coverage and company-site tracking answer different questions

Climate Draft's homepage describes venture-backed climate startups and jobs across climate investors' portfolios. It identifies the project with Lowercarbon Capital and describes access as free. That frame can help a reader asking, “Which startups are part of this climate investing ecosystem?” Its resources and events provide additional ways to investigate the sector.

Investor backing can help organize employer research. Assess current software vacancies, financial context, team responsibilities and country availability separately. A portfolio can include a company without a current matching vacancy, so save it as an employer to watch rather than an application ready to prepare. Even a promising technical mission may produce mostly field, manufacturing or commercial openings at the moment you search.

ClimateTechList's explanation describes a company directory alongside jobs aggregated directly from employers' careers pages. Its company profiles aim to explain the climate problem and why software matters to the business. The site also distinguishes paid listing promotion from its collection process. Those are publisher descriptions, not independent proof of completeness, neutrality or hiring quality.

Its older curated-company methodology, dated July 28, 2023, considers climate impact, growth and the importance of software. It explicitly says that curated list is not comprehensive. Do not assume those selection criteria are an exhaustive description of every organization currently present in the wider job tracker. Company selection and job ingestion are separate questions.

Ask whether the source introduces an employer you want to investigate, then whether its requisition fits your constraints. This preserves the value of a narrower portfolio view without mistaking an aggregator's larger-looking inventory for a better personal shortlist.

Compare the same criteria before choosing a source

The following matrix combines official descriptions with our dated public-access observations. Unknowns remain visible because we could not inspect Climate Draft's current board inventory.

Criterion Climate Draft ClimateTechList What it changes for you
Employer discovery frame Venture-backed climate startups and VC portfolios, according to its homepage Company directory plus company-career-page aggregation, according to its About page Choose the frame that adds relevant employers to your existing list
Software context Startup and climate ecosystem context; current board details were unavailable in our visit Profiles aim to explain the business and software's role Read the company explanation, then confirm actual engineering ownership in the vacancy
Public access observed Homepage readable; linked Jobs destination returned not-found Jobs page, title/location inputs and individual description readable without signing in ClimateTechList supported immediate public research in this session
Location and title narrowing Current controls unverified Title and location inputs produced a filtered table; Remote selection subsequently remained loading A visible control does not establish a completed result
Freshness evidence Current update cadence and inventory not verified Jobs page describes daily collection and first-posted ordering Check the employer page before spending time on a packet
Additional participation Homepage links events, resources and joining routes Newsletter, alerts and talent-collective routes are separate Browsing a vacancy does not mean you joined a recruiting program

This matrix supports a bounded choice: begin with ClimateTechList for the observed public job-search task. Revisit Climate Draft when its board is accessible if the portfolio angle serves your search. It does not support a claim that either source has exclusive access, better employers or a higher interview rate.

What the completed search session actually showed

We opened the Jobs link on Climate Draft's official homepage. Its destination, jobs.climatedraft.org, redirected to a not-found screen. We could read the main site's description, but could not run a comparable board search. An inaccessible page is not a zero-job result. It also does not establish that the project has shut down.

On ClimateTechList's Jobs page, we entered software engineer in the position-title field and United States in the location field. The embedded table displayed filtering by Position Title and Location. After the title and location view loaded, it showed 401 records in Latest Job Openings and one in Featured Job Openings; we did not inspect all records. These were displayed group counts, not 402 independently verified, distinct vacancies suitable for a particular candidate.

The visible rows included software internships, embedded work and a software/AI title. An Infravision result showed Buda, Texas and an onsite-only tag; a featured XyloPlan result showed United States, Remote. This demonstrates why a software title and country match still require work-setting, seniority and duty checks. It does not establish either candidate's eligibility.

Action completed October 13 Observed result Decision supported
Follow Climate Draft's official Jobs link Not-found destination Use another accessible discovery route now; leave Draft coverage unknown
Enter software-engineering title and US location on ClimateTechList Filtered table with mixed seniority and technical specialties Inspect individual rows; do not treat the total as a qualified shortlist
Select Remote on that page Embedded view continued showing a loading message in saved follow-up observations No remote-filter count or result set accepted
Open Aurora Solar from the separate example table Description led to an employer-hosted overview with more explicit work-setting information Use the employer requisition to resolve the listing's uncertainty

There is an important interface boundary here. ClimateTechList also displayed a separate example table lower on the page. That sample remained visible while the embedded view loaded. We did not count it as the filtered output. Aurora came from that separate sample, so we do not claim it belonged to the completed title/location query.

Follow one lead through to its employer

The Aurora Solar listing was titled Senior Software Engineer, Computation. Its summary identified the United States and full-time work, while the remote field directed readers to the job post for details. We followed its employer link rather than interpreting that field as either remote approval or an onsite requirement.

The Aurora employer overview specified United States, Remote and Full time when inspected. It described backend computation for solar and electrical design, requested at least five years of professional software experience, and named hands-on simulation or optimization experience. An advanced degree appeared among the nice-to-have qualifications. This was a readable employer requisition during our visit; we did not submit its application or establish future availability.

The completed check changed the note from “US software lead; work setting unresolved” to “US remote role; computational experience needs assessment.” That is useful progress even without applying. The employer page resolved one uncertainty while exposing another. A generic backend background alone does not demonstrate the requested simulation work.

An illustrated job listing with an unresolved remote tag is compared with an employer requisition showing US remote work and a computational-experience check

The next decision is whether you can show simulation or optimization work, the specific experience this requisition requests. If your work includes optimization services, numerical systems or simulation infrastructure, identify the specific contribution you can explain. If it does not, keep the requirement visible instead of rewriting general API work as mathematical modeling experience. The board helped discover the lead; the requisition supplied the decision detail.

Two readers can reasonably choose different starting points

June is a fictional backend engineer who is open to relocating and wants to understand venture-backed climate startups before selecting applications. She has no fixed target employer and values a map of companies connected through climate investors. Climate Draft's documented portfolio frame fits that research objective. Its failed board means she uses the readable resources for orientation and defers any claim about its vacancies until access returns.

For June, ClimateTechList adds a different task: reading company explanations and checking the available work. She starts there for an actual opening in this session, while keeping the portfolio research question separate. Her completed decision is to use ClimateTechList now for accessible leads and return to Climate Draft for startup discovery. She has not concluded that either list is a complete climate-employer universe.

Mateo is a fictional senior software engineer who needs US remote work and is already familiar with several climate employers. His immediate problem is finding an eligible requisition rather than learning which investors back startups. ClimateTechList's public title/location search is the more useful starting point under the observed conditions, but its unfinished Remote view prevents him from relying on a remote result count.

Mateo instead follows the Aurora example to the employer overview. The US remote setting fits his stated location preference. He still needs to compare his experience with the computational requirement before deciding to apply. His completed disposition is “location fit confirmed; technical fit unresolved.” If his existing employer alerts already surface this role, adding another board has not created an additional opportunity.

These choices differ because the readers need different information. June values employer discovery; Mateo values a workable vacancy under a hard location constraint. Neither case predicts a recruiter response or implies that portfolio membership validates the company's climate impact.

Read freshness and duplicate signals carefully

ClimateTechList's daily-update description explains its intended collection cadence. It does not guarantee that every source is reachable, that every removed job disappears immediately, or that a first-listed date equals the employer's original publication date. A recently surfaced record can still point to a role that has changed. Record when you checked the employer and keep that date separate from the board's label.

We also saw inconsistent volume signals across ClimateTechList surfaces: its Jobs header, embedded table and newsletter material did not show a single reconciled total. We have not established why. Differences could reflect scope or update timing, but those explanations remain hypotheses. None is a sound basis for declaring a coverage winner against a board we could not query.

For your own shortlist, keep the employer, requisition URL, title, location and first discovery source together. If both boards lead to the same employer requisition, retain one opportunity with two discovery sources. If titles match but requisition identifiers or locations differ, inspect them before merging. This makes the second source's value concrete: it may add a distinct employer or role, rather than merely another copy of something you already found.

Keep optional participation separate from job discovery

Public browsing was enough for the observations in this review. Newsletter enrollment, alerts and talent-collective participation involve additional actions and information. ClimateTechList's collective description says submitted profiles may be shared with interested companies and that it will contact candidates when there is interest. That is a recruiting route with its own terms, not a placement commitment or a prerequisite we encountered for reading the sampled role.

Likewise, a learning or community link does not establish that a course is required to apply for a climate job. Evaluate any separate program's scope, schedule and price against a need you actually have. This comparison did not test program enrollment or paid services.

Start with one discovery source that answers your immediate question. Open one employer requisition and save its location, central experience requirement and your decision: investigate, consider applying or set aside. Add the other source when it introduces a useful employer or role you have not already reviewed. You can use LandOffer.ai's recent-role search for another discovery session, with the same employer-verification standard.

Sources and Further Reading