The Analyst gives you simulated workplace practice—not employment history. Use this guide to make your judgment visible: the decision you faced, the methods you chose, the artifact you produced, the limitation you recognized, and what you would do next.
01 / PROOF, NOT LABELS
Do not say “strong analyst.” Show the decision trail.
A competency claim becomes credible when another person can inspect what you did. Keep the chain intact from the request through the boundary you recognized. Your portfolio shows the evidence; your résumé summarizes it; your interview explains the judgment behind it.
01Situation
Name the fictional workplace context, audience, and operating constraint.
02Decision
State the choice your analysis needed to support—not merely the topic you explored.
03Analytical action
Show what you defined, reconciled, tested, modeled, or deliberately declined to claim.
04Artifact
Point to the query, figure, diagnostic, brief, or reproducibility record a reviewer can inspect.
05Boundary
Explain the material limitation and the evidence that could change your recommendation.
02 / NACE COMPETENCY EVIDENCE MAP
Use the framework without overstating the evidence.
The labels below describe where The Analyst can support practice—not verified proficiency. NACE does not require every experience to address every competency.
01DIRECT PRACTICE
Critical Thinking
Define grain and cutoffs, test rival explanations, reconcile conflicts, and make proportionate recommendations.
Group slicing alone does not establish equitable practice or cultural competence.
Competency names reference the NACE Career Readiness framework. NACE currently marks Equity + Inclusion as under review; institutions should consult the current NACE notice and follow their own policies. The framework and competency names are referenced courtesy of the National Association of Colleges and Employers.
03 / BUILD AN EVIDENCE RECORD
Capture what happened before polishing what it means.
Complete this after a serious attempt. Choose no more than two competency claims and connect each to something a reviewer can actually inspect.
Assignment and simulated roleWhat workplace decision was on the desk?
Operating constraintWhat cutoff, capacity, privacy, or policy rule shaped the work?
Analytical choiceWhat did you define, reconcile, compare, model, or decline to claim—and why?
Evidence producedName one query, figure, diagnostic, or decision artifact another person can inspect.
Supported resultReport the finding or recommendation, never an invented real-world impact.
Material limitation and revisionWhat could the evidence not establish, and what changed after review?
SUGGESTED CONTEXT LINE
Independent Data Analytics Simulations | The Analyst
Completed workplace-style analyses in a fictional enterprise data estate, producing reproducible SQL/Python evidence and decision-focused handoffs.
PLACEMENT
List this as a project, coursework, or independent simulation—not employment at Meridian. Link a public portfolio only when you choose to publish one.
04 / PORTFOLIO REVIEW
Make the decision legible before making the code impressive.
The Portfolio Builder creates a selective, GitHub-ready package locally. Use this review before publication; GitHub is optional, and The Analyst does not host, score, or verify the result.
READY TO DISCUSS?
The business decision is clear before the technical detail begins.
The population, grain, cutoff, exclusions, and important definitions are explicit.
Selected SQL or Python can be connected to the visible result.
At least one reconciliation, validation, or credible rival explanation is present.
The recommendation follows from the evidence and names a material limitation.
The repository is selective, readable, and free of private notes or unsupported claims.
05 / INTERVIEW TRANSLATION
Tell the judgment story—not a tour of the notebook.
STAR—Situation, Task, Action, Result—is a useful structure. For simulated analytical work, add one more sentence: the limitation.
60-SECOND STRUCTURE
S
Situation — identify the simulation, role, and operating context.
T
Task — name the decision and constraint.
A
Action — explain the few analytical choices that mattered.
R
Result — state the supported recommendation or responsible refusal.
L
Limitation — identify what the evidence could not settle.
QUESTIONS YOUR PORTFOLIO SHOULD HELP ANSWER
What initially looked straightforward but was not?
Which grain, timing, denominator, or measurement choice materially changed the work?
What alternative explanation did you test?
Why was your chosen method proportionate to the decision?
What did you recommend, qualify, hold, or refuse?
What evidence would change your recommendation?
For conflict, supervision, or teamwork questions, use a real class, job, volunteer, or group experience unless this work was genuinely completed with others. See Handshake’s STAR interview guide for the standard framework.
06 / CAREER CENTERS + FACILITATORS
A public resource that can fit an existing program.
No account, roster integration, résumé upload, or institutional data transfer is required. Staff can link the permanent page through their normal resource library, course, event, or experiential-learning workflow.
RECOMMENDED / 90 MINUTES
From Workbench to Interview
Participants arrive with one completed assignment or Priority Brief. The session converts existing work into a reviewed portfolio claim and interview story; a GitHub account remains optional.
Set the boundary
Identify the simulation, audience, and one decision worth discussing.
Select the proof
Choose two evidence moves, one artifact, and one material limitation.
Rewrite the takeaway
Make the decision legible to someone who did not complete the assignment.
Review the package
Inspect selected code, figures, disclosures, attribution, and publication scope.
Build the portfolio
Generate the local portfolio ZIP; publishing to GitHub remains optional.
Challenge and rehearse
Peer-review the claim, revise once, and practice a 60-second explanation.
ALTERNATIVE / 90 MINUTES
Analytical Judgment Sampler
Use one focused Priority Brief with learners who already have baseline SQL or Python fluency. The outcome is exposure, evidence discussion, and reflection—not a promised finished portfolio.
10 MIN
Frame the role, decision, and source boundary.
55 MIN
Investigate individually or in deliberately assigned teams.
15 MIN
Challenge competing recommendations and missing evidence.
10 MIN
Write the handoff and identify the next practice gap.
Students in data science, analytics, computing, economics, business, and adjacent quantitative programs
FORMAT
Self-guided browser resource; no account required
TIME
Priority Briefs generally require 60–120 minutes; full assignments require multiple sessions
TECHNOLOGY
Current laptop or desktop browser; assignment work is not designed for mobile use
URL
https://theanalyst.dev/career/
Practice SQL, Python, analytical judgment, executive communication, and portfolio development through fictional workplace simulations. Learners investigate a connected synthetic enterprise data estate, make a defensible decision, and can export selected work as a GitHub-ready portfolio. No installation or account is required; analytical work remains on the learner’s device.
07 / HONEST BOUNDARIES
Practice evidence is not professional experience.
Use the work to make a narrower, stronger claim: “Here is how I approached a difficult analytical decision, here is the evidence, and here is the boundary I recognized.”
Meridian Living Systems and its data are fictional and synthetic.
Assignments are not employment, internships, client work, or production deployment.
An export does not certify correctness, mastery, or a NACE competency.
Solo work cannot, by itself, establish teamwork or people leadership.
Synthetic consequences cannot support claims about real revenue, customers, or organizational impact.
Never paste employer, client, student, patient, or other protected data into the workbench.
BUILD THE NEXT PROOF
One reviewed project is worth more than five unexplained repositories.