Interview Guide SAP Hybris
Interview Guide SAP Hybris
Interviews
http://www.runhybris.com
Colin Longworth
B.Eng, M.Eng, MSc. Mgmt
1
Introduction
This document is designed to give you an overview if what you should expect when
attending an SAP Hybris job interview. We’ll break down how you should prepare, how
you should conduct the interview and how you you should follow up. Remember, SAP
Hybris is a large, multi-faceted system and you should have ample experience before
attending an interview. Above all, the very best of luck in your interview and SAP Hybris
career!
Important
● This document is a guide and should be treated as such. This guide is not a
guarantee or an interview or job offer.
● SAP Hybris is a large system and questions can be made from any aspect of it.
You should be familiar with all elements of the SAP Hybris system, not just the
areas highlighted in this document.
● You should always revert back to the job posting and ensure you are prepared
based on what the job is expecting you to deliver.
This is the most technical of the SAP Hybris roles and requires a strong understanding
of Java and the Java Spring Framework. Most roles require experience with SAP Hybris
along with SAP Hybris project experience. Many jobs will ask for SAP Hybris Developer
Certifications from SAP, known as HY400 and HY410, but these are rarely mandatory.
They are however a significant advantage as worldwide, there is a shortage of qualified
SAP Hybris developers. If you have no experience with SAP Hybris, you should
showcase your understanding of Java in an enterprise scenario or on similar systems.
Knowledge, or experience of, other ecommerce systems is a significant advantage e.g.
Magento.
2
The business analyst role is a functional role in the SAP Hybris job domain. Your role
will be to take customer requirements and contrast them to the capabilities of Hybris,
determining if a function can be created without customisation or code. You should
have extensive experience of all elements of SAP Hybris, along with significant time on
the system itself, exploring the capabilities and features. You should be comfortable
demoing the system and know how basic to intermediate functions are carried out.
Code level knowledge, for example how the Drools Engine works, are not strictly
required but this is a distinct advantage. You should have a strong understanding of a
business analyst role especially within a development cycle (e.g. Agile Scrum). Lastly,
you should have a basic understanding of coding, development and the overall software
cycle.
The System Administrator is the highest level role for SAP Hybris jobs and is rarely
confined to SAP Hybris. A System Administrator will largely operate the entire
landscape of a company, or be tasked with an element of it. As a System Administrator,
you should be aware of how SAP Hybris starts, runs and shuts down. You should be
familiar with its performance topics, be able to instrument SAP Hybris and have an
understanding of the logging functions. You should be aware of all cockpits of SAP
Hybris and be familiar with their features. Knowledge of networking and clustering is a
significant advantage, along with knowledge of the Tomcat and similar Java engines for
web platforms. Experience of databases, including disaster recovery, is key in large
scale SAP Hybris installations. You should fully understand Apache Solr. As a systems
administrator, you will rarely be tasked for functional or code-level topics but a high
level understanding of each is advantageous.
The SAP Hybris Architect is the broadest role of the SAP Hybris suite. The role however
can be broad or extremely focused. In generally, an architect develops from numerous
projects and generally come from the developer or business analyst stream. Generally
speaking, the business analyst (BA) stream is the most advantageous as the BA is
tasked with speaking to stakeholders on a technical and non-technical basis. As an
architect is generally tasked with creating the system, end to end, they are required to
3
engage with stakeholders from all areas of the business. As an architect, you must be
intimately familiar with Hybris, it’s features and how it can integrate to other platforms.
You should have an understanding of the wider Hybris and SAP CX suite, and how
different systems interoperate. You will need to keep abreast of developments in the
suite, including new releases and updates, to ensure you knowledge is current. Similar
to a BA, you will require knowledge of all functional aspects of the suite, but unlike a BA,
you will also need technical knowledge of how the suite operates and how it is best
leveraged.
Interview Questions
The scope of your SAP Hybris interview questions will depend on your role. You should
revise the following topics as part of your interview study using both online resources,
RunHybris.com and the SAP Hybris Wiki.
● Explain the typical use for Cron Jobs, ImpEx scripts, workflow and addons.
Identify integration points with the SAP Hybris commerce suite, hierarchy of
users,users' roles and validation rules.
● Distinguish between various backoffices and cockpit applications and their
purposes, demonstrate an ability to perform basic tasks in them such as
extending simple workflow or triggering synchronization. Be capable of
explaining the concept of catalog versions.
● Identify standard functionality available in SAP Hybris Commerce suite including:
e.g. B2B, SOLR, Subscriptions, Bundling, Entitlements, mobile and responsive
storefronts. Create standard CMS components and explain the checkout
process.
● Explain concepts of variants, categorization and classification, and identify
possible approaches of adapting the SAP Hybris data model to match
customer's product, customer, CMS content and pricing models.
● Demonstrate how to use ImpEx and Flexible Search. Explain the Service Layer
and the SAP Hybris Cache. Explain Test Driven Development and Unit Tests in
Hybris. Discuss the Commerce Services and Facades, the Spring MVC and
DTO's. Give an overview of Search & Navigation from a technical standpoint.
Explain the out of the box factors that impact SAP Hybris Security. Give a high
level overview of SAP Hybris Integration Strategies to other SAP products.
5
● Discuss Service Layer Interceptors and how you would customise them. Explain
Pricing and how it could be customised to reach a requirement. Discuss Coupons
and Promotions including their use in the Payment flow. Give a technical
overview of the Events system and a use case for it. Explain the Process Engine.
Give an end to end account of the Order Management system in SAP Hybris.
Explain how SAP Hybris Cron Jobs can be customised. Underline the importance
of Transactions and how they occur in SAP Hybris. Discuss Advanced
Personalization and the Backoffice Framework, explaining how you would
customise both. Explain your most recent SAP Hybris project including three
requirements from differing SAP Hybris component areas e.g. Data Model,
Pricing, Promotions, CMS etc.
● Discuss the SAP Hybris support framework including support from SAP
themselves. Give an overview of monitoring tools, how they work and important
criteria to be monitoring for. Explain Hybris clusters and the impact of cache
within the cluster. Discuss, at a high level, how clustering and tenants work in
SAP Hybris. Explain where log files are located in SAP Hybris. Give an overview of
the build, deployment and start up of SAP Hybris. Discuss how you would backup
and restore SAP Hybris in line with best practises. Give an end to end overview of
traffic from the outer web via your network infracture to SAP Hybris including
SSL termination.
6
The following are questions that we have experienced or consider good questions for
an SAP Hybris interview. This list is not exhaustive and not all of them would be
applicable for your role or SAP Hybris area. You should be able to confidently answer
the majority of these questions and give a full example where applicable. Ensure you
can give between 3 and 5 lines of an answer per question and revert to your own
experience where possible. We recommend you do not use stock answers or answers
prepared by someone else.
How would you add a facet to the Solr What is Apache Ant? Why do we use it?
search?
What is the standard that SAP Hybris
What is a Java Bean? use to develop their code?
What is the Spring Framework and how What is Git? Have you used SVN?
does it relate to SAP Hybris? Explain how you would write your own
code, test it and then push it to the code
What is Spring MVC?
repository.
How would I customise a storefront in
How would you test your SAP Hybris
SAP Hybris?
code without starting the server? Can
How would I begin to set up my IDE to you do this?
develop in SAP Hybris?
What is dependency injection?
Explain the concept of the c
ustom folder
How would you modify the checkout
to me.
flow of SAP Hybris?
My developers need to change some
code in SAP Hybris itself, when should I
7
How would you add a new CMS banner Explain the search process in SAP
to SAP Hybris? Hybris.
What is SOP and HOP pages in the What is the difference between
checkout flow? How would you add or categorization and classification?
remove them?
Our customer has a brand new product
Explain the Drools Engine to me. that needs extensive changes to the
Hybris data model, how would you do
How would you add a new promotion to
this? (This question generally has an
Hybris?
example given to you)
Write a sample ImpEx to import a
What is deployment?
Product
What is a DTO?
Explain ImpEx macros and other syntax
elements. Explain the Type system.
Write a sample flexible search query to Explain I tems.xml, why it is needed and
return all Products. when it is used.
Follow Up Interview
● Thanking your interviewer for their time and asking when you should hear the
results of the interview.
● If you do not hear after 2 weeks, you should follow up with your interviewer for
feedback.
● Always request feedback, especially technical feedback, as this can assist you in
your next interviews should you be unsuccessful.
● Arrange a one on one consultation with RunHybris.com if you feel you have an
area that requirements improvement.
Good Luck!
oOo
Version 1.0
July 2018