Case File: Coram AI Ashby Board, Access Date November 3, 2026

This case study is a dated research file, not a placement story. We opened Coram AI's Ashby careers board on November 3, 2026, counted what was titled, labeled the soft CTA, and wrote a coverage decision. The point is the file structure. Without an access date, a Series B banner ages into fake evergreen demand.

Primary sources: Coram AI Ashby board and the General Interest Series B posting.

Case header fields

Employer: Coram AI. Board URL: jobs.ashbyhq.com/coram-ai. Access date: November 3, 2026. Soft CTA present: yes — "General Interest - Coram AI is Hiring (Series B & Growing)." Titled roles present: yes — board listed on the order of forty-plus open positions spanning sales, engineering, marketing, HR, and operations. Researcher: RecruitHacker desk note for this batch.

What we logged as titled examples

Sales: Account Executive in Atlanta, New York City, Lehi, Scottsdale; Associate AE and SDR lines in Sunnyvale and Scottsdale; Channel Sales Manager in Chicago, Scottsdale, Sunnyvale, New York City; Tech Sales Manager in New York City. Engineering: Member of Technical Staff lines in Sunnyvale, Bangalore, and London across frontend, full stack, infrastructure, real-time systems, and security. Other: Growth Manager and Product Designer in Bangalore; Brand and Design Lead and some marketing seats US Remote; Technical Recruiter and HR leadership in Sunnyvale.

Each example was stored as title | city | work mode. We did not store "Coram / Series B hiring" as a title.

What we logged as soft CTA

The General Interest posting states Series B closed, hiring is accelerating across functions and offices, and the hiring plan may move faster than the page. That is useful context for a watch note. It is not a submit-able req. In the case file, soft CTA sits in its own field with a one-line paraphrase, not in the titled-role table.

A careers case file without an access date is a rumor with formatting.

Coverage decision written the same day

Active this week for a US on-site GTM desk: Account Executive Lehi and Scottsdale; SDR Sunnyvale. Parked: Bangalore growth and product design; London engineering; soft CTA. Reason: desk coverage is US on-site sales, not global engineering. The decision is disagreeable on purpose. Partners can argue hubs. They should not have to guess whether Series B soft CTA was treated as a role.

Outcome of the method

No candidates were submitted in this case. The deliverable is the dated file. If a partner asks next month whether Coram was "hiring everywhere after Series B," the file answers with access date, titled examples, and the parked soft CTA. That is stronger than a screenshot without a date.

Who this case method is not for

Teams that only work exclusive retained orders may not need Ashby case files. Teams that scrape aggregators without employer URLs will not get soft-versus-titled labels. Teams that refuse to write coverage decisions will still spray resumes at Bangalore rows while talking about Lehi.

Replicable checklist

1. Access date and URL.
2. Soft CTA yes/no with exact title text.
3. Titled sample table with city and mode.
4. Coverage decision for the week.
5. Explicit non-claims: no invented headcount, no agency authority, no pay bands unless copied from a titled posting.

Reuse the same five fields on the next multi-hub board. The employer name changes. The discipline does not. ## What we explicitly did not claim

We did not claim agency authority on any Coram seat. We did not invent headcount from "hiring across the company." We did not treat Bangalore and Lehi as one market. We did not copy compensation from one titled posting onto another. We did not use third-party aggregator cards as the system of record.

Failure modes this case is meant to prevent

Failure one: a CRM note that says only "Coram Series B — hiring" with no date. Failure two: a shortlist built from the soft CTA audience description. Failure three: a partner handoff that forces the partner to re-open Ashby to learn which city you meant. The dated file prevents all three if you keep it updated.

Cadence after day one

Forty-eight hours later, re-open the board. If Lehi AE closed, strike it from active coverage the same morning. If a new titled seat appears in Chicago channel sales, add a new row with a new access stamp. Soft CTA can remain yes without changing titled coverage. The banner is sticky. Your shortlist should not be.

Store the case file where a partner can open it without Slack archaeology: employer, date, URL, soft CTA stub, titled table, coverage decision. Five fields. If any field is missing, the case is incomplete. Incomplete cases are how Series B folklore replaces research on a boutique desk that cannot afford folklore.

If you teach this case in a team meeting, project the Ashby board live and fill the five fields in real time. Do not lecture from a stale screenshot. The access date only matters if people see you write it while the board is open. That habit transfers to the next employer faster than another slide about process.