 |
Search
IT Courses |
|
|
|
|
|
|
|
|
|
|
|
IT
dart News Letter
|
Get
ITdart.com weekly headlines before it's published on our site! Subscribe
and receive the articles delivered to your inbox!
|
|
|
Resume
RÉSUMÉ
Writing a resume need not be a daunting task that calls for specialised skills. But some basic rules must be followed to make your resume have the desired effect on a prospective employer. Here, we tell you about the basic components of the resume and how to piece it together. The idea is not so much to impress the employer, but put together all the necessary information in a manner which will make it easy for the employer to know what he wants to know about you, and what he should know about you.
RÉSUMÉ BLOWUP
When we write our résumés or attend interviews we often tend to forget some insignificant work done in a particular project that could be very relevant to the client's current requirement. Also we tend to overlook the small details about our personal information. The blown-up résumé helps you to overcome both these problems.
The blown-up résumé is personal and not to be given to anyone. It is meant to support your résumé (which needs to be job focused) writing and interview preparation.]
KEY INFORMATION
The key information in a résumé from the employers point of view is, what work you are able to do and what potential you have, vis-à-vis his requirements. This is to be brought out clearly in the RESPONSIBILITIES section of the assignments in the résumé. Some samples are given below.
POSITION: Software Analyst / Data Base Administrator.
PROJECT TITLE : Z 2 (Integrated Store Management System)
PROJECT SCOPE: The project involved the development of an integrated Store Management System for E ZEE BUY retail outlets. E ZEE BUY has over 200 outlets in the UK and deals in over 1,40,000 items. The small stores have an average of 15 counters and the larger ones about 80. The system consists of the accounting, inventory, sales and marketing, human resources and administration.
RESPONSIBILITIES :
Designing databases.
Implementing, indexing, denormalising and partitioning schemes.
Reviewing program and SQL Design for optimisation choices.
Using EXPLAIN PLAN for SQL analysis and to administer RDBMS applications proactively.
Customising Oracle 7.1.
Organising and creating Oracle users / UNIX users.
Monitoring security grants and verifying table space utilization.
Scheduling and taking regular back ups.
TECHNICAL ENVIRONMENT: Team Server (PENTIUM Based), UnixWare : 2.0 Oracle 7.1.
LOCATION : London , UK.
POSITION : Project Leader.
PROJECT TITLE : Hospital Management System.
PROJECT SCOPE : The project involved the development of two modules of the hospital management system. The system was for the pharmacy inventory as well as patient registration at ABC’s Hospital out patient department. On-line pharmacy inventory was maintained by the system, which was also integrated with stores management system and personnel information system. The module generated various reports and queries on : category wise OPD patient visits, doctor wise medicine issues, patients against a particular medicine, employee wise / patient wise medicine expenditure etc.
RESPONSIBILITIES :
Carrying out the complete software development life cycle.
Preparing requirement specifications / systems specification.
Carrying out initial system design consisting of context diagram, DFD, entity relation diagram, normalisation of tables and table structure and definition with declarative constraints.
Creating indexes after analysing SQL, for optimisation and testing using EXPLAIN PLAN statement.
Carrying out physical design including screen and report layout.
Developing 16 complex forms using forms 3.0.
Coding of 22 PRO
C reports.
Testing.
Preparing user / system / operation manuals.
Implementing the system.
Conducting user training.
TECHNICAL ENVIRONMENT: VAX ALPHA 3600, Open VMS 6.01, Oracle 7.0, SQL · Forms 3.0, L / SQL 2.0, SQL · MENU 5.0, Turbo Analyst, Relational Designer Pro · C.
INTERVIEWER'S VIEWPOINT
The purpose of your résumé is to provide the interviewer with information to assess your suitability for the job. While it is necessary to provide as many supporting details as possible it is as important to be brief and concise. Winning résumés generally meet the following criteria:
FOCUSING
Bringing relevance to the job i.e. Programmer, Analyst, Designer, Data base Administrator, Team leader etc.
CUSTOMIZING
Matching skills to requirements and highlighting or elaborating areas of particular interest to the interviewer e.g. Platforms, Languages, Database, Tools Lines of business etc.
SPECIFYING
Providing detailed information on role responsibilities of work carried out i.e. Coding, requirements study, change management, client interaction, estimation, data modeling etc.
QUANTIFYING
Giving details regarding the extent of activity or usage, i.e. lines of code, number or reports / screens designed, extent of tool usage etc.
QUALIFYING
Differentiating the work done i.e. complexity, features of tools used, function of deliverables, project management techniques / methodologies used etc.
AMPLIFYING
Highlighting special accomplishments in work done to meet / beat targets, milestones or bench marks i.e. Problems solved, breakthroughs made, extra responsibilities accepted midway through the project, motivating, counseling, co-ordination, managing resource crunch, etc.
UNIFYING
Consolidating all aspects of the résumé to project your area of core competence / expertise i.e. predominant skills, knowledge area or line of expertise.
BOLSTERING
Elaborating on the project, customer or company is important especially when project features are unique or company / customers are reputable. However, it must be borne in mind that the interviewer is interested in this aspect only in the context of your capabilities and contribution i.e. working for a reputed company would mean having satisfied their selection criteria. For customers it could be quality standards or line of business. For projects it could be related to size, complexity, quality, specifications, etc.
|
|
|
