Post History
You're focusing on the wrong angle. Think about it this way: why would a potential employer care that you wrote a report? What skill set does it show you have? What does it prove you could do again...
Answer
#4: Attribution notice removed
by
System
·
2019-12-13T12:00:01Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/4420 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T02:03:28Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/4420 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
You're focusing on the wrong angle. Think about it this way: why would a potential employer care that you wrote a report? What skill set does it show you have? What does it prove you could do again?
So think about the report:
- Why did you write the report? For whom? Boss, peers, IT, management, accounting? What are they going to do with the report when it's done?
- Was it just stating the facts of what NFS can do, or were you analyzing pros and cons of installation, or comparing it to some other system?
- What were the sources of the report? Did you pull information from many different sources and create a new reference document for your department, or did you just copy what you learned in the course?
Once you figure that out, it will be much easier to write it as a résumé bullet. ("Analyzed NFS system so that IT Department could justify purchase requisition for next year's budget," for example.)
#1: Imported from external source
by
System
·
2011-11-10T16:50:23Z (over 12 years ago)
Original score: 8