Work With Us: Developer Jobs in Bologna

What the work at Codebaker actually looks like

Codebaker was founded in Bologna in July 2019 and works almost exclusively with local SMEs: manufacturing, logistics, food production. That shapes the work far more than the technology stack does. Projects do not start from a specification written by someone else: they start from going to the company, seeing how people actually work and understanding which part of that work makes sense to hand to software. People here spend part of their time talking to production managers and warehouse staff, not only to other developers.

The practical consequence is that you see the effect of what you write. Teams are small, the path from analysis to release is short, and whoever built a feature is usually the one who hears back from its users. That is the flip side of working on our own products and direct engagements rather than subcontracting on isolated pieces of someone else's project. How we work in practice is described in our software development method, and the projects already delivered are collected in the portfolio.

It is worth saying what we are not, so you can avoid a pointless interview: we are not a large organisation with codified career tracks and teams dedicated to a single component. You work across several things, you will sometimes touch a legacy system written twenty years ago, and the organisation is that of a small team. Some people find that far too constraining; others find it is exactly what they were looking for.

stack and areas of work

Web and mobile

Frontend with React, Next.js and TypeScript; backend with Node.js, Python and REST and GraphQL APIs. On mobile we work both native — Kotlin and Swift — and cross-platform with Flutter and React Native, choosing case by case rather than on principle.

Cloud, DevOps and infrastructure

Docker, Kubernetes and Talos OS, CI/CD pipelines with TeamCity and Fastlane, infrastructure on European cloud. This is the area with the most room for people who want to get their hands on the infrastructure as well as the application.

IoT, integrations and AI

IoT and Industry 4.0 projects with data coming from real machinery, integrations with business systems and ERPs — including work on legacy systems such as AS400 — and AI solutions on company data. These are the areas where the problem is rarely just about code.

Open positions and speculative applications

There are currently no published openings

We would rather not keep adverts online that do not correspond to a real search. Speculative applications, however, remain the most common route into Codebaker: we are a small team and needs usually arise right before a project starts, so having a profile already under consideration counts for more than waiting for the right advert. Write to info@codebaker.it attaching your CV and a couple of lines about what you would like to work on.

How the hiring process works

Introductory call: half an hour to understand what you are looking for and to tell you what the company is really like, awkward parts included.
Technical interview with your future colleagues: it starts from what you have actually done — a project, a problem you solved, a decision you are not convinced by — not from memorised quiz questions.
Final meeting on terms and expectations: contract, working arrangements and mutual expectations, put on the table before any decision is made.

We give feedback after every step, including when it is negative. If we are interested but have no immediate opening, we say so openly instead of letting the conversation lapse.

Location and working arrangements

The office is in Bologna, at Via N. Corazza 7/8, and part of the work happens there or at client sites: many projects start from directly observing processes inside the company, and that part is hard to do remotely. Remote work is a normal part of the week; the exact balance is agreed during the interview, depending on the role and the projects involved. To get to know the team and the company's history, the page to read is about us.

Frequently asked questions about applying to Codebaker

How do I apply if there are no published openings?

Write to info@codebaker.it with your CV and a couple of lines about what you would like to work on. Speculative applications are the most common route into Codebaker: we are a small team and needs usually arise right before a project starts, so having a profile already under consideration counts for more than waiting for the right advert. If your profile is interesting but there is no immediate opening, we say so openly rather than letting the conversation lapse.

What does the hiring process look like?

The process is short and free of pointless steps: an initial introductory call, a technical interview with the people you would actually work with, and a final meeting about terms and mutual expectations. The technical interview starts from what you have actually done — a project, a problem you solved, a decision you are not convinced by — not from memorised quiz questions. We give feedback after every step, including when it is negative.

Is the work on-site in Bologna or remote?

The office is in Bologna, at Via N. Corazza 7/8, and part of the work happens there: many projects start from directly observing processes at the client's premises, and that part is hard to do remotely. Remote work is a normal part of the week; the exact balance is agreed during the interview, depending on the role and the projects involved.

What technologies do you work with?

On the frontend React, Next.js and TypeScript; on the backend Node.js, Python and REST and GraphQL APIs; on mobile Kotlin, Swift and Flutter; on infrastructure Docker, Kubernetes, Talos OS and CI/CD pipelines with TeamCity and Fastlane. On top of that there are IoT and industrial projects and integrations with business systems and ERPs, including work on legacy systems such as AS400. Nobody is expected to cover all of it: you come in from wherever you are strongest.

Send us your application

Write to info@codebaker.it attaching your CV and a couple of lines about what you would like to work on and the kind of problems you enjoy. We read every application and reply even when the answer is no.