Backend Engineer - Tracking Team

As a Backend Engineer in the Tracking Team at InPost Group, your primary responsibilities include designing, building, testing, and maintaining high-performance microservices in Java. You will work with a variety of modern technologies to improve shipment tracking capabilities, ensuring a seamless experience for customers and partners. Collaborating with other engineering teams and advocating for quality and innovation in development practices are also key parts of your role.

To qualify for the Backend Engineer position at InPost Group, candidates should hold a degree in computer science or a related field, or possess at least 4 years of relevant experience. Proficiency in Java and experience with frameworks like Spring Boot are essential, along with familiarity in designing data structures and developing microservices. Knowledge of containerization (Docker, Kubernetes) and cloud-based infrastructure (GCP) is also important.

In the Backend Engineer role at InPost Group, you'll work primarily with Java and Spring Boot for backend development. Additionally, you'll engage with modern technologies such as Docker, Kubernetes, Firestore, Kafka, and Google Cloud Platform. Your role will involve building and maintaining cloud-based, highly scalable applications, so familiarity with these tools and technologies is crucial.

The team culture for Backend Engineers at InPost Group is collaborative and innovative. You'll be part of an international team where knowledge sharing and cross-functional collaboration are encouraged. The company emphasizes quality and good development practices, creating an environment where engineers can thrive and advocate for improved engineering principles and innovation in the work they do.

Yes, InPost Group allows for flexible work arrangements. As a Backend Engineer, you have the option to work from the office in Kraków or remotely, providing you with the flexibility to choose the working environment that suits you best.

In a microservices architecture, I emphasize principles like loose coupling, single responsibility, and independent deployment. I also advocate for proper API design, ensuring that services are decoupled from one another, which facilitates scalability and maintainability. Providing clear documentation for each microservice is also crucial for team collaboration.

I have hands-on experience with Google Cloud Platform, utilizing its services for developing and deploying applications. I've specifically worked with GCP tools like Firestore for real-time data handling and Kubernetes for managing containerized applications efficiently. My experience also includes implementing CI/CD pipelines within GCP.

Ensuring code quality is a multi-step process for me. I use code reviews and automated testing practices such as unit and integration tests to catch issues early. Additionally, I follow best practices like writing clean, maintainable code and using tools such as Sonar to monitor code quality metrics continuously.

To handle failures in microservices effectively, I implement strategies like circuit breakers, retries with exponential backoff, and thorough logging to monitor service health. I also prioritize redundancy and graceful degradation of services to minimize the impact of failures on end users.

I have significant experience with containerization, particularly using Docker to create and manage containers for applications. This experience includes writing Dockerfiles, using Docker Compose for local development, and deploying containerized applications on Kubernetes clusters, ensuring robust scaling and portability throughout the development process.

I make it a point to stay updated with new technologies by following tech news, participating in webinars, and engaging with online communities. I also dedicate time to explore new frameworks and tools through personal projects and contribute to open-source projects, which helps keep my skills sharp and informed.

I am very comfortable with Agile development methodologies, having worked in Agile environments extensively. I value iterative development and regular feedback, which helps refine features and fixes throughout the project lifecycle. I also believe in the importance of daily stand-ups and sprint retrospectives to maintain team alignment and continuous improvement.

To prioritize tasks in a fast-paced environment, I assess project goals and deadlines while considering dependencies between tasks. I often use project management tools for visibility and transparency, which allows me to focus on high-impact tasks and allocate my time accordingly while remaining flexible to adapt as priorities shift.

My biggest challenge in backend development was integrating a new microservice with legacy systems. This required a thorough analysis of existing APIs and a well-documented plan for gradual migration. By implementing thorough testing and monitoring during the transition, I was able to minimize downtime and ensure a smooth integration.

When designing APIs for microservices, I consider usability, clear documentation, and efficient communication between services. I also follow RESTful principles, ensuring that my APIs are predictable and follow the core CRUD operations. Additionally, I prioritize security and performance to ensure a robust API lifecycle.