Might be helpful for you!
1. Keywords: If your resume doesn t repeat the right keywords (or search terms) numerous times searchers are unlikely to find it. It s a sad fact but resumes are ranked based on how many times they repeat the right keywords.
2. Critical Keywords - Job Titles/Job Descriptions: When headhunters and hiring managers search for candidates they use the major definitive elements of the job. Keywords are not cross-functional multi-tasking interpersonal skills or other nice-to-include descriptive jargon. Those are good to have somewhere (if relevant) but only once or twice at most. Instead your resume should repeat basic core search terms. Job titles - creative director business analyst CFO. Job descriptions - creative direction business process analysis corporate finance. These should be repeated in your resume s headline opening section every job description - wherever you can fit them.
3. Synonyms : You don t know exactly which keywords your dream employer uses. So to cover all the bases you also need synonyms: comparable titles and parallel job descriptions. Here s a good keyword-loaded job description opener: Promoted from Software Developer to Senior Software Developer to serve as lead programmer / analyst for major software development / software engineering projects.
4. Qualifications Summaries: Another way to up your keyword count: opening summaries. These enable your resume to highlight your most relevant strengths immediately - and also offer another opportunity to reiterate keywords.
5. Resume Keyword Lists: Finally list specific terms. It s a perfect way to showcase your diverse skills and add even more keywords. You don t have to name it a nerdy Keywords. Label your table Strengths or Expertise listing 3-4 keywords per line in a professional organized appearance.
6. Readability and attractivness: Make it very presntable use the fonts and sizes which are popular and professinal.
7. Certifications: List the Related Certifications this goes long way.
8. Hobbies: Avoid personal hobbies on the resume.
9. Personalization: Customize the resume for the requirment (Highlit the points which suit the requirment).
10. COntact Details: List the best email address where you can respond quick and phone numbers (two are good).
Note: It’s copied from Lucid Jobs
J2EE as a dominant paradigm/technolgy of solution implementation has been there in the industry for over a decade. Enough time to develop some best practices (some times more than warranted).
If you go by conventional wisdom of industry and its median practice we would come across such as these (listed below).
“The best of the best practices”
Always use MVC.
Don’t reinvent the wheel.
Apply automated unit tests and test harnesses at every layer.
Develop to the specifications, not the application server.
Plan for using Java EE security from Day One.
Build what you know.
Always use session facades whenever you use EJB components.
Use stateless session beans instead of stateful session beans.
Use container-managed transactions.
Prefer JSPs as your first choice of presentation technology.
When using HttpSessions, store only as much state as you need for the current business transaction and no more.
Take advantage of application server features that do not require your code to be modified.
Play nice within existing environments.
Embrace the qualities of service provided by the application server environment.
Embrace Java EE, don’t fake it.
Plan for version updates.
At all points of interest in your code, log your program state using a standard logging framework.
Always clean up after yourself.
Follow rigorous procedures for development and testing.
Please see http://www.ibm.com/developerworks/websphere/techjournal/0701_botzum/0701_botzum.html
Everyone is aware of Dashain here. But in a working environment there’s no feel of Dashain till now.
