Dear Advertiser,
I work as a Software Engineer for a leading company in Computer Graphics Industry.
My hobbies include social networking, internet surfing, writing reviews for products, books and services, writing
reviews of articles published in online journals and newspapers, writing blogs, criticisms and articles on social
blogging sites.
I apply for this opportunity solely due to my inclination to benefit others through my writing skills. This also
gives me a chance to make some extra pocket money and to prove to me that I can write good articles pertaining to a different domain.
I am sure I shall be able to perform well. Considering that re-writing 5 articles per day for 30 days should yield an amount of $200, I have placed an initial bid, which I am sure will change if we continue to collaborate.
To demonstrate my writing skills, I have pasted an essay that I wrote recently for a college.
Looking forward to hearing from you soon.
Sincerely,
Pooja
--------------------------------------------
Essay: ----
Topic: Please describe a time when you coached, trained, or mentored a person or group. (500 words or less, limited to one page)
I had the opportunity to mentor and coach my co-workers and seniors informally on engineering courses relevant to our work. This guidance was primarily required to get through some design problems and arguments that were on for a while on a time-critical project.
Part of engineering profession entails with mentoring people in order to let them get to speed. However, there’s one particular incident that draws my attention every now and then. I was a beginner compared to my fellow workers and closer to academia in my approach to solving problems. Each of my project partners held at least five years of engineering experience and were more accustomed to handy ways of getting things done as is the case with any industry. We were stuck with a project involving an evolving design and we didn’t know which way to go. In a split second, going back to basics was all I could think of. In general, on a time-critical project, reviewing fundamentals is not considered a really good idea and is considered highly risky. Since I was the junior most in the herd, I had no authority to educate the team either.
Finally, discussions and heated arguments lasting a couple of hours were enough for me to convince everybody that as long as the risk involved in the process of coaching was a calculated one, it should effectively pose no threat to the completion of the project and also that the solutions arrived after such a course would definitely be helpful in achieving the objectives of the overall project.
Eventually, I decided on some disciplines and certain topics in each of those disciplines that would help the audience to quickly arrive at solutions to the current design problems. I proceeded with a presentation to put forth ideas and concepts in a crisp manner and explained to them not only the concepts, their implications but also described in detail, the possible uses of the concepts in the context of the project at hand. Concepts from data structures, algorithms, design patterns, design of embedded systems and design of other pieces of firmware interacting with the project deliverables were primarily covered in the presentation. Quite aware that people on my team were not really very confident of coming up with questions over a short period of time, I ensured that all the sessions covered all the audience needed to know.
As was expected, the presentations turned out to be of much use to refreshing everybody’s memory of basic courses. The solutions arrived thereafter were relatively more efficient with respect to both, power and performance. I am glad to admit that those solutions have already been shipped as a part of some products now.
This experience also made me realize if we give a head start to a project without much thought, sometimes we fail to look at very simple aspects of the problems to be solved. Coaching my fellows also helped me to refresh my subjects at school and college.
