My name is Bharathi I am working as a Technical Recruiter with National consulting group.

Please find the below position and reply back to with updated resume ASAP. I need following details for submission.

Full Name :

Current location;

Contact Number:


Availability for Face-to-face interview (Yes/No):

Relocation :

Visa Status :

Expected Rate:

Employer Details:


Position: Senior Java, J2EE Developers (2 Positions)

Loc: Long Island, NY

Duration: Long Term (2-3 Years minimum with a great possibility of further extension)

Rate: max $55/hr on c2c

Start: Immediate

Interview - 1 Round of direct In-person Face to Face interview must. No Telephone or Skype Interview.

We are looking for 2 Strong traditional Senior Java, J2EE Middleware Developers to start immediately in Long Island, NY. We are implementing this project at the client site and this is our own SOW project. Any help needed in H-1B filing, extension or stamping will be provided.

Only Local Candidates required as Face to Face Interview is must after the telephone round. Please do not submit out of state candidates or who can not come for Face to Face In-person interview on their own expense.

This is our own SOW position and we are looking to fill for a replacement of the candidate who is leaving to India on an emergency. Immediate interview assured.

An immediate interview is assured for the right candidate. Please make sure that the resume is a 100% match to the skills required below. Please submit the candidate with best minimum rate and contact information.


The role is for a senior Java J2EE developer who will help implement inventive solutions for a large-scale online ECommerce, in conjunction with a global development team.

* Minimum 8 Year of Strong Java/J2EE development experience including Core Java (1.5 or above), JSP, Servlets, JMS and other J2EE technologies for large complex systems with emphasis on middleware server side development

* Hands on development experience with traditional JSP, Servlet, XML, XSLT, DTD, DOM, SAX Parsers (WOODSTOX preferred), JMS, Active MQ

* Strong conceptual understanding of Object oriented Design and development.

* Experience using various Java (J2SE and J2EE)Design Patterns.

* 2-3 years of experience with Spring or any other web development Framework

* Must have Service Oriented Architecture (SOA) based application development experience

* Experience with Enterprise Service Bus (ESB) is a big plus

* 3-5 years of strong hands-on development experience with MS SQL Server or/and Oracle.

* Strong in TSQL or/and PL/SQL programming including the Stored Procedures

* Experience designing on-line Content Management web applications is highly preferred.

* Any Experience designing and developing applications with Search Engine is big plus.

* Build release experience with ANT and or Maven.

HIRING MANAGER NOTE: Need strong technical candidates with excellent communication, Great Attitude, A passion to learn new and challenging technologies and long term commitment to work on project for next 2-3 years.

Great team and an excellent environment to work with No pressure and peers to support. This position is good for some one who is looking for a stability for next 2-3 years with No tension of H-1B extension, stamping etc.. as we provide full support.

Highly prefer local or east coast candidates.


Bharathi | IT Recruiter

Direct # 908-333-5825

National Consulting Group INC


Gtalk: barati.ncg

YIM: barathi_ncg

Technical writing requires the ability to write clearly, plainly, and accurately about extremely complicated material. If you can do that-and quickly-then becoming a successful technical writer is well within your grasp.

The most common clients for freelance technical writers are educational firms, training companies and manufacturing/electronics/software companies. All of these demand a high volume of documentation-style writing, and thus a high volume of technical writers to produce that writing. However, the nature of technical writing indicates there aren't many opportunities outside these industries. Tech writing is only warranted when there's something sufficiently complex to explain in a standardized way, and a mom n' pop software company may not have the money or the need to hire even an entry-level tech writer. So if you want to freelance as a tech writer, you'll almost certainly wind up working on contract for one of the bigger companies.

As with copy editing and journalism, a high degree of familiarity with as many style guides as possible is mandatory for any good freelance technical writer. Technical reports are frequently only a small part of a company's wider technical literature. Writing all of a company's documentation in the same style is a good way to ensure consistent quality and readability over a long company lifespan. The most commonly used style guides are AP (Associated Press), MLA (Modern Language Association), and Chicago. Strunck and White, although older, is still a classic, and commonly in use with certain firms. Pick up a copy of each and familiarize yourself with them. Knowing the popular style guides will improve your technical writing and you'll become more marketable to a wide variety of clients as well.

Once you know which style guide your client works with (and once your own style is clear enough to write effectively), you'll need to start thinking about how to approach your material. Contacting and interviewing SMEs (Subject Matter Experts) is often a huge part of effective technical writing. Without good technical information supporting your work, you won't know what you're writing about. Engineers, technicians and professionals who have to use the work you create won't know what you're writing about either. This leads to a severe loss of productivity and of money, and probably to the loss of your reputation at the company as well. So make sure you have enough data to write your report, and make sure you understand it as thoroughly as possible before you start planning your articles. No one expects you to know as much about, let's say, a supercollider as a nuclear physicist (especially not on a deadline), but knowing the basic theory and how to use most of the technical vocabulary is beneficial.

The one principal rule of good writing in any field is "know your audience." This statement is truer of technical writing than any other form of freelance writing. Your audience, in technical writing, is going to use the processes, machines, and equipment you write about. If your audience can't understand what you're saying or follow the flow of your argument, you've failed as a tech writer. Clients likely won't hire you for future contracts.

Think carefully about whom you're writing for. Do the users have a background in the theory behind the machine, or do they just need to know how to pull the levers and push the buttons in the right order? Will the users have ready access to troubleshooting facilities (i.e. assembly line workers with a machine shop on the factory premises); or will they have to go to some lengths to fix any mistakes they might make in operation (i.e. people who've bought a new operating system and have to drive an hour to whenever their computer needs service)?

Take some time to think about your end users, their likely qualifications, their questions, and their overall needs. Structure your articles to follow their probable concerns in the order they'll come up. If you need to, talk to some of your prospective end users and ask them questions about what they find problematic in their jobs. It'll help you think of their problems more when you're structuring your work, and that'll make your work that much better.

Once you have your basic structure and some idea of the logical flow of your report, all that's left is the description. Be as clear as possible while still keeping a readable style, and be as accurate as possible. Don't be afraid of footnotes and additional information-unless it's specifically prohibited by your client's style policy. As long as you're thinking of your audience, and you've done the appropriate research and structuring work, this part should be straightforward.

If you can synthesize information from SMEs, keep your audience well in mind, and describe complicated processes clearly and simply, then you have the basic skills to be a successful freelance tech writer.

Watch the classifieds and make inquiries at engineering and training companies. You have a skill that's in high demand. If you keep yourself in the marketplace (and are willing to accept a "trial period" with lower pay, in some cases), it's only a matter of time before you establish yourself as a tech writer. Over time you can develop a reputation that'll win you contract after contract and keep your technical writing career alive and thriving.

About the Author :

For tips on squirrel feces and squirrel repellent, visit the Squirrel Deterrent website.