JPMorgan Code for Good Resume —
What the Screening Actually Rewards
Students using JPMorgan's nonprofit hackathon as a route into its technology roles.
Code for Good is JPMorgan's selection-hackathon: students build solutions for nonprofit organisations over an intensive event, observed by JPMorgan engineers — and performance there has historically fed directly into internship and full-time offers. The mechanic is observed collaboration: you are being evaluated while building in a team, live.
The resume matters twice: once to be SELECTED for the event (a real screening round from large applicant pools), and again as the record interviews anchor on afterward. The selection screen favours demonstrated building plus service/impact signals that fit the event's nonprofit frame.
Eligibility — the shape, not this cycle's numbers
- Students within the year-of-study windows JPMorgan defines per event, via official application.
- Selection is competitive from the applicant pool — the application materials are a genuine screen.
Event timing, eligibility windows and what performance leads to are defined per cycle — verify on JPMorgan's official careers/events pages.
How JPMorgan Code for Good actually selects
- 1Application + screening
Resume-and-form screening (with coding assessments in various cycles) selects the event cohort.
Resume angle: This is one of the few drives where the resume itself is a scored gate before any event.
- 2The hackathon
Team builds for nonprofit briefs, mentored and observed by JPMorgan engineers.
Resume angle: None during — but everything you claimed is now visible in how you actually work.
- 3Offers / interviews
Strong performers have historically progressed toward internship and role offers.
Resume rules specific to JPMorgan Code for Good
- Build evidence first: hackathons attended, things shipped, repositories — the screen selects people who visibly build.
- Include service/impact signals honestly (volunteering, community tech work) — aligned with the event's nonprofit frame without manufacturing it.
- Teamwork texture in bullets ('paired with', 'integrated with teammates' API') — observed collaboration is the event's whole point.
- Web-stack readiness evidenced somewhere; CFG builds skew toward rapid web prototypes.
- Keep it one page and screen-readable — the cohort is selected from large pools at speed.
What gets filtered in this drive
- A solo-genius resume for a collaboration-observed event.
- Manufactured 'social impact' lines that interviews puncture in one question.
- No shipping evidence — the screen is looking specifically for people who finish builds.
Free ATS check against the four screens that filter fresher resumes — no signup to scan.
Score my resume free