UC PIQ Examples for CS and Engineering Majors

UC PIQ Examples for CS and Engineering Majors

You answer 4 of UC's 8 personal insight questions, 350 words each, and the same four go to every campus. For a CS or engineering applicant, Question 6 (academic subject) is the natural home for the subject, and one of Questions 1, 2, 3 or 4 carries a project, a skill or a team. UC publishes no sample answers, so every example below is constructed by us and labelled.

The stakes are real: UCLA admitted 3.9% of 6,083 Mechanical Engineering applicants and 7.3% of 6,806 Computer Science applicants for fall 2025 (UCLA profile by major). Our view: at those rates, telling the reader you love building things adds little. It is a claim, not evidence. What a reader cannot get from your activities list is one technical decision you made, explained so a non-specialist can follow why it was hard. Each example below is built around that sentence.

UC's prompts and writing tips were checked on October 30, 2026 on UC's personal insight questions page, for the fall 2027 application due November 30, 2026. If you have not picked your four yet, start with how to choose your 4 UC PIQ prompts.

On this page: which questions to use · example 1, Question 6 · example 2, Question 3 · example 3, robotics two ways · jargon test · campus notes · checklist

Which four questions carry engineering evidence

UC says: "All questions are equal. All are given equal consideration in the application review process, which means there is no advantage or disadvantage to choosing certain questions over others." So there is no "engineering question." There is only the question that fits each piece of evidence you have.

Our recommendation: use at most one answer per activity. Four answers about one robotics team tell the reader one thing four times. The constructed robotics example below shows the same experience framed two ways, and why your set should hold only one of them.

The countercase: if your strongest story is not technical, such as caring for a sibling or working after school, write it. UC's own advice is to choose questions "that are most relevant to your experience and that best reflect your individual circumstances." One clear technical answer plus three strong non-technical ones can make a better set than four thin technical ones. Do UC PIQs need to be about your major? covers that choice.

Constructed example 1: Question 6 about a coding project

The prompt: "Think about an academic subject that inspires you. Describe how you have furthered this interest inside and/or outside of the classroom."

Constructed example, written by us, not a real applicant statement. First, the weak version (57 words):

Ever since I was young, I have loved computers. I know Python, Java and C++, and I have built many projects, including a tutoring scheduler, a website for my robotics team and a Discord bot. Through these experiences, I learned problem-solving and perseverance, and I want to major in computer science at UC to continue my passion.

It names three languages and three projects and explains none of them. UC's tip covers it: "Making a list of accomplishments, activities, awards or work will lessen the impact of your words."

Constructed example, written by us, not a real applicant statement. The revised version (327 words):

In tenth grade, our school's peer tutoring sign-up was a paper sheet taped to the library door. Tutors wrote down their free periods, students wrote down what they needed, and Ms. Okafor, the librarian, spent Friday afternoons matching them by hand. I asked if I could try writing a program to do it.

The first version took me two weekends in Python. It read the sign-ups from a spreadsheet and paired each student with the first free tutor. It worked until the second week, when three calculus students were matched with a tutor who only knew chemistry, because he happened to be free first.

That bug led to the decision that taught me the most. I could keep adding rules to my first-come approach, or I could change the question the program was answering. Instead of "who is free first?", I made it ask "which set of pairings leaves the fewest students without a tutor?" Checking every possible set was too slow once we had forty students, so I read about matching problems and learned that a known method finds the best set without checking every option. I did not invent it. I had to understand it well enough to explain to Ms. Okafor why a student might now get their second-choice period instead of their first.

In its first week, the new version matched 38 of 41 students. The three it could not match told me something too: no tutors were free in sixth period, so the library recruited two more.

I took AP Computer Science A the next year and finally learned the names for things I had already run into, like why my first version broke. I want to study computer science because that project changed what I think programming is. I used to think it was writing instructions. Now I think it is deciding what question the instructions should answer, and then checking whether the answer is fair to the people it affects.

What the revision does:

• One project, not three. The scheduler gets all 327 words. The website and the bot are on the activities list, where they belong.
• A decision sentence. "I could keep adding rules … or I could change the question the program was answering" is the line a reader remembers. It shows judgement, not just effort.
• Jargon translated. It says "which set of pairings leaves the fewest students without a tutor" instead of naming the algorithm. A reader outside computing can follow it.
• Honesty about what you did not do. "I did not invent it" makes the rest believable.
• The subject, not the career. The last paragraph answers the prompt's "academic subject that inspires you" with a claim about what programming is.

Constructed example 2: Question 3 with no internship

You do not need an internship, a lab or a summer program. School-level evidence works if you show how the skill grew. The prompt: "What would you say is your greatest talent or skill? How have you developed and demonstrated that talent over time?"

Constructed example, written by us, not a real applicant statement. (290 words)

My greatest skill is measuring before I fix. I learned it the slow way.

When I was thirteen, the focus knob on our school's oldest microscope snapped off, and the science department had no money to replace it. Mr. Delgado let me try. My first attempt was a knob I designed in a free online CAD program by guessing the size from a photo. It printed well on the library's 3D printer and did not fit.

The second attempt failed too, by less. That was when I bought a cheap digital caliper with birthday money and learned to read it to a tenth of a millimeter. I measured the broken stub six times, wrote the numbers down, and designed to the average. The third knob fit, but it slipped, because a part printed in layers is weaker in one direction. I turned the design ninety degrees on the print bed so the layers ran around the shaft instead of across it. That knob has been on the microscope for two years.

Since then I have fixed a cracked pencil-sharpener gear, a lab drawer runner and the hinge on my grandmother's glasses case. None of these are impressive objects. What I have developed is a habit: measure first, change one thing at a time, and write down what I changed so I know what worked. When our physics class built bridges from craft sticks, I was the one who tested each joint before we glued the next.

I want to study mechanical engineering because I want to learn the theory behind the guesses I have been making with a caliper and a printer. I already know how to be wrong carefully. I want to learn how to be wrong less often.

Why it works for Question 3: the prompt asks how you "developed and demonstrated that talent over time," and the answer is a sequence of three attempts, a tool, a technical fix (rotating the part so the layers run the strong way) and a habit. No award appears. UC's guidance for this question says "You don't necessarily have to be recognized or have received awards for your talent."

Constructed example 3: robotics as leadership vs talent

Same club, same season, two different answers. Two constructed examples, written by us, not real applicant statements. These are opening paragraphs, not full responses.

Question 1 version (leadership; 104 words):

Three weeks before our first competition, our robotics team's builders and programmers stopped talking to each other. The builders kept changing the arm, and every change broke the code. As build captain, I called a meeting and asked each side to list what they needed from the other. The programmers needed the arm's motor positions fixed. The builders needed a week to test. We agreed on a rule: no design changes in the last ten days before an event. I wrote it on the whiteboard and enforced it, including on myself when I wanted to swap a gear. We finished fourth, with working code.

Question 3 version (talent; 96 words):

My skill is finding the one wire that is wrong. On our robotics team I am the person who gets handed the robot when it stops moving. Freshman year, I fixed problems by replacing parts until something worked. Sophomore year, I started drawing the wiring diagram before touching anything, and I began to check power, then signal, then software, in that order. Last season our drivetrain cut out mid-match. Using that order, I traced it in ten minutes to a connector that loosened when the robot turned left. I now teach that checklist to new members.

Why your set should hold only one: both answers come from one activity, so together they use half your set on it. Pick by asking what your other three answers lack. If none of them shows you working with people, use the Question 1 version. If your Question 6 is already about teamwork, use the Question 3 version. The UC PIQ leadership without a title guide shows how Question 1 works when you were not the captain.

Jargon test and the list trap

UC's writing tips set two rules that matter more for technical applicants than anyone else:

Applying to engineering outside the UC system as well? The why engineering essay covers the Common App supplements that ask for a build and your role.

• "Making a list of accomplishments, activities, awards or work will lessen the impact of your words. Expand on a topic by using specific, concrete examples to support the points you want to make."
• "Use "I" and "my" statements in your responses."

Run this test on every technical sentence: could a smart reader who does not code follow it? If not, translate it. Constructed before-and-after lines, written by us:

The "we" in team stories is a trap too. UC asks for "I" statements, so say what you did inside the "we."

Campus notes that change the essays

The four answers are the same for every campus. Two places on the UC system ask CS or engineering applicants for extra writing:

• Berkeley M.E.T. (engineering plus business). The prompt, 350 words maximum: "Share with us the world you come from (for example, your family, school, community, city, or town). What unique experiences from your world motivated you to apply to this business and engineering dual degree program?" Due "by 11:59 p.m. PT on December 14, 2026." The Berkeley Haas undergraduate application guide covers it.
• UC Santa Barbara College of Creative Studies, Computer Science. The CCS apply page asks you to "Write a letter to the attention of the CCS Computer Science faculty, stating your academic interests, your reasons for wanting to study at CCS, and your background in Computer Science. This letter is separate from the essay required in the UC application."

Everything else about CS admission by campus is in UC computer science admission at Berkeley, UCLA and UCSD.

A checklist before you paste

1. Each answer is 350 words or fewer.
2. No two answers are about the same activity.
3. At least one answer contains a decision sentence: what you chose, what you gave up, why.
4. Every technical sentence passes the jargon test.
5. Each "we" has an "I" inside it.
6. Each answer answers its own prompt. Question 6 is about a subject; Question 3 is about a skill over time; Question 1 is about other people.

Questions about CS and engineering PIQs

Should all four of my PIQs be about computer science?

No. UC gives all questions "equal consideration." One or two clear technical answers plus answers that show the rest of you can give a reader more to work with. That is our recommendation, not a UC rule.

Can I write a PIQ about a coding project if I had no internship?

Yes. UC's guidance for Question 3 says you do not need awards, and Question 6 asks how you furthered your interest "inside and/or outside of the classroom." A school project or something you taught yourself is enough if you explain the decision you made.

Can I reuse these examples?

They are constructed to show method, not to be copied. UC's PIQ page says: "Your answers should reflect your own ideas and be written by you alone, but others — family, teachers and friends can offer valuable suggestions. Ask advice of whomever you like, but do not plagiarize from sources in print or online and do not use anyone's words, published or unpublished, but your own." For PIQ 6 outside a technical major, see the general UC PIQ 6 guide.

Get a free review of your UC PIQ

Get a free Quick Review of your UC PIQ against GradPilot's UC PIQ academic passion rubric for Question 6. It reads whether you name the subject and the question that holds you, show how you followed it, and say what you came to understand. For a project or skill answer, use the UC PIQ creative side and talent rubric; for a team answer, the UC PIQ leadership rubric. All three start from the UC PIQ review page.

More UC PIQ guides:

• The UC PIQ prompts for 2026-2027 has the exact wording of all eight questions.
• UC PIQ examples covers each question across majors.
• The college essay hub lists every UC and Common App guide.

Sources

Retrieved October 30, 2026, except where noted.

• University of California, Personal insight questions (current first-year questions): the eight prompts, "4 of the 8", 350 words, equal consideration, writing tips, the help rule.
• UCLA, First-Year Profile by Major, Fall 2025: Mechanical Engineering and Computer Science applicants and admit rates.
• Berkeley M.E.T., Supplemental Application (fall 2027 cycle): first-year prompt, 350 words, December 14, 2026 deadline.
• UC Santa Barbara College of Creative Studies, Apply (fall 2027): CCS Computer Science letter of intent.
• University of California, Quick Reference Guide to UC Admissions (August 2026): fall 2027 filing period; the application goes to every campus you designate.