Reframe a mechanical/core engineering project for a software resume

I have an engineering project from a core branch (mechanical, civil,
electrical, ECE) that involved some programming, simulation, automation, or
data work. Rewrite it for a software-engineer resume so the software parts
are front and center.

Rules:
- Lead with the software or data component, not the physical outcome.
- Name specific tools (MATLAB, Python, Simulink, Arduino, Fusion 360, etc.)
  only if I mentioned them.
- If the project had a physical hardware component, mention it briefly but
  don't let it dominate.
- Output: 1 project title line + 3 bullets.
- Do not invent tools or outcomes.

Here is the project:
[DESCRIBE what you built, which tools you used, what you programmed or
automated, and the outcome]

Who this is for

This prompt is for core engineering students — mechanical, civil, electrical, electronics, or any non-CS branch — who have projects that involved programming, simulation, automation, or data analysis but are currently written in a way that highlights the physical or hardware outcome rather than the software work.

This is a common problem. A mechanical student who wrote a Python script to analyze vibration data will describe the project as "Vibration Analysis of a Cantilever Beam" and focus entirely on the beam. A robotics project will lead with the physical robot rather than the Arduino or ROS code. An electrical student who used MATLAB to simulate a circuit will describe the circuit, not the simulation.

Software recruiters do not care about the beam, the robot, or the circuit. They care about the code, the tools, the data pipeline, and the automation logic. This prompt flips the emphasis so the software components come first and the hardware context becomes background.

If you are a non-CS student applying to software roles at companies like Zoho, Hasura, Postman, or any tech startup, this prompt helps you make the most of the projects you already have instead of building entirely new ones.

How to use it

Step 1: Describe your project with emphasis on the tech. Write down what the project was, which programming languages or tools you used (MATLAB, Python, Arduino IDE, Simulink, AutoCAD scripting, etc.), what you coded or automated, and the outcome. If you wrote even 50 lines of code, mention it.

Step 2: Copy the prompt and paste it into ChatGPT, Claude, or Gemini. Paste your description where indicated. Be honest about what tools you used. The AI will not invent tools you did not mention.

Step 3: Review the output. The AI will produce a project title and three bullets that lead with software. Read each bullet and make sure the software contribution is accurately represented. If your code contribution was minor, scale the bullets back accordingly.

Example before and after

Before (how a mechanical student describes it): "We designed a robotic arm for our final year project. The arm could pick and place objects. We used Arduino Mega and some sensors. I wrote the code for motor control and sensor input processing in Arduino IDE. The arm achieved 90% accuracy in pick-and-place tasks."

After using this prompt:

Automated Pick-and-Place Robotic System

• Engineered motor control and sensor input processing algorithms in Arduino IDE for a 4-axis robotic arm, achieving 90% task accuracy.
• Implemented real-time serial communication protocol between Arduino Mega and 3 sensor modules for coordinated movement decisions.
• Developed calibration routines to optimize grip timing and placement precision, reducing error rate from initial 30% to final 10%.

Notice how every bullet leads with software: algorithms, serial communication, calibration routines. The robotic arm is mentioned as context, but the focus is on what was programmed. A software recruiter can now see Arduino, real-time processing, algorithms, and optimization — all from what was originally described as a hardware project.

Common mistakes to avoid

Describing the project as if applying for a mechanical role. If your project title is "Design and Fabrication of XYZ Machine," a software recruiter may not read past the title. Change it to emphasize the software or automation aspect.

Claiming to have used tools you did not actually use. The prompt explicitly prevents the AI from inventing tools. But when reviewing, make sure you do not accidentally accept a bullet that mentions a library you only read about but never coded with.

Overemphasizing the hardware. The AI is instructed to mention hardware briefly. If you find that the output still focuses too much on the physical components, rephrase your input to give more detail about the code and less about the physical build.

Leaving out numbers. If you measured anything — accuracy, speed, data points processed, lines of code — include it in your input. Numbers make bullets concrete and verifiable.

When not to use this prompt

Skip this if your project had zero programming or software component. If you designed a part in SolidWorks but never wrote a line of code, there is nothing for this prompt to work with. Focus on a different project or build a new software side project.

Also skip this if you are applying for core engineering roles, not software roles. In that case, emphasizing the hardware is the right approach and you should write your bullets the traditional way.