Job search
GM Human Interface Design Internship Portfolio Submission: PDF, Website Link, and Sharing Rights
Current GM requisition JR-202619285 plus public FAQ and Adobe export guidance support two original fictional packet and provenance decisions, with actual application/upload/terms acceptance unperformed.
For GM's specific 2027 Human Interface Design internship posting, prepare the portfolio PDF attachment and treat the encouraged website link as an additional reading route. Review sharing rights before including work: a polished file or accessible website does not establish permission to share its contents. Keep the requisition's instructions with your packet rather than assuming every GM design opening uses the same process.
This guide reviews public employer instructions inspected October 20, 2026, and uses original fictional packet and permission examples. We did not open a private application, upload material, change sharing permissions, accept terms, or contact GM. For other opportunities, browse recent roles on LandOffer.ai, then follow each employer's own current submission requirements.

Match the instructions to the actual requisition
The official GM careers page identifies requisition JR-202619285, Summer 2027, with Pasadena, California, and Warren, Michigan, in its location header. It displayed an October 16, 2026 posting date when inspected. Its body includes Warren-specific work-arrangement language; do not infer that every location has identical arrangements.
The guidance below concerns that posting's portfolio section. It does not establish eligibility for a particular reader, a deadline extension, or requirements for a different year. Read the full current qualifications and location instructions before spending time customizing a packet. A similar title or a copied listing is not enough to establish that you have the same requisition.
Record the requisition beside the exact portfolio version you intend to use. If the posting changes or disappears, preserve what you prepared but recheck the employer's actual route. Do not describe an old instruction set as a currently open application simply because you still have a downloaded copy.
Distinguish the attachment from the website recommendation
The posting requires a portfolio and separately encourages an online link in the application's website field or on the resume. Its file instructions specify PDF, the LAST NAME, FIRST NAME naming pattern, and an attachment, potentially condensed. It excludes Dropbox files and Google Docs.
The website recommendation does not state that a link alone replaces the PDF attachment instructions. Preparing both gives you a PDF suited to the specified file route and a website for work that benefits from its intended presentation. If the actual form creates a conflict, resolve that against the current employer instructions rather than guessing that one route silently replaces the other.
We did not inspect authenticated attachment controls, so this article supplies no universal upload cap, accepted-file count, or required page limit. Use the constraints shown in the actual application. It is easy to focus on getting the file accepted. Check the small annotations and the website’s intended reader access too; neither is established by a tidy filename.
For the PDF, retain a local editable source and an exported copy. Review page order, legibility, and links after the final export. For the website, identify the intended landing page and the work it contains. A resume link, application-field value, and PDF reference should lead readers toward compatible work rather than three unrelated versions.
Select work that explains your contribution
Editorial preparation method: Choose examples that let a reader follow a design decision. A project can explain the problem, the relevant constraint, an alternative you considered, the reason for your choice, and the limits of what you evaluated. This is a suggested presentation method, not GM's undisclosed scoring rubric.
For interface work, a sequence can be more informative than a wall of final screens. Show the task and how the interaction changes across meaningful states. Label an exploratory concept as a concept. Do not present a class exercise as a shipped automotive feature or claim user validation when you only made a prototype.
Separate your own work from a team's. Explain whether you contributed research synthesis, interaction flows, visual design, prototyping, or a handoff. If teammates created an artifact, credit them and establish the permission to include it. Being on the project does not automatically make every deliverable yours to distribute.
Avoid making the website carry every explanation omitted from the PDF. The attachment should explain the selected work on its own, so a reviewer can follow your contribution without opening another destination. Motion, a longer walkthrough, or additional process material can remain on the website if you can share it and the destination is accessible.
Completed artifact selection and delivery review
Iris Chen is a fictional design student. Her proposed packet contains an original parked-vehicle charging-summary concept and a team campus-service scheduling project. Neither is a real GM project, and no PDF or application was submitted for this article. The observations below are stipulated for this worked example, not measured file or website tests.
Iris first reduces her proposed collection to these two projects. She excludes an unrelated employer dashboard while its permissions remain unresolved. She then completes a six-page content plan; six pages is her editorial choice, not an employer limit:
| Page | Completed content decision | Evidence the page should carry |
|---|---|---|
| 1 | Introduce Iris and the selected projects | Identify original concept versus team work |
| 2 | Define the charging-summary problem | Explain the parked-use context and design constraints |
| 3 | Compare two interaction flows | Show the rejected alternative and the reason for the final choice |
| 4 | Present the concept and its limits | Distinguish prototype behavior from untested real-world use |
| 5 | Summarize the campus scheduling contribution | Identify Iris's flow design and credit teammates' work |
| 6 | Provide credits and the intended website route | Keep ownership notes and further reading consistent |
For the first project, her completed synopsis is:
Original class concept for explaining a charging session while the vehicle is parked. I designed the information hierarchy and comparison of session-summary states. I rejected an initial screen that mixed historical totals with the current session because the two timeframes were unclear. The revised concept separates those views. I did not test it in a vehicle or validate it for driving use.
The synopsis gives a design decision and a limitation without inventing production impact. The synopsis explains Iris’s decision without requiring a working prototype; it does not establish that the design succeeds in a real vehicle.
Iris completes this delivery review under the fictional premise:
| Item reviewed | Stipulated finding | Completed decision |
|---|---|---|
| PDF filename | Draft name still says Portfolio-final-new | Rename the prepared attachment to Chen, Iris.pdf |
| PDF page sequence | The six selected pages appear in the planned order | Retain the sequence; remove unused export pages |
| Legibility | Key annotations remain readable in the example's final copy | Keep that copy as the selected candidate, not proof of form acceptance |
| Website route | Planned portfolio page contains the same projects | Use that destination rather than a cloud-document link |
| Resume reference | Points to an older portfolio collection | Revise the prepared resume reference to the selected collection |
| Upload and submission | Neither performed | Keep delivery status pending |
Her completed packet decision selects Chen, Iris.pdf, the two-project website collection, and a resume reference to that same collection. The website is not treated as a substitute for the attachment. Actual file-size acceptance, saved application fields, and submission confirmation remain unverified.
Reduce file size without discarding the explanation
If a PDF exceeds the form's stated limit, work from a copy and inspect the result. Adobe's current size-reduction guidance, updated October 16, 2026, describes saving a reduced-size copy with compatibility settings. That is a tool option, not a GM-required product or a reason to buy a subscription.
Reduce unnecessary image weight or export excess before shrinking every page indiscriminately. Reopen the selected export and read the small labels, diagram legends, and captions. Keep the design reasoning that makes the example useful; a file that uploads but hides your contribution is a poor trade.
Do not upload confidential work to an unrelated online compressor merely because the application needs a smaller attachment. Resolve whether material can be shared before choosing any external processing route. We did not compress a candidate's file or transmit a portfolio to Adobe or another service.
If you remove pages to fit, recheck the references. A page may point to an explanation that is no longer included. The final filename should identify the actual reviewed copy, while your working folder can retain the source and earlier exports for your own use.
Read the sharing conditions before choosing restricted work
The posting's disclaimer excludes NDA or confidentiality-covered work and requires express written owner consent for third-party-owned material. It also describes hiring-related reuse rights and a release of claims upon sharing. Read that full language before proceeding; this article does not determine the legal effect for your materials or accept the conditions for you.
Separate authorship, ownership, confidentiality, and permission. You may have drawn an interface as an employee without owning the right to distribute it. A manager's informal praise is not the same thing as a documented permission covering the specific work and intended disclosure.
A password does not establish permission to share the underlying work. Nor does changing a logo, blurring a customer name, or redrawing the same restricted design from memory. Those steps can change presentation without establishing that sharing is allowed. When the needed permission is unresolved, choose an independently shareable example instead of treating a disclaimer in your portfolio as authorization.
Keep a record precise enough to explain the decision: the artifact, its source, the ownership situation, any confidentiality restriction, the permission scope, and whether the work is included. This is a preparation record; it does not replace the actual agreement or an owner's written consent.
Completed provenance review: what Iris excludes
This second original fictional asset resolves the materials decision before delivery. The permissions below are stipulated facts for teaching, not real approvals or interpretations of an existing contract.
| Candidate artifact | Fictional provenance and restriction | Completed decision |
|---|---|---|
| Original charging-summary concept | Independently authored for class; premise establishes no third-party ownership or confidentiality restriction | Include with class-concept and untested-use labels |
| Team campus scheduling flow | Premise establishes ownership review, no confidentiality restriction, and written consent covering the selected team's work for sharing with GM | Include only the approved version, with contributor credits |
| Employer dashboard screenshots | Employer-owned; no written sharing consent established | Exclude from both PDF and website |
| Unreleased client concept | Covered by an NDA in the premise | Exclude; do not rely on a password or visual redaction |
Iris's final review note reads:
Selected packet: independent class concept and the specifically approved team contribution. Employer dashboard and NDA client concept excluded. Credits identify my contribution. No permission is inferred from my having worked on an artifact. Final sharing conditions still need to be reviewed by the applicant before submission.
The note completes a concrete include/exclude decision. It does not certify that every student owns all class work, that every teammate can grant the necessary rights, or that a similarly worded email clears another person's portfolio. The relevant owner and actual agreements must support the real decision.
Her website draft uses the same approved collection. She does not keep the excluded dashboard online and assume that leaving it out of the PDF solves the disclosure problem. Both destinations are part of the material a reviewer may encounter through her packet.

Keep preparation, upload, and submission as separate states
GM's application FAQ says a confirmation email follows a completed submission. It also says a draft can be resumed before the posting expires, while changes are unavailable after submission or expiration. Review your selected materials before that boundary rather than assuming you can replace them later.
In your own record, separate “packet reviewed,” “attachment present,” “website field checked,” and “application submitted.” A local file or an open application page establishes none of the later states by itself. Preserve the requisition and the actual confirmation if you submit through the employer's process.
For this article, every application state remains unperformed. Use the worked decisions to prepare an accurate, shareable packet, then browse recent LandOffer roles if you need other opportunities. Carry the evidence and permission discipline forward, while reading each new role's delivery instructions independently.
Sources and Further Reading
- GM internship JR-202619285, exact current role and portfolio instructions; full public native body verified despite direct-fetch restriction.
- GM application FAQ, public submission-confirmation and draft-editing answers expanded and read.
- Adobe: Reduce PDF file size, a documented local export option, not an employer requirement or a tested candidate-file workflow.


