Qlik Community

QlikView Documents

Documents for QlikView related information.

QlikView Developer Skill Set

dvqlikview
Honored Contributor II

QlikView Developer Skill Set

QlikView developers come from different backgrounds & skills. Generally speaking, we can divide QlikView developers into two categories: Organic & Tailor-made.

Organic QlikView developers come from one of the streams – Traditional BI/ETL Developer, Database Developer, Data Analyst, Excel Developer, Web Developer, Test Analyst, Business Analyst and a DBA. Coming from one of these streams have both advantages and dis-advantages in Qlik world. Personally, I have done almost all of the above jobs before making my debut into Qlik world. Experience of data handling and analytical thinking is a big plus if you come from one of the above streams. And the dis-advantage is unlearning what you already know; because you need to approach in different way whilst developing in QlikView.

Tailor-made QlikView developers are budding new developers who start with QlikView or developers who move to QlikView from non-IT background. Generally, these developers are fresh graduates or first timers who approach QlikView with great enthusiasm & passion. It’s easy to get started with QlikView and most of the time you will start feeling comfortable within weeks instead of months or years. However, very soon you will realise that – the more you know, the more you need to know!

After thinking hard, I thought the following are the essential skills to be a successful QlikView developer on the long term basis.

QlikView Developer

  • Understanding Data/Business: No matter how good you are with the code, but you still need to know the data you are going to deal with. It’s very easy to start development just thinking about the tables, columns & rows but you will soon hit the brick wall, just after finishing the scripting. Understanding business data rules is a critical aspect to calculate KPI(s) and measures. Last thing you wanted is good looking application with jaw-dropping functionality and not answering any business questions. As a developer, we all get excited solving problems and designing functionality but it’s very important to understand the business data for successful QlikView application.

  • SQL/Data Modelling: Having good understanding of traditional data modelling techniques is a big plus. Simple analogy – I can compare traditional data modelling skills with Badminton and QlikView data modelling with Squash. Although these two games are different but there are some common skills. So, having traditional data modelling skills definitely have good value within Qlik realm.


  • Microsoft Expression Language: Those who have advanced Microsoft Excel and/or Visual Basic skills will always find QlikView expression language easy to understand. Because, some of the functions available in QlikView are also available in Excel/Visual Basic. There are many powerful new functions in QlikView Expression language. On average, every QlikView developer will spend at least 25% of their development time in writing QlikView expressions. So, having good understanding of QlikView Expression language is a must have skill.


  • UI/UX Design: QlikTech separated QlikView Developers from Designers. But in reality, almost all the companies just have one person with two hats and sometimes even the third hat as QlikView admin. Every QlikView developer should have good understanding of data visualization techniques. There are plenty of options in QlikView to represent your data but it takes special skills to present them in the simplest yet effective way. I have seen many developers who are really good with the script & data modelling but they struggle designing a good UI (User Interface). With good eye for UI design & detail you can create the instant “wow” effect within <=5 seconds of launching the QlikView application.


  • Web Development: As a QlikView developer, this may not be essential skill. But, having good understanding of web development life cycle and web architecture is very useful. These skills will help you if you need to develop Extension objects in QlikView. Not just Extension object but QlikView.Next will be based on HTML 5 & JavaScript. So, for now it’s in “good to have” category which will change in future as “must have”.


Elsewhere: Steve Dark made a great post on similar topic - What makes a QlikView Developer?


Cheers - DV

www.QlikShare.com

Calibrate Consulting

Comments
richard_pearce6
Valued Contributor

Thanks for sharing DV, great post and fits in well with Steve's topic and between them its clear what makes the difference between a good QlikView Developer and a great one.

Rich

QlikCentral.Com

Not applicable


Great job....

kirankkk
Contributor

Totally Agree.

preminqlik
Valued Contributor II

thank u and great job...

Not applicable

Good post.

I think you have the skill set catagories correct, I would think the proportions in your chart would be different depending on the particular requirement, Large enterprises may have the SQL/Modelling skills and the Understanding of the business/data, but need help in the UX design and web presentation.  They may have design skills in house and merely need the developer to realise their vision.

I would add a two more though.

Communication skills

All too often I see projects fail to deliver on time, as the initial requirements have not been fully discussed and full design specifications documented; changes are made to requirements as the project progresses causing rewrites and delays, and all because the original developers and Analysts could not effectively communicate with the business function.

Documentation skills
Documentation in both design specification and functional requirement gathering are essential, each party should have clear documentation of what is required and what is expected.  All before the developer logs into Qlikview.

Also documentation is often missing in the development lifecycle, and you have to be aware of the next person to look at your code, and make changes.  Too often Qlikview expressions resemble an explosion in a typesetters workshop, and whilst is may be elegant to the initial developer, it takes a long time to de-cipher for the next developer.  (or indeed the original developer, a year later!)

Richard

dvqlikview
Honored Contributor II

Makes sense Richard. I agree that - Communication & Documentation Skills are important but I would implicitly expect any Dev to have them.

Not applicable

10 years ago, I would have agreed.  However, as someone who does recruit, I can see a distinct change over last few years, where inexperienced IT people grab onto an emerging technology like Qlikview and go for the "qualifications" they then sell themselves as a Qlikview expert, however some of the basics like communication, documentation, analysis, best programming practice are missing.

I see your article as a useful checklist for recruiters who need qlikview expertise, and hopefully avoids this pitfall.  I also see same issues with Microsoft qualifications, and Linux.

The IT vendor qualifications sometimes muddy the waters when it comes to recruiting.

richard_pearce6
Valued Contributor

Hi Richard,

I agree, that happens so often these days and its a shame for people who have developed skills over many years. The post does talk about these types of people, if QlikView is your core skill set there's probably another pie chart needed to cover all the possible skills you can acquire.

I see this post as a guide for QlikView people to expand their knowledge to the peripherals of QlikView and help them develop rather than an aid to recruitment. Maybe Deepak Vadithala had another purpose in mind.

Richard


Not applicable

Richard,

I agree you are right.  I will step down from my soapbox.

Excellent post though, certainly generated some thought.

Thanks Deepak for a great post.

Regards

Richard

dvqlikview
Honored Contributor II

Thank you Richard & Richard.

Richard Pearce you're absolutely right with your comment.

Cheers,

DV

Version history
Revision #:
1 of 1
Last update:
‎05-20-2014 04:28 AM
Updated by: