Skip to main content

CV Preparation





An old saying, - First Impression is the best impression. When we are applying for the jobs, chances of getting interview depend mainly on CV. Each location has its own CV format. While applying for an UK based job you need to sent a standard UK  format CV(optional cases some organisations do not accepts CV). 



1 Header with Name, phone number and email address (avoid address)

2 Career Conspectus – Describe about your experience, what technology you familiar with, what domain you got experience etc

3. Technical Skills – Mention all the technical skills on this section (In good format, if necessary use tables)
4. Certifications - Mention about the Certifications passed.

5. Employment Chronicle- Mention about the professional experience (Most recent first).Include Project name/Client name  , a brief summary  of project, your responsibility (Means role in the project), and the environment(Which  technologies used) which the projects works
6. Internal ship-Mention the internal ship undertaken
7 Academic qualification -Give a brief description about you qualification (Most recent first)
8 Mention about the Reference (No need to add it in CV, just mention available on request)
These are the common areas need to cover in CV.
The maximum length of the CV should be less than 4 page
Last but not the least
CV should be in a good format, can get some good templates from job sites. 
NB: - Avoid spelling mistakes (I know, I make a lot spelling and grammar mistakes)
Best of luck for the job search !!!
 





Comments

  1. CV length should not be more than 2 pages ideally.

    ReplyDelete
  2. Thanks for the comments. I actually like to see comments and more debates. Then we people can share the knowledge.

    Not like actually. If you are applying for a graduate role CV length should not be more than 2 page. But for the experienced guys can keep the CV length up to 4 pages to include all your expertise.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to write secure mvc application using encrypting URL

There are lots ways available to write the secure Mvc application. In my experience I came across lots of secure application in public facing. I want to tell about some of the mechanism I followed. 1- encrypting the URL Parameters and preserving id's encrypted on the client side 1- I always make sure if I pass Id or any sensitive data into the view always make sure it's encrypted. By doing so make sure if we forced to use HTML.hidden or HTML.hidden for have the encrypted values, in action link if I pass any parameters from the client side (eg:- edit or create or navigating between different actions we can make sure that all the values are encrypted) During the design of the actions results if it's http get I usually encrypt the sensitive data [httpget] Public actionresult display() { TestModel testModel=new TestModel(); testModel.id= encrypt(id); Return View(testModel); } [httppost] Public ActionResult Display(string id) { Guid d_id= new Guid(decrypt(id));

Single page application (SPA) using ext.js

what is spa? Single page application are applications that fit in one page with rich and fluid user experiences like a desktop based applications. Why is SPA? All web based elements (html, CSS,javascript) are downloaded from the server on single page load and avoid the continuous page post back. i can explain what this mean. Suppose your web application is made of certain flow and it consists of 5 different pages. Each page need to get data from the user and save before moving to the next page. So when we navigate from one page to other it need to make a round trip to server to store the data in one page and get the data for the next page to display. but in spa we can avoid the continuous post backs. The whole page will not post back any time other than the first load. But it communicate to the server dynamically behind the scene and can achieve the same functionality. Spa using ext.js designing a SPA using ext.js is a challenging task if you are unaware about the ext.js

Sql Server Internals - Named Pipes

Named pipes enables clients applications to request a reliable and two way connection between the client application and Sql Server, across a network. A named pipe has a name which follows the UNC naming convention : \\Server\pipe\name The default names pipe for SQL server is :                 \\Server\pipe\sql\query A named instance would have a named pipe of                \\server\pipe\MSSQL$instancename\sql\query Early versions of SQL Server only provided Named Pipes. Named Pipes also allows for impersonation of a clients credentials. The feature is used by SQL server when using Linked Servers. The clients logon credentials are passed across to the Linked Server for authentication. Named Pipes can operate over TCP/IP, NETBEUI or IPX as it indirectly relies on the Common Internet Files Sytems