EssayLens

RPI  /  Essays  /  Prompt 2

RPI: Extracurricular elaboration

300 words

Please briefly elaborate on one of your extracurricular activities or work experiences.
What it’s really asking

Pick one activity or job and go deeper than your activities list allows. RPI wants to see what you actually did, how you think, and what you took away, not a summary of every club you belong to. A single vivid scene or problem usually beats a broad overview.

Why they ask it

Rensselaer is a maker and doer culture. This essay lets them check whether you genuinely engage with things or just collect memberships. It also reveals character traits (persistence, leadership, curiosity) in a way a list of titles cannot.

Three ways in
Pick depth, not prestige

Choose the activity where you can describe a specific moment, problem, or decision, not the one with the most impressive title.

Lead with what went wrong

Think about something that broke or failed and what you did next. Struggle reveals more than a clean success.

Pick one that pairs with Why RPI

Choose the activity that connects to how you want to spend your time at RPI, so the two essays reinforce each other.

✕  Weak opening

“Throughout high school, being captain of the robotics team taught me valuable lessons about leadership, teamwork, and perseverance that I will carry with me forever.”

✓  Strong opening

“With three days before the regional, our robot's arm kept jamming, and I was the only one who knew the gearbox was the problem and the only one too scared to say so out loud.”

✦ Annotated example · Robotics team electrical lead. Written by EssayLens to teach, not a real applicant’s essay. Tap a highlighted line →
I am the electrical lead on my high school's FIRST Robotics team, which is a polite way of saying I am the person everyone blames when the robot dies on the field. 1Last season, our robot kept browning out during matches. The drive team would push full throttle, voltage would sag, the roboRIO would reboot, and we would sit dead on the field while the crowd groaned. 2Everyone wanted to blame the battery, so we kept swapping in fresh ones, and it kept happening. I was suspicious. I borrowed a clamp meter, logged current draw during a practice match, and found that all six drive motors were spiking at the same instant whenever we slammed the joystick to full. 3The fix was not bigger batteries. I wrote a slew-rate limiter in the drive code so the motors ramped up over a quarter second instead of jumping, and I rebalanced which motors shared each breaker. The brownouts stopped. 4What surprised me was that the answer lived in the gap between two subsystems nobody owned. The programmers assumed it was hardware; the hardware team assumed it was code. 5So I started running a five-minute integration check before every match where the two teams sat together and traced one signal end to end. We did not brown out again all season. I am still proudest not of the limiter I wrote, but of getting two stubborn groups to read each other's wiring before the buzzer.6
  1. 1Opens with self-aware humor and a concrete role. RPI rewards builders, and the very first line establishes a hands-on technical responsibility.
  2. 2Describes a specific, vivid failure with real technical vocabulary (brownout, voltage sag, roboRIO). Specificity over enthusiasm is the school's stated value, and the failure makes the later fix earn its weight.
  3. 3Shows methodical debugging instead of guessing, and resisting the easy explanation. This signals the analytical builder mindset RPI wants, and the borrowed clamp meter is a telling concrete detail.
  4. 4Delivers a real, specific solution (slew-rate limiter, breaker rebalancing) that crosses hardware and software. The resolution proves the applicant can actually build and not just diagnose.
  5. 5Reflects on a systems-level insight, showing maturity beyond the immediate fix. This kind of cross-boundary thinking is what an engineering school like RPI values in a future student.
  6. 6Ends with a leadership move that scales the individual fix into a team process, and a humble final note. It shows the applicant builds systems and culture, closing the elaboration at full length on what they learned about people, not just circuits.
Stuck? Start here
  • Which activity has a single moment I can replay in vivid detail, second by second?
  • Where did I struggle or fail, and what did I actually do about it?
  • What does this activity reveal about how I will act in a lab or team at RPI?
Before you submit
  • Did I focus on one activity and one moment instead of summarizing my resume?
  • Is there a specific scene a reader can picture, with real detail?
  • Does my takeaway sound like me, not a generic lesson about leadership or perseverance?

Drafted it? Get an honest, admissions-style read, free.

Score my essay