Blog

12.08.2021. | Autor: Melissa Pürstinger

Company insights – the teams behind JIT

If you’re an attentive reader of our blog posts you might have already noticed that the topics and projects the people of JIT are working on are quite diverse. We are an IT company that is successfully covering more than one area and that is only possible because of the vibrant and motivated teams behind our projects. But who are those teams and how are they adding value to the company? In the following weeks, you will get a glimpse of the faces of JIT including their day-to-day challenges and achievements. But let’s start with a general introduction. 

JIT has seven teams at the moment. Each of them covering different areas. Of course, some teams are working closer together than others but overall it’s like a big diverse family. 

1. OE Department

If you are familiar with company structures you might already know that OE stands for operational excellence. So basically it is the part of the company that makes sure operations work in an excellent way. They take over our resource planning and are involved in the process of gathering new clients. But mostly they are responsible for the management of projects, quality, and customers. Our OE department is providing the structure for successful work life. 

2. Backoffice Team 

Aside from the OE department, the team in our back office is also an essential part of providing structure in the day-to-day life of JIT. Invoice management and making sure project booking works smoothly are just snippets of the broad range of tasks our Backoffice Team is taking over. But also planning of events, providing the teams with the needed computer hardware, and checking on the work environment are areas our Backoffice Team is actively participating in.

3. Microservice Team

Next up is our Microservice Team. Consisting of two groups with the very promising names of Bugbusters and Kamikatzen. As the main team name suggests they are responsible for microservice development. Another important task is their handling of legacy applications support. Aside from that, they take care of TMA (T-Mobile Austria) support. Our Microservice Team especially works together with some of our newer clients but if you are curious about that just stay put for the follow-up blog posts where we dive a little deeper into the teams. 

4. Database Team

The Database Team – again the name kind of spoils their main area of work. These guys and girl(s) work on various databases. Not only JIT internally but also for our clients. And what would an IT company be without proper database handling? But more on that soon. 

5. Middleware Team

The members of our Middleware Team are confronted with TMA (T-Mobile Austria) quite a lot. They are not only developing TMA middleware but also TMA internal Camunda applications. This team is a mix of JIT internal and specific TMA members. Therefore they are kind of self-independent.

6. Camunda Team

Since Camunda plays such a big role in the life of JIT there is a specific team for that as well. As this team is kind of under construction right now the name is not set yet. They can also be seen as a construction team after all. Why? Because their work areas consist of (internal) Camunda training, developing plus consulting, integration workshops proof of concept + value (POC/POV), and general client support. But will we decide on a final team name? We will keep you updated, blog post following 😉

7. Gustaffo Team

JIT has a little sister and her name is Gustaffo. Gustaffo is a digital concierge providing hotels with modern check-in and check-out systems and making hotel day-to-day life easier for the staff(o) and guests. A part of the JIT members is very involved in these processes and we will introduce them to you very soon. 

We hope this little insight made you curious for more information about our teams because you have the opportunity to get to know them better here in our blog!

Melissa Pürstinger
Back Office Assistant

Photo by Headway on Unsplash

Weitere Blog

10.09.2021.

BPMN Error Handling Mechanism – Dealing with many errors in a process

Autor: Gerardo Manzano

Errors are inherently part of software development. They can happen because of several reasons. One common definition of a software error is a mismatch between the program and its specification. In other words, we can say, a program has an error when the program does not do what the end-user expects. In this blog post, […]

Blog lesen
29.07.2021.

Ruby external task worker

Autor: Maximilian Kamenicky

“The value of a system is often defined by how well it integrates with other systems” The best software is limited if you cannot integrate it with existing frameworks. In the case of Camunda, this fact is all the more true. Imagine a workflow automation engine without a way to interact with the existing software. […]

Blog lesen
15.07.2021.

REST Schnittstelle von Camunda Plattform in External Java Service Tasks aufrufen

Autor: Maximilian Kamenicky

Erfahren Sie mehr darüber, wie man mit Camunda REST-Webservices aufrufen und nutzen kann. In dieser Blog-Serie zeigt Ihnen unser Experte zwei unterschiedliche Möglichkeiten um dieses Ziel zu erreichen.Der erste Beitrag (REST Schnittstelle von Camunda Plattform via Java Service Task aufrufen) hat gezeigt wie dies über Java Service Tasks geht. Wie man dies über externe Services […]

Blog lesen