IS Jobs guide
The academic job market can already feel like a lot. IS Jobs brings together a community-maintained list of Information Systems openings and a private place to organize your own search.
You can browse and contribute without an account. Sign in when you want to save a search, track applications, or connect an AI assistant to your account.
Browse
IS Jobs groups openings by academic job-market season. The Jobs link opens the current season. Seasons lets you look back at earlier years, though those openings may no longer be active.
Start with the current season
Open Jobs to see positions published for this academic hiring year.
Narrow the results
Search by position, university, or department, or choose a job type, region, tenure-track status, or Carnegie research designation. Carnegie covers U.S. institutions: matched schools outside R1/R2/RCU have no research designation, while non-U.S. or unmatched schools appear as unavailable. Results update automatically. If you sign in, Save filter keeps that search for later; it does not send alerts.
Check the employer’s posting
Open a job on IS Jobs, then follow the original posting to confirm the deadline, requirements, and application instructions.
Private tracker
The tracker is your private application list. Use it to keep jobs, stages, deadlines, notes, and history together. You need an account to use it.
Jobs you save, application stages, deadlines, notes, and history do not appear on public listings. The website shows your tracker only in your signed-in account.
Start with one question: is the opening already listed on IS Jobs?
Already listed on IS Jobs
Open the job and select Save to tracker. If you are not signed in, select Sign in to track. After signing in, you will return to the listing; select Save to tracker once more.
Browse public jobsNot listed on IS Jobs
Select Add private job. If you need to sign in first, open Tracker afterward and choose Add private job. Keep private is already selected, so the job will not be added to the community list.
Add a private jobWant other candidates to find an unlisted job too? Add it to the community list.
Every tracked job starts in Watch. On the board, drag a card or use its status menu when something changes; switch to the table for a compact list. You can move a job backward to correct a mistake, and open it to add a note or review its history.
Jobs you may apply to · Applications in progress
Applied · Screening
Interview · Offer
On-campus interview visits
Accepted · Rejected · Withdrawn
Community list
If an Information Systems job is missing, you can share it with the community. You do not need an account to submit a public listing.
Only saving a job for yourself? Use Add a private job instead.
Check whether it is already listed
Search the current season first. The form also checks for likely duplicates.
Use the original employer posting
Copy the position title and university carefully. Include the original posting link, the posted date, and the deadline when provided. If applications continue after priority review, mark the date as Priority, then rolling.
Submit the form
After the form accepts the submission, the listing appears immediately—there is no review step.
Signing in is optional. It changes how your contribution is credited, not whether the job can be published.
The listing is published without your name. It cannot be added to an account’s contribution history later.
The listing shows your display name by default, and the submission appears in your account’s contribution history. Select Submit anonymously to hide your name from the public listing.
A listing submitted while signed in belongs to that account and can be edited from its contribution history. API and MCP clients with jobs:edit can also edit or unpublish listings within the account’s authority; unpublishing archives rather than deletes the record. Moderators, admins, and people with a moderator grant for the listing’s season can manage it directly. Republishing archived listings requires moderator authority.
A connected tool that should only recommend a correction can request jobs:suggest instead. Its evidence-backed suggestion enters a private moderator queue and never changes the public listing automatically. For a listing you do not own or moderate, you can also follow its Season maintainers link and send the exact correction with the employer’s original posting. Do not submit the same job again as a correction.
For moderators
Moderators keep the shared job list accurate without gaining access to candidates’ private account data. Sign in with the account that has your moderator permission to open the moderation queue.
Season moderators can manage public listings only for seasons assigned to their account. The moderation queue automatically limits them to jobs within those seasons.
Global moderators and administrators can manage listings across every season. Administrators can separately manage accounts; the global moderator role cannot.
The Jobs and AI suggestions tabs separate listing review from agent-proposed corrections. Attention counts show how many items need review, and both views include only jobs within your moderation authority.
Verify the source posting, then approve the listing for publication or reject it.
Edit incorrect details or archive a stale or invalid opening. Archiving removes it from public views and archives the record instead of deleting it.
Republish an archived listing, or reopen a rejected listing so it can be reviewed again.
Suggestions are grouped by job. Compare the current and proposed values, review the agent’s rationale and evidence, then apply selected corrections or decline the suggestion.
Moving a listing to another season requires authority for the destination season as well as its current season. A season moderator cannot use a move to extend their access beyond assigned seasons.
If a job changed after a suggestion was submitted, conflicting fields cannot be applied from the queue. Open the full edit form to review those fields directly.
Each public season page credits its assigned season moderators. It also credits global moderators after they record a moderation action on a job in that season.
Moderator permission does not reveal account information, private trackers, or saved searches. It also does not allow account management, which is restricted to administrators.
Account access
The shared job list is open to everyone. An account is for saved searches, your private tracker, contribution history, and connecting an AI assistant through MCP.
| What you want to do | Access |
|---|---|
| Browse current and past job-market seasons | No account needed |
| Submit a missing public job | No account needed |
| Edit a public job you submitted | Sign in required |
| Manage jobs in an authorized season | Moderator permission required |
| Save a set of search filters | Sign in required |
| Use the private application tracker | Sign in required |
| See your contribution history | Sign in required |
| Connect an AI assistant through MCP | Sign in required |
Both choices create a full IS Jobs account. Passkey appears first because it avoids creating another password, but you can use a username and password instead.
Use the fingerprint, face scan, screen lock, or password manager already connected to your device. You do not create an IS Jobs username or password during sign-up. After signing in, you can name and connect up to 10 passkeys.
On the sign-in or sign-up page, choose Use username and password. Pick a password of at least 15 characters; a long passphrase works well. IS Jobs does not collect an email address for login, but you can change your password while signed in by entering your current password.
While signed in, you can change your password and add or revoke up to 10 passkeys. Changing your password requires your current password. Adding a username and password to a passkey-only account requires verification with an existing passkey. A passkey change requires your current password when one is connected, or verification with an existing passkey otherwise.
Successful credential changes sign out your other browser sessions while this browser stays signed in. IS Jobs cannot recover a locked-out account by email, so keep at least one working sign-in method connected.
After signing in, open Dashboard → Account → Sign-in methods to manage your password and passkeys. Every connected method opens this same account and private tracker.
Optional
Most people can stop here. This section is only for connecting an AI assistant, research tool, or script to IS Jobs.
Use MCP for a compatible AI assistant. Use the REST API when you are writing code or working with a research script.
MCP lets a compatible assistant search and open published jobs, submit a missing listing, propose evidence-backed corrections for moderator review, and work with your private tracker. It can edit or unpublish listings you submitted only when you separately grant edit access; accounts with moderator authority can also manage listings within that authority. Republishing archived listings requires moderator authority.
Copy this MCP server address into your assistant:
https://isjobs.xyz/mcpIf your assistant supports OAuth, IS Jobs opens in your browser so you can sign in and approve access. The connected tool does not receive your passkey, username, or password.
If the client asks for a personal token instead, create one in API access settings and follow the client’s instructions for adding a bearer token.
Published jobs are available from /api/v1/jobs without a token. Submitting a job, proposing a correction through /api/v1/jobs/{slug}/suggestions, or accessing a tracker requires an OAuth connection or personal token.
The full list of routes, filters, request fields, and responses is in the OpenAPI 3.1 document.
Choose only the permissions it needs. Job access and tracker access are separate, and reading does not automatically include changing anything.
| Permission | What it allows |
|---|---|
Read jobsjobs:read | Search and open published jobs through MCP. Public REST job reads do not need a token. |
Submit jobsjobs:write | Submit a job to the shared list using your account. Successful submissions appear immediately. |
Suggest job correctionsjobs:suggest | Propose evidence-backed public metadata corrections for moderator review without changing the listing. |
Edit or unpublish jobsjobs:edit | Edit or unpublish listings you submitted. Accounts with moderator authority can also manage listings within that authority; moving or republishing listings requires moderator authority. |
Read trackertracker:read | View your private tracker and its history. |
Manage trackertracker:write | Add, edit, or permanently delete tracker entries and their history. |
Grant jobs:suggest when a connected agent should identify corrections without receiving edit access. Every suggestion must include the proposed public-field changes, a plain-text rationale, and one to five HTTP or HTTPS evidence links. Submitting a suggestion creates a private moderation record; it never changes the public job automatically. An authorized moderator can apply selected proposed fields or decline the suggestion from the AI suggestions queue.
Include a stable externalId for idempotent retries. Reusing it with the same complete request returns the original receipt; reusing it with any different request data is rejected.
POST /api/v1/jobs/{slug}/suggestions
{
"changes": { "postedOn": "2026-07-15" },
"rationale": "The employer posting supplies the original posting date.",
"evidence": [{
"url": "https://example.edu/careers/123",
"title": "Official employer posting"
}],
"externalId": "audit-example-123-v1"
}suggest_job_edits({
"slug": "assistant-professor-example-university-job-1",
"changes": { "postedOn": "2026-07-15" },
"rationale": "The employer posting supplies the original posting date.",
"evidence": [{
"url": "https://example.edu/careers/123",
"title": "Official employer posting"
}],
"externalId": "audit-example-123-v1"
})A personal token is shown once. Treat it like a password, keep it out of shared documents and source code, and revoke it when you no longer use the connection.
Owner disclosure
A candid explanation of who operates IS Jobs, who can access account data, and the security limits to consider before saving private information.
IS Jobs is currently owned and operated solely by me, Zenan Chen. Community maintainers or moderators may help with different job-market seasons, but their permissions are limited to moderating public job posts. IS Jobs does not give them access to account information or private trackers.
Information you deliberately make public—such as a display name attached to an attributed job submission—remains public as described above. Apart from those choices, community maintainers and moderators cannot view account-level information.
There is no administrative interface for conveniently looking up a person and browsing their private tracker, and I do not intend to inspect individual tracker records. The information is nevertheless stored in the database. As the person who administers that database, I remain technically capable of accessing its contents; a database cannot meaningfully hide its data from its administrator.
If you are uncomfortable associating your identity with private tracker data, you can choose how much information to keep on IS Jobs.
Your tracker account does not need a recognizable display name. Use a pseudonym if you do not want private tracker entries associated with your public identity.
Use one account under your public name for attributed job submissions and another account under a pseudonym for your private tracker. IS Jobs does not link the two accounts, so it does not identify them as belonging to the same person.
Use the public API with a coding agent or your own software to build a private tracker that stores no tracker data on IS Jobs. If you open-source or share an IS Jobs-compatible tracker, I would be happy to feature it.
A breach is unlikely, but it is possible. IS Jobs or the services it depends on—including Supabase for the database, Vercel for hosting, GitHub for source code and development infrastructure, and open-source packages—could be compromised. Supply-chain attacks and rapidly evolving threats, including AI-enabled attacks, add further uncertainty.
I do my best to secure the application, but neither I nor any vendor can guarantee that data will remain 100% secure. Please avoid storing information you would consider unacceptable to have exposed.