The paper audits the top 10 STEM master's programs in the U.S. — the ones most OPT students attend. It asks whether those programs teach what H-1B-sponsoring employers actually require. You are both the subject of this research and a potential author of it.
| By the end of this, you will be able to… | Bloom's Level |
|---|---|
| Summarize the paper's argument and its stakes for OPT students specifically | Understand |
| Classify the paper's open TODOs by type and match them to your existing skills | Analyze |
| Apply CRITIQ's /brainstorm to generate at least one substantive contribution idea | Apply |
| Evaluate your co-authorship fit against the CRediT taxonomy | Evaluate |
| Decide whether to pursue co-authorship — and if yes, name the specific TODO you will own | Create / Decide |
Tier 1 — pattern execution, algorithm implementation, framework application. Observable in syllabi through verbs: implement, build, apply, use, write, construct.
Tier 3–5 — system design judgment, AI auditing, stakeholder navigation, causal reasoning. Appears primarily in electives, if at all.
Documents that mismatch with enough methodological rigor to publish — and recruits co-authors to close the open TODOs.
Pattern execution, algorithm implementation, framework application. Observable in syllabi: implement, build, apply, use, write, construct. This is where most required coursework lives.
Communication, stakeholder navigation, ethical judgment, cross-functional collaboration. Observable through: communicate, negotiate, advise, present, advocate.
Problem formulation, AI output auditing, system design under uncertainty, interpretive judgment. Observable through: evaluate, audit, formulate, critique, distinguish. Employers require this. Curricula rarely do.
Causal and counterfactual reasoning — root cause analysis, interventional thinking. The paper codes every required course at every audited institution against this framework.
Think about your own required coursework. Which of your core courses would you code as Tier 1? Which — if any — would you code as Tier 3 or 4? What verbs appeared in the course descriptions?
| CRediT Role | What it maps to in this paper |
|---|---|
| Formal Analysis | Coding the Bloom's-to-tier rubric; running chi-square, Cohen's Kappa, Cramér's V on the full dataset |
| Data Curation | Pulling and archiving degree requirements, course catalogs, and learning outcomes at all ten institutions with timestamps |
| Investigation | Verifying primary sources — CS2023 guidelines, SEVIS data, Anderson & Krathwohl, prior Bloom's audit studies |
| Methodology | Designing or refining the Bloom's-to-tier coding rubric, anchor examples, and adjudication notes |
| Writing – Original Draft | Methods, Results, Discussion — written in sequence after data is locked and coded |
| Writing – Review & Editing | Reviewing and tightening any section; running CRITIQ on drafted content before submission |
One role, done rigorously, is a legitimate co-authorship claim. The orange rows are the current bottlenecks — the paper cannot move forward without them.
CRITIQ is a peer review and paper development tool. It reviews manuscripts and builds them from raw ideas using the same standard it would apply as a reviewer. It will teach you as it works.
The full outline — including TODO annotations, research questions, methodology section, and the working hypothesis. All of it. CRITIQ needs the complete context to find the real gaps.
CRITIQ will ask: what did you notice? What's your gut explanation? What would prove you wrong? It will move you from observation to testable research question in six questions.
Look for: one gap, one methodology question, one thing the outline doesn't address that should be. If you can't find anything after running /brainstorm — that's data too. This paper may not be the right fit.
| CRITIQ Output Section | What it gives you |
|---|---|
| Your Research Question | One clean, specific, answerable question — not a topic. This becomes your entry point for a co-authorship conversation. |
| Your Working Hypothesis | One sentence: what you think is true and why. Sharpened by CRITIQ — but the observation is yours. |
| The Gap You're Filling | What's known, what's not, and where your question sits between the existing literature and the paper's open TODOs. |
| Study Design (Rough) | The simplest viable approach to test your hypothesis — constrained to what's actually feasible given the paper's scope. |
| What to Read Next | Three search terms or topic areas that extend understanding of the gap — not fabricated citations. |
| Concepts to Learn | Terms from the brainstorm to understand before drafting. Each is a /learn shortcut in CRITIQ. |
This output is yours — not the paper's. A working hypothesis may be wrong, under-specified, or already addressed in the outline. That's fine. It's the beginning of a conversation, not the end of one.
After running /brainstorm: what was the one observation or gap you found? Can you name the CRediT role it maps to? Are you willing to own that contribution through to completion — not just through the interesting parts?
The paper documents a structural mismatch between what STEM master's programs teach and what H-1B-sponsoring employers require. You are both its subject and its potential author. The /brainstorm command is the entry point. The second coder slot is open. The TODO list is documented.
What's missing is a decision.
Irreducibly Human // Nik Bear Brown // Research Methods // 2025