resume writing"resume writing" I'm looking for a great online resume writing resource, where should I start?
I am trying to discover the most effective way to write an eye catching resume. What online resouces will assist me?
Referring back to your question:
"I am trying to discover the most effective way to 'write' an eye catching resume. "
This trick is not to write it, but create it. Think about a brochure with a lot of text... what catches you eye, the 500 words written on the page or how it's designed? Your resume should be considered a sales tool (like a brochure) and the product you are selling is you! Even if those 500 hundred words were brilliant, what if the brochure itself was printed on a white piece of paper with an inkjet printer? Would you be interested or intrigued enough to read it?
Statically it's been shown that on average for every 200 resumes submitted for a position, only 1 is granted an interview. I actually think the odds are even less these days. You only have about 10 seconds to convince the person look at your resume to read it.
What you need to do is learn how to make your resume into a presentation piece that will bring you to the top of the pile. While having a well written resume is important, in order to get it read it should look amazing!
So few people do this that if you do you are sure to increase your odds.
To learn more as well as get job searching tips, please visit my website http://www.dooropeningresumes.com
how to write a interview report"how to write a interview report"
Nine Tips for an Effective Bug Reporting
It is important that a software tester reports everything what he feels. A software tester role is that of a catalyst in any team. He makes up the team on one hand and breaks up the application on the other. It is important to clearly understand all the issues in the application may be big or small with due course of understanding in terms of business and the application. Therefore a strong Bug Report serves as a definite proof in Software Development Life Cycle, provided the status of bugs is updated at all stages. Sole objective of your reporting a bug is that your intention is to get the bug fixed.
1. Clarity of Bug Description - Bug description refers to a small statement, which briefly points towards the exact problem. May be the problem requires a couple of steps to reproduce it, however this small statement of bug description must be able to communicate the exactly nature of problem. For instance in case of a problem concerning an error from the server, the bug description could clearly elaborate the meaning by stating that the server error takes place while performing such an such operation.
2. Don't Pass your Verdict - even if you are brimming with confidence about authenticity of the bug detected by you, avoid writing a bug report which would reflect as if you are trying to pass your verdict on the genuinity of the bug. In every probability this could initiate a controversy which would reflect your superiority complex as a tester. Your main aim should be to keep your bug report conclusive supporting your bug plus the sole motive must be to get the bug closed ultimately. Try to use diplomacy in bug report, instead of using authoritative statements in favor of your bug thereby making your bug report unpleasant, best way is to be suggestive. Such an approach shall always be taken in good spirit.
3. Steps to Reproduce - How to reach the precise point of bug, with due explanation of the set of conditions so as to reproduce it must be clearly defined in the bug report. For instance, for graphical software, tester needs to communicate to the developers, as to what he had done before getting the bug. The details must be elaborated like which buttons were pressed and in what order. For a program executed by keying in a command across the prompt, the details of the command typed before getting the bug needs to be indicated precisely.
4. Use of Simple Language - People do not like to read long paragraphs containing complex jargons & tongue twisters. A good bug report contains small bulleted like containing small but clear sentences. It should describe the observations relevant to the concerned bug only. Do not make the bug report unnecessarily complex and lengthy by writing too many facts. Avoid narrating superfluous details, which may not be of any help in reproducing the bug. Do not write things, which are commonly known, to everyone.
5. Quote-Relevant Examples - In majority of situations, we find that for reproducing a particular bug, some particular group of inputs is essential. Thus instead of making vague statements like feed invalid name of a person in the contact list, & save; it can be said that feed an invalid input like 035bbb@$% in the name field & click save. In order to get the bug fixed quickly tester must try to help the programmers by providing all the relevant information / to-the-point information.
6. Provide Back References - In case a particular bug happens to contradict the specification document or any other document related to the project; the bug report must provide adequate reference to the particular chapter or clause number of the concerned document being contradicted.
7. Allocate Bug Priority & Severity - Bug reporting is not complete without earmarking the level of Bug Severity & Bug Priority.
Bug Severity: refers to the quantum of danger as to how badly the bug can harm the system. It describes as to how bad the bug is. Severity is a feature of constant nature associated with the bug.
There are three levels of Bug Severity, which are described as under:
Severity level - Critical: is the most dangerous level, which does not permit continuance of the testing effort beyond a particular point. Critical situation can arise due to popping up of some error message or crashing of the system leading to forced full closure or semi closure of the application. Criticality of the situation can be judged by the fact that any type of workaround is not feasible. A bug can fall into "Critical" category in case of some menu option being absent or needing special security permissions to gain access to the desired function being tested.
Severity level - High: is a level of major defect under which the product fails to behave according to the desired expectations or it can lead to malfunctioning of some other functions thereby causing failure to meet the customer requirements. Bugs under this category can be tackled through some sort of workaround. Examples of bugs of this type can be mistake in formulas for calculations or incorrect format of fields in the database causing failure in updating of records. Likewise there can be many instances.
Severity level - Medium: defects falling under this category of medium or average severity do not have performance effect on the application. But these defects are certainly not acceptable due to non-conformance to the standards or companies vide conventions. Medium level bugs are comparatively easier to tackle since simple workarounds are possible to achieve desired objectives for performance. Examples of bugs of this type can be mismatch between some visible link compared with its corresponding text link.
Severity level - Low: defects falling under low priority or minor defect category are the ones, which do not have effect on the functionality of the product. Low severity failures generally do not happen during normal usage of the application and have very less effect on the business. Such types of bugs are generally related to looks & feel of the user interface & are mainly cosmetic in nature.
Bug Priority: refers to the need as to how urgently bug is required to be fixed. It describes the importance of the bug. Bug priority may change according to the schedule of testing. There are three levels of Bug Priority, which are described as under:
High Priority: Such bugs if not fixed immediately, are going to affect the normal functioning at customer end. Hence such bugs are given immediate or topmost priority for fixing.
Medium Priority: is allocated to the bugs with major defects having great effect on the functioning of the customer. Such bugs are allocated great priority so those related problems are resolved prior to release of the present software version. If due to some time constraint it is not possible to resolve this issue, some sort of patch or service pack must be released
Low Priority: is generally allocated to bugs, which do not have significant effect on the performance of the software at the customer end. Effort is made to resolve such bugs prior to release of the present version, if this is not feasible due to constraint of time such fixation can wait till the release of next version.
8. Explain by Screenshots - As per an old saying "A picture is worth more than 100 words". When we encounter an error, it is best to capture the screenshot of the particular moment. If an error message is seen, its screenshot will help the developer in having a precise understanding of the problem. This is the stage the developer does not try to fix the problem, rather focuses his attention to firstly understand the problem clearly.
Such screenshot should be an appendix of the bug report as evidence. This way tester is able to communicate & explain his bug in a better way & with more clarity to the developer.
9. Standby your Genuine Bugs: Most interesting portion of bug reporting is when the software tester needs to be standby the bugs found by him & needs to defend that bugs covered under his report are genuine bugs needing fixation since it is going to affect the performance of the application. During this the course, the software-testing engineer must be ready to face situations with the programmers like the few ones mentioned below.
Case 1: Developers usually hit back saying that particular bug can't be reproduced. The best way of reporting the bug is practically showing it to the developer. This can be done by asking them to have a look at the scenario on your computer system, load the application & provide live demonstration of the problematic event. This would provide them actual look & feel of the situation as to how you had fired the application, how you had been interacting with the application & how the software reacts to the inputs provided. As a best practice avoid reporting of non-reproducible bugs in an enthusiasm to report maximum number of bugs in shortest possible time.
Case 2: Sometimes the software tester comes across funny circumstances with some application having inconsistent pattern of failure. Such situations can arise when the tester encounters pressure of deadlines & the application under test fails, but he faces embarrassing moments while demonstrating the same to the developers, since the application behaves normally at that moment. Thus a good tester needs to be patient & always build a defense mechanism in the form of preserving test data & screenshots etc. to justify his statements.
Case 3: If the tester provides the developers a big list of various actions & inputs etc. but the program fails to show anything wrong when executed on the system of the developer. This means that the tester has not provided sufficient information. It is quite possible the systems of the developer & the tester differ in some configuration, thereby causing the fault not to appear on computer system of the developer. It is quite possible that the tester had misunderstood the expectations of the program, while the tester & the developer are witnessing the same display, but with a difference in viewpoint. It might be possible that what appears, as an error to the tester might be correct from the point of view of the developer. Thus to come out of such situations, it is preferred to say as to what you had expected & what you had seen exactly & what had happened.
About the Author
http://www.softwaretestinggenius.com A Storehouse of Complete Knowledge on Software Testing & QA under one Roof
The Pace Report: "The Genius of Gil Scott-Heron Part 1" The Gil Scott-Heron Interview
how to write a interview report how to write a interview report how to write a interview report
how to write a workplace report"how to write a workplace report" Dysfunctional work environment advice?
So, two days ago, there was a screaming match in my office and of the two people involved had a police report written up. Last week, another co-worker landed in jail without bail after trying to murder his girlfriend. The list goes on and on. Truthfully, is this how most workplaces are as I don't know if it's me or if its normal??
its just the place you work at, get out. please it will help me you and the other 7 billion people on this planet sleep at night
Henry Blackaby - Bringing faith into the workplace based on Biblical principles
how to write a workplace report how to write a workplace report how to write a workplace report
technical writing resumes"technical writing resumes" Is it possible for me to get a per diem physical therapy assistant job?
I am employed full-time and have a BS Biology with a good GPA from a top college and have clerical, technical writing, and customer service experience. The problem is I have had too many jobs and no clear direction. If I get a 4.0 in the A.S. program, will I even get calls for interviews? I know there is great demand in this field. I thought of writing a career-change resume that would highlight my hospital volunteering experience, my experience dealing with at-risk students, and my scientific writing skills, as well as my health-related background. Do you think this strategy will work? I had a problem with tardiness before, too, but not recently.
When you say the A.S. program, I assume that means you are enrolled in an accredited PTA program. If not, you will not be able to work as a PTA...only a tech.
However, as a PTA, per diem work is always possible. Weekends at hospitals, nursing homes and rehab centers are always hard to fill.
Business & Creative Writing : Writing a Teaching Resume
how to write technical resume"how to write technical resume"
Top Tips for Writing IT Resumes
The main purpose of writing a resume is when one wants to land up for a job. Resume is a document which contains the details of your identity and the purpose of doing job. It is the prime step which one puts to apply for the job. Hence, it is essential to make such a resume which could be selected by the interviewer.
Some of the best tips to write IT Resumes are as follows:
1) While writing a resume one should identify the purpose. Some of the candidates write a large document which seems to be boring and written desperately. The main motive of the resume is to provide you the job, so make a meaningful resume.
2) Some of you write unknowingly a long boring document which is rejected by the employee as the first glance. Hence while writing IT Resumes, stress on your job objectives, experiences, skills, education etc. Try mentioning it your qualities and it should not appear as you are trying to exaggerate yourself.
3) The keywords should match your job profile, hence use the IT related keywords which shows your technical abilities. If your resume don not support the IT job keywords then your resume would be surely rejected.
4) Give effectual titles so that it would be able to catch the employee attention as there are several other candidates resume lying under the employee desk. Try to give descriptive title so make your resume become an eye catchy.
5) As there are many other resumes lying in front of employee, so they would not have so much time in reading long paragraphs. Therefore, while writing, use bullets and write short sentences. But avoid using excessive bullets.
About the Author
While writing IT Resumes make sure to get all the relevant information about the job and the company you are applying for.
IT Resume Writing - Technical Resumes
how to write technical resume how to write technical resume
writing technical resumes"writing technical resumes" When reapplying to a company, should previous employment be addressed?
Helping a friend write a job application letter for a government security police company. He resigned from the company four years ago, and is unsure whether or not to address this fact in the letter. A large portion of his resume features this previous job and the qualifications he received while employed for the company.
Business and technical writers...what would you do?
he should deff mention it and explain why he left. it would be a good thing to have had previous experience in the same place.
