The role
Build the systems around the model.
Pexon Romania is hiring a software engineer in Cluj-Napoca to build the services behind its AI work: Python and Java backends, API integrations into ERP and MES systems, and the retrieval pipelines a company brain runs on. The role needs at least three years of backend or full-stack experience. Jobs are based at the Cluj office.
The work
Three problems you will make work.
Retrieval
Answers grounded in the right documents
Manuals and engineering drawings arrive with conflicting revisions and different access rights.
- Your part
- Build ingestion and permission-aware retrieval pipelines.
- The outcome
- Answers cite the source revision and respect who can read it.
Explore company brain engineering ↗Integration
A reliable way into industrial systems
ERP, MES and PLM systems differ by plant and cannot simply stop during a shift.
- Your part
- Build APIs, service contracts and tests in Python or Java.
- The outcome
- A dependable interface between the model and the customer's systems.
Explore the data foundation ↗Serving
The gateway around inference
An upstream model can become slow, expensive or unavailable.
- Your part
- Build routing, caching, quotas and audit logging.
- The outcome
- A service whose behaviour can be understood and operated in production.
Explore enterprise model rollouts ↗What you bring
A production mindset. Solid foundations.
- ✓
Production experience
At least three years in backend or full-stack engineering, with a system you can discuss in detail.
- ✓
Python or Java in depth
Strong in one and comfortable reading the other. Customer systems shape the stack.
- ✓
Cloud and containers
Working experience with AWS, Azure or Google Cloud, and Docker.
- ✓
Data and delivery
Relational and non-relational databases, plus CI/CD with GitLab CI, GitHub Actions or Jenkins.
- ✓
Technical English
Comfort discussing requirements and trade-offs directly with customer engineers.
Room to grow
What you can learn here.
- Production retrieval and model gateways
- The customer's industrial systems and domain
- Kubernetes alongside the platform engineer
You do not need a machine-learning research background or a particular degree. German is helpful, but English is the working requirement.

A person behind the process
Meet Laura Picovici.
HR Business Partner · Recruiting
Laura runs recruiting for the Cluj hub. Your application reaches her first, she answers your questions about the process and the range, and she brings in the engineers you would actually work with. Later in the process you also meet Noel Dinger, who runs the company.
Meet the people behind Pexon ↗The conversation
A clear path from hello to a decision.
- 01
Introduce yourself
Share something you have built or operated. Your message reaches Laura Picovici, who runs recruiting for the hub.
- 02
Talk engineering
A 30–60 minute first conversation about your work and what you want next. Ask for the salary range by email beforehand.
- 03
Work through a problem
A practical session together, inside working hours. No weekend take-home assignment.
- 04
Meet the hub
Talk with Noel Dinger about the company and what you would own.
- 05
Get a decision
A yes or a no, with a reason. After a technical session, feedback addresses the work discussed.
The practical questions.
Where is the role based, and what is the office schedule?
The role is based at the Cluj-Napoca office. The team is built around people who can work there together. Discuss the current office schedule in the first conversation; this is not a remote-first role.
Can I ask for the salary range before a call?
Yes. Ask in your application email and the range will be shared in the reply, before a technical session. The email preparation form includes an optional request for the range so you can raise it from the start.
Is this an AI research role?
No. Nothing in this job trains a model or evaluates an architecture on a benchmark. The work is the system around the model: the retrieval pipeline, the integration into an ERP, the service that has to answer while the source system is having a bad day. The focus is applied engineering and making the surrounding systems work.
Which languages and stack will I actually use?
Python and Java are the two that recur, on cloud infrastructure the customer already runs, which in practice means AWS, Azure or Google Cloud with containers on top. The retrieval and gateway work is mostly Python. The integration work is wherever the customer's system already lives, and that is sometimes neither.
How much of the job is customer-facing?
Enough that you need to be able to run a technical conversation in English without a manager in the middle. Forward deployed means you sit inside the customer's environment and next to their engineers, so requirements arrive in conversation rather than as tickets from a product owner you never meet.
What does the technical session involve?
A real problem of the kind the job contains, worked through with the people you would work with. There is no whiteboard algorithm round and no take-home task that expects a weekend of unpaid work. You will be asked what you would do when the data source is wrong, because that is most of the job.