Independent technical consulting

I turn complex systems into software that lasts.

Backend, cloud, and telecom engineering for teams moving from a difficult idea to reliable, deployable software.

  • BackendAPIs & systems
  • CloudKubernetes delivery
  • Telecom5G & open networks
Portrait of Panagiotis Pavlidis
Open to thoughtful collaborationsGreece · Working internationally

What I can help with

Deep engineering, shaped around your actual problem.

I connect architecture decisions to working code and dependable delivery. Engagements can be focused or span the full path to production.

01

Backend systems

Design and implementation of maintainable services, clean APIs, integration paths, automated tests, and practical ownership boundaries.

From a brittle service to a system your team can confidently evolve.

02

Cloud-native delivery

Docker, Kubernetes, Helm, and CI/CD workflows shaped around predictable releases, observability, and lower operational uncertainty.

From “works locally” to repeatable, production-ready delivery.

03

Telecom & open APIs

Standards-aware engineering across 5G Core, CAMARA open network APIs, NEF/CAPIF concepts, and reproducible network experiments.

From dense specifications to working, testable software.

04

Engineering acceleration

Practical AI-assisted workflows for exploration, implementation, testing, refactoring, documentation, and technical review.

Shorter feedback loops without compromising engineering judgment.

Selected proof

Work grounded in real systems.

Experience across production platforms, research environments, and integration-heavy systems where software quality matters.

Integrate02

Open network API environments

FastAPI services and reproducible test environments around CAMARA concepts, Open5GS, PacketRusher, NEF, and CAPIF.

  • CAMARA
  • FastAPI
  • Pytest
  • Open5GS
  • NEF
Modernize03

Backend quality & delivery

Modernization of Java systems through Spring Boot, integration tests, deployment support, and quality feedback loops.

  • Spring Boot
  • Java EE
  • Integration testing
  • CI/CD

About me

Technical depth.
Human clarity.

I’m Panagiotis, a software engineer who enjoys the hard part: finding a clear path through technical complexity.

My work sits between backend engineering, cloud delivery, and telecom systems. I help teams define sound boundaries, ship dependable services, and turn specifications or prototypes into software they can operate with confidence.

I bring an engineer’s eye for detail, a consultant’s focus on outcomes, and direct communication throughout the work.

Connect on LinkedIn ↗
CKADCertified Kubernetes Application Developer · 2024
MEngIntegrated Master in Electrical & Computer Engineering · 7.76/10
ResearchSoftware Defined Networks, ONOS, P4, and open network APIs
PublishedPeer-reviewed work on network openness and B5G/6G systems

A simple way forward

From first conversation to forward motion.

  1. 01

    Understand

    We map the goal, constraints, system context, and the decision that needs to be made.

  2. 02

    Shape

    I turn uncertainty into a focused technical plan with clear tradeoffs and useful checkpoints.

  3. 03

    Build together

    I work alongside your team, from architecture and code through testing and delivery.

BackendJava, RxJava, Spring Boot, Python, FastAPI, Java EE
PlatformDocker, Kubernetes, Helm, Linux, Jenkins, CI/CD
Data & APIsCassandra, MongoDB, REST, YANG, Microservices
Telecom5G Core, CAMARA, NEF, CAPIF, Open5GS, B5G/6G

Before we talk

Common questions, clear answers.

What kind of projects are a good fit?

Backend, API, cloud, platform, and integration work where reliability and maintainability matter. I am particularly useful when a team needs both architecture thinking and hands-on implementation.

Do you only work in telecom?

No. Telecom is a specialist advantage, not a boundary. The core work—backend services, APIs, cloud delivery, testing, and integration—applies across technical products and industries.

Can you join an existing engineering team?

Yes. I can own a defined technical outcome, support a delivery phase, or work alongside an existing team to unblock architecture, implementation, testing, or deployment.

What should I include in my first message?

A short description of the idea or problem, where the project stands today, the main constraint, and what a useful outcome would look like. Early ideas are welcome.

Start a conversation

Have an idea worth building well?

Tell me what you are exploring. You do not need a polished brief—just enough context to start a useful conversation.

This opens your email app with your message ready to send. Your details are not stored by this website.