Muse Task HubUnofficial guide

Work · Community report

Build a verified internship directory

After talking with students at AfroTech, @altonpeques says Muse built a free directory of 348 tech internships, fellowships and early-career roles, each checked on the employer's careers page. This page covers how to plan and maintain a verified internship directory, and what the post leaves unshown.

What you can get

Illustration — suggested task flow, not an execution result
  1. Prepare

    The audience and the role types and fields to cover

  2. Ask and review

    Decide the scope before collecting anything: who the directory is for, which role types count, and which fields and regions to include.

  3. Check the result

    A reviewed internship directory with source links, quoted eligibility and a dated changelog; not a guarantee that any role is open, that an applicant qualifies, or that updates run unattended.

The source case

@altonpeques reports that after conversations with students and early-career professionals at AfroTech, they used Muse to build a free directory of 348 tech internships, fellowships and early-career opportunities across engineering, product, design, marketing, sales and business. By their account, every listing was verified on the employer's careers page with eligibility requirements quoted word for word, and the list contains no dead links, closed roles or scraped aggregator dumps. They also say Muse checks for new opportunities daily, removes closed listings and documents each update in a public changelog. The post links to the live list but does not show the prompts used, how the daily checks are set up, or any sample listing or changelog entry, so those details remain the author's description.

A public report by someone outside this library. Not independently reproduced here.

From the source

Source excerpt

After conversations with students and early-career professionals at @AfroTech, I used Muse to build a free directory of 348 tech internships, fellowships, and early-career opportunities across engineering, product, design, marketing, sales, and business.

@altonpeques · Read it at the source · checked

Source excerpt

Every listing was verified directly on the employer’s careers page, with eligibility requirements quoted word for word. No dead links, closed roles, or scraped aggregator dumps. The best part? Muse checks for new opportunities daily, removes closed listings, and documents every update in a public changelog.

@altonpeques · Read it at the source · checked

Quoted from the original posts. Not written by this guide, and not a result produced here.

Suggested prompt

Bring The audience and the role types and fields to cover, A list of target employers or a starting set of careers pages, Where the directory will live and who approves publishing. Source community report, checked 2026-11-12.

Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.

What you need

You supply

  • The audience and the role types and fields to cover
  • A list of target employers or a starting set of careers pages
  • Where the directory will live and who approves publishing

How to try it

Editorial, not from the source

  1. Decide the scope before collecting anything: who the directory is for, which role types count, and which fields and regions to include.
  2. Build a starting list of employers and find each one's official careers page, so every listing traces back to the employer rather than a job board.
  3. Collect listings into a sheet with fixed columns: company, role, location, deadline, careers-page URL, date checked and the eligibility text copied exactly.
  4. Spot-check a sample yourself by opening the careers-page links and comparing the quoted eligibility against the page.
  5. Start a dated changelog for every addition and removal, and review it before each public update.
  6. Re-check listings on a regular schedule and remove any role whose page is gone or marked closed; if you rely on the agent for this, confirm a few removals by hand.

What the author built

@altonpeques describes the project as turning an idea into something useful. Conversations with students and early-career professionals at AfroTech led them to have Muse build a free directory of 348 tech internships, fellowships and early-career opportunities, spanning engineering, product, design, marketing, sales and business.

The post sets a high bar for the list: each listing verified on the employer's careers page, eligibility quoted word for word, and no dead links, closed roles or aggregator dumps. It also says Muse checks for new openings daily, removes closed ones and logs each update in a public changelog. The post links to the live list, but the prompts, the schedule behind the daily checks and any sample entry are not shown.

Why quote eligibility from the employer

Aggregators often copy postings late or trim the requirements, so a reader can apply for a role that has closed or that they do not qualify for. Linking to the employer's own page and copying the eligibility text exactly lets each reader check a listing in one click. In general, the requirements that trip applicants up are graduation windows, enrollment status and work authorization, so give those text space in the listing rather than summarising them.

Keeping the list honest over time

A directory like this goes stale within weeks unless someone re-checks it. A dated changelog that records each added and removed role, with a short reason, shows readers how current the list is and makes mistakes easy to trace. If an agent does the re-checking, open a few removed and newly added listings by hand from time to time to confirm the changes were right.

Limits and confirmation points

Limits to confirm

  • The post does not show the prompts, the setup behind the daily checks, or any sample listing or changelog entry.
  • The claims of no dead links or closed roles and of daily updates are the author's description; the listings were not checked for this page.
  • Postings change quickly, so an employer's careers page stays the authority on whether a role is open and who qualifies.
  • This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.

If it goes wrong

Editorial, not from the source

A listing links to a job board or aggregator instead of the employer
Search the employer's own careers site for the same role; if it is not there, mark the listing unverified or drop it.
The quoted eligibility no longer matches the careers page
Replace the quote with the current text, update the checked date and add a changelog line saying what changed.
Closed roles are still showing in the directory
Open each flagged link, remove roles that are closed or gone, and log every removal with the date.

Common questions

Can Muse build and update an internship directory?

One user reports that it built a directory of 348 roles, verified on employer careers pages, and that it checks daily, removes closed listings and logs updates. The post does not show how this was set up, and this guide has not reproduced it.

What should each internship listing include?

At minimum the company, role, location, any deadline, a direct link to the employer's careers page, the date it was checked, and the eligibility requirements copied exactly.

Why avoid aggregator listings?

They can lag behind the employer or drop details, which leads to dead links and closed roles. The author's directory excludes scraped aggregator dumps for that reason.

Next

Related to this task

  • Organize job interview opportunities A role-by-role application and interview tracker with reviewed drafts, not a promise of interviews or employment.
  • Automatically apply to jobs A day's worth of matching roles found and applications submitted, with you brought in only when something needs a decision, plus a record of which roles were skipped and why.

More in Work

Every work task

Similar tasks

  • Build an automated local events website Creative · A draft local events website and a written list of the sources it pulls from, checked by you before it goes live. This is not a guarantee that listings stay accurate or that organizers have agreed to be listed.

Get recurring task recommendations — ask your own agent to check for relevant updates.