I want to restructure my resume so that the first page displays a hierarchical tree of qualifications. My goal is to advertise myself like a tradesman who lists what he can do on the side of his van rather than using a list of employers in the descending chronological order and then the potential customer (AKA employer) has to fish out your credentials by scanning each employer listed. I also think that this approach puts me and my skills in the foreground rather than who I worked in the foreground and let me be evaluated by who I worked for.

I still plan to list the employers but give a much briefer description of each job as I would like to put less emphasis on that than on my actual skills that I'm bringing to the table.

Considerig that I am breaking the convention but also considering that I want to weed out conservative employers who do not appreciate doing thing innovatively, is this a good idea? If not, can you suggest a compromise but something that in format differs from traditional resumes? My aspiration is to market myself as a contractor who comes in, does the job, and leaves, and as such, I want to differentiate myself from the get-go, i.e. the first kick in the door.

Languages
    |
    |--Java
    |    |
    |    |--Web 
    |    |   |
    |    |   |--JSP/JSF  
    |    |
    |    |--App Server
    |    |   |
    |    |   |--GlassFish 
    |    |   |--WebLogic 
    |    |    
    |    |--Framework
    |        |
    |        |--Spring 
    |        |--Jersey (JAXB-RS) 
    |        |--Hadoop/MapReduce 
    |
    |--Perl
         |
         |-- (...)
    
Data Management
    |
    |--SQL
    |   |
    |   |--Oracle 
    |   |--MySQL
    |
    |--No SQL
        |
        |--MongoDB 
        |--Redis

(...)

I want to restructure my resume so that the first page displays a hierarchical tree of qualifications. My goal is to advertise myself like a tradesman who lists what he can do on the side of his van rather than using a list of employers in the descending chronological order and then the potential customer (AKA employer) has to fish out your credentials by scanning each employer listed. I also think that this approach puts me and my skills in the foreground, rather than who I worked for in the foreground, and it lets me be evaluated by what I did instead of who I worked for.

I still plan to list the employers, but give a much briefer description of each job, as I would like to put less emphasis on that than on my actual skills that I'm bringing to the table.

Considering that I am breaking the convention but also considering that I want to weed out conservative employers who do not appreciate doing things innovatively, is this a good idea? If not, can you suggest a compromise, but something in a format which differs from traditional resumes? My aspiration is to market myself as a contractor who comes in, does the job, and leaves, and as such, I want to differentiate myself from the get-go, i.e. the first kick on the door.

Languages
    |
    |--Java
    |    |
    |    |--Web 
    |    |   |
    |    |   |--JSP/JSF  
    |    |
    |    |--App Server
    |    |   |
    |    |   |--GlassFish 
    |    |   |--WebLogic 
    |    |    
    |    |--Framework
    |        |
    |        |--Spring 
    |        |--Jersey (JAXB-RS) 
    |        |--Hadoop/MapReduce 
    |
    |--Perl
         |
         |-- (...)
    
Data Management
    |
    |--SQL
    |   |
    |   |--Oracle 
    |   |--MySQL
    |
    |--No SQL
        |
        |--MongoDB 
        |--Redis

(...)