<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zuzana Andel on Medium]]></title>
        <description><![CDATA[Stories by Zuzana Andel on Medium]]></description>
        <link>https://medium.com/@zuzana.vojtekova?source=rss-46ce7fda06a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rCv5ETr9ruqRRvsp0osyPA.jpeg</url>
            <title>Stories by Zuzana Andel on Medium</title>
            <link>https://medium.com/@zuzana.vojtekova?source=rss-46ce7fda06a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 06:56:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zuzana.vojtekova/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What does our HR management system look like?]]></title>
            <link>https://medium.com/inloopx/what-does-our-hr-management-system-look-like-94989a40da7b?source=rss-46ce7fda06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/94989a40da7b</guid>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[human-resource-management]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Zuzana Andel]]></dc:creator>
            <pubDate>Fri, 01 Jun 2018 07:24:19 GMT</pubDate>
            <atom:updated>2018-06-01T07:46:46.462Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B5XMVDaEtpigxBpgSXB8nA.png" /></figure><p><strong>What does our HR management system look like?</strong></p><p>Have you ever thought about creating your own HRMS ? Here in <a href="https://www.inloopx.com/">INLOOPX</a>, we created one based on <a href="https://www.atlassian.com/software/jira">Jira</a> which covers perfectly (for now) all of our needs. In this article, I would like to give you a little sneak peek into what it looks like.</p><p>We have some different boards in our HRMS which are being used by different people. That’s why this article is divided into the three parts that our HRMS covers : <strong>Hiring needs</strong>, <strong>onboarding needs</strong> and <strong>offboarding needs</strong>.</p><p>But, firstly, here is a little map, so that you will be able to imagine how the person is “moved” in our system from the beginning until the end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c1sNPJRk3dDESpUO" /></figure><p><strong>Hiring needs</strong></p><p>The first part of our system is used mainly by our <strong>hiring team. </strong>We created different boards with all of the information from the beginning of the conversation with the candidate.</p><p>All of our candidates have one issue dedicated to them. We keep the information about how this person got into our system (their personal agency, LinkedIn, referral…), and which position they applied to. As the recruiting process goes on, we change their status from <strong>Candidate</strong>, <strong>Interview,</strong> and so on, until they are <strong>Rejected</strong> or <strong>Accepted.</strong></p><p>JIRA helps us to keep our records nice and tidy, by giving us the opportunity to create a variety of boards. For example, we use the “Candidates” board (people that we are starting the conversation with)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BT2Z3KbDVA3cTPC9" /></figure><p>or “Recruiting“ board (applicants who are in an interview, doing sample app etc.).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nDUAO91OP3rXhMi1" /></figure><p>You can create any board to be suitable for your needs.</p><p><em>Hint 1 : It’s particularly useful that there are also “quick filters”, which allow you to see, for example, how many candidates you have for a certain position or which recruiter has been assigned to them (it’s also helpful for the recruiter themselves to just see their candidates).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0CyzQiJNIwCBB3OX" /></figure><p><em>Hint 2 : You can create a tab with the “date to contact” them</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/0*cPaAOt2_RHWZhxds" /></figure><p><em>and when that day comes, you can see the candidates names in the “people to contact” board.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mie8DaAofxV22rpw" /></figure><p><em>Hint 3 : The same status can be listed in more than one board, so the hiring team can just move the applicant’s name from one board to another without needing to change his status in every issue in the workflow. It’s especially useful to have the candidates “dismissed“ in some of the boards after the chosen period of time. For example, you don’t need to see the person with the “Interview“ status in the “Candidates“ board for long, since it is clearer for the whole system to have him listed in the “Recruiting“ board, after a while that he is in this state.</em></p><p><em>Hint 4 : In JIRA you can begin with a small amount of tabs and statuses, and start to add more once you know how to work with them.</em></p><p><strong>Onboarding needs</strong></p><p>The next part of our system is mainly used by our <strong>onboarding team</strong>. Once the candidate’s status changes to “Accepted“, we know that it’s time for them to start.</p><p>We do have statuses and boards here too, but they are very different to those in the recruitment project. We have only one board — “Onboarding” here. This consists of the statuses <strong>Get info, Legalities, Onboarding, </strong>and then<strong> Ready to work. </strong>We change the candidates status as the process goes on<strong>. </strong>Then we know, for example, if that employee has the contract already prepared, his hardware is ready, and so on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iIIcX25IhDEFgr9o" /></figure><p><em>Hint 1 : Create screens with tabs containing the important information you need. We use Interview, Legal, On/off-boarding, Basic info, Addition info and Education.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/808/0*yezVL5jYXh7EKpN5" /></figure><p><em>Hint 2 : As an example, here is what we keep in the “Legal” screen:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/0*cieTttQwSGSJSO-M" /></figure><p><em>Hint 3 : Use EazyBI (simple business intelligence tool (jira plugin) to create the reports that we need), and to create the “Contact list” where you´ll be able to see all the internal people and filter them according to their position, office, country etc. With this, all your employees will know who works where, in which position, and how they can be contacted.</em></p><p><strong>Offboarding needs</strong></p><p>The last one of our boards in HRMS is an <strong>“Offboarding” </strong>board<strong>.</strong> Like every company, we also need to keep track of people with whom we didn’t find the right fit with each other. We reserve the status <strong>“Terminated” </strong>for them. With this, we are able to go through and filter all the information mentioned in the onboarding process, and also keep track of when the accesses were deleted, if the termination contract was prepared/signed, when the termination date was, etc.</p><p>We hope that this small insight into our HRMS system can help you to build your own. But every company is different — so before creating your own system, we recommend that you have a lot of discussions with your leaders, back-office, finance, and of course HR, about which bits of information are crucial for them to have in the database. Then you can store and divide the right information that your people usually need to check and use for their everyday work.</p><p>Did you create your own system or are you planning to do so? Share your ideas in the discussion below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94989a40da7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inloopx/what-does-our-hr-management-system-look-like-94989a40da7b">What does our HR management system look like?</a> was originally published in <a href="https://medium.com/inloopx">INLOOPX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why did we create our own HR management system?]]></title>
            <link>https://medium.com/inloopx/why-did-we-create-our-own-hr-management-system-72538a6a2dfc?source=rss-46ce7fda06a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/72538a6a2dfc</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[jira]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[human-resource-management]]></category>
            <category><![CDATA[general]]></category>
            <dc:creator><![CDATA[Zuzana Andel]]></dc:creator>
            <pubDate>Thu, 15 Mar 2018 14:07:25 GMT</pubDate>
            <atom:updated>2018-04-18T15:17:48.975Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tmPLkTpoK8OBLOYFpCOViA.png" /></figure><p>If you google <strong>„HRMS”</strong> (Human Resources Management System or HR Management Software) you’ll get about 359 000 000 results. But how do you choose the right one for your needs?</p><p>When we were in this decision-making process at <a href="http://www.inloopx.com/">INLOOPX</a>, we found that there are three main options — <strong>to buy one, to use an open-source, or to create one</strong>. All of these options have their pros and cons, so it depends on what are your company needs. You have to consider how big it is, what other tools you use and what laws there are in your country — because not all of the systems can be used in every country given all the different privacy laws. This article is about our search for the best option, and why we decided to create our own HRMS in the end.</p><p>There are so many good HRMS across the world. If you have budget that is big enough, and you can’t create a system of your own, the best way is to buy a <strong>system that is already pre-made and working well</strong>. During our research, we found some really good ones, which can also be linked to other internal systems. You just have to choose whichever supports your company needs the best. Whether it is, for example <a href="https://www.bamboohr.com/">BambooHR</a>, <a href="https://www.hibob.com/">BobHR</a>, <a href="https://www.sap.com/index.html">SAP</a>, etc…</p><p><strong>The open-source variety</strong> is a great option if you don’t have enough money but you have people capable of developing changes in there. With these, you can also have all the information in one place. A lot of open-sources have the possibility of buying additional tools and systems, but you might also develop this sort of things yourselves. There is also a long list of options here: for example <a href="https://www.orangehrm.com/">OrangeHRM</a>, <a href="http://www.sentrifugo.com/">Sentrifugo</a>, etc…</p><p>When I came to INLOOPX, all the data was stored as a paper archive in the HQ and on excel sheets. I found out what an advantage is it to have an electronic database set directly from the start:it can grow and change together with the development of the company. But it’s quite normal to forget about this, as you are focusing on other more important things whilst starting your company. As Martin (our CEO) says : “<em>Over time you just get to the point, when accessing and managing the data becomes slow and frustrating. As programmers say: It’s time for cleanup and refactoring.</em>” At that time, when we needed information about our employees (their address, start date, salary, etc.) we had to ask our back-office every time. So, to have an “HRMS” based on excel sheets was ok while we were still a small company. But the bigger we grew the more insufficient it became. <strong>We discovered that a professional HRMS will give us more info in one place, better summary and better orientation there.</strong> And also give all the people working on it access to this information on daily basis.</p><p>Even though the decision-making process wasn’t easy, we came to the conclusion that it was necessary to create our own HRMS based on <a href="https://www.atlassian.com/software/jira">JIRA</a> This was because we wanted a tool for our superiors, back-office and HR. We didn’t need nice graphics and coloured links. <strong>We were in need of reliability and easy management.</strong> And we found out that JIRA was the most apt provider of these qualities.</p><p>Our decision was also supported by the fact, that we had already using Jira for our recruitment process. For this purpose, we had a project named Recruiting, so we extended this by several new boards, new issue types, custom fields and statuses, and thus our new shiny HRMS was born. Using this system allows us to have all the data stored from the first contact with a person right up to the end of our cooperation. The communication between the hiring and onboarding teams is much smoother now, as we just change the status to “<em>accepted</em>” and the person who takes care of onboarding knows, that their time has come :) Among other structured information we have in the HRMS, we store the salaries and full costs of our employees, which allows us to create various cost view dashboards and reports.</p><p>Currently JIRA is not only a software project management tool for us, but has over time, become a business intelligence system that we are using for our cost evidence, attendance, project management and portfolio management as well as CRM.</p><p><em>Hint : Link HRMS to your cost system, hiring tool and have it all in one place. It’s worth it! (Anytime you´ll want to create a report — Cost, Revenues, Headcount — or have a closer look at your employee’s history, you’ll find everything here and you’ll be able to connect all the systems together.)</em></p><p>Because we centralised all our business intelligence into JIRA, we began searching for a plugin that would allow us to create various dashboards and reports, and that we could utilize for our day-to-day business operations. We found <a href="https://eazybi.com/">EazyBI</a>, which is a perfect fit for our needs. With it, we can easily see how many people are working for us, where they’re working from, and any other information that we might need.</p><p>In Slovakia and within the broader EU, there is a really strict law about the protection of personal information. <strong>In JIRA, you can avoid unauthorized leakage of this confidential data</strong> by simply restricting access to only the people who need to have it.</p><p>There are currently 135+ people working for INLOOPX and JIRA has proven to be the right system for us. Maybe we´ll have to rethink and go for another option as we grow bigger. But until then, we are completely satisfied and happy to improve our own HRMS.</p><p>Which systems do you use? Share your opinions in the discussion below the article.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72538a6a2dfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/inloopx/why-did-we-create-our-own-hr-management-system-72538a6a2dfc">Why did we create our own HR management system?</a> was originally published in <a href="https://medium.com/inloopx">INLOOPX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>