AVSYSTEM
AVSYSTEM

Integration Software Engineer

Why should you join us?

AVSystem is the company behind the Unified Management Platform (UMP) – a solution used by Tier-1 telecom operators such as Orange, Vodafone, AT&T and T-Mobile. Our software enables automatic configuration, upgrades and monitoring of millions of routers worldwide.

This role has real impact. You won’t be building internal tools or proof-of-concepts — you’ll deliver solutions that run in production environments at global scale.

As an Integration Software Engineer, you will:

  • combine software engineering with real networking environments,
  • work directly with customers and see the results of your work,
  • develop expertise at the intersection of backend development, integrations and networking,
  • collaborate closely with domain experts (Senior Engineers, Product Owners, Solution Architects) from the very beginning,
  • learn and use our Scala-based functional DSL designed for large-scale device management.

This role is a strong fit if you want to:

  • understand systems end-to-end
  • take ownership of production-grade integrations
  • grow toward Solution Architecture, system integrations, or telecom/IoT domains

What does the day-to-day work look like?

Your work combines development, system integration and project collaboration

In practice, you will:

  • write project-specific code (Python and our in-house functional language)
  • implement and integrate REST APIs (both client and server side)
  • configure UMP for specific customer deployments
  • work with routers and external systems
  • analyze logs and troubleshoot issues (Linux CLI, tcpdump, curl, ssh)
  • collaborate with Solution Architects and Software Engineers (including code reviews)
  • support your integrations after delivery together with 1st and 2nd line support teams

Work distribution typically looks like:

  • 40–50% development and configuration
  • 30–40% integrations and troubleshooting
  • 10–20% direct customer communication (calls, emails, support portal)

The pace can be project-driven — especially around delivery milestones

Who is this role NOT for?

You may not enjoy this role if:

  • you prefer pure backend development with no customer interaction
  • you don’t like troubleshooting production issues and analyzing logs
  • you’re uncomfortable taking responsibility for live system integrations
  • you’re looking for a fully remote role (Kraków onsite / hybrid preferred)
  • networking topics (IP, TCP/UDP, firewalls, SNMP) don’t interest you
  • you expect close managerial guidance and step-by-step instructions

This team operates with a high level of autonomy. There is no micromanagement here — and no one will “hold your hand.”

From the beginning, you’ll be expected to:

  • take ownership of your integrations
  • manage your work independently
  • proactively seek information and solutions
  • understand the purpose behind what you’re building — not just execute tasks

If you thrive in environments with strong structure, constant supervision and clearly predefined paths, this may not be the right fit

But if you value autonomy, ownership and understanding the bigger picture — you’ll likely feel at home!

What do you need to succeed?

  • Strong programming skills (Python preferred)
  • Experience with REST APIs (client and/or server side)
  • Understanding of networking fundamentals (HTTP(S), TCP/IP, WLAN, firewalls)
  • Basic Linux administration skills (log analysis, CLI tools, ssh, tcpdump)
  • English proficiency (B2/C1)
  • Willingness to learn our Scala-based functional DSL

Nice to have:

  • Professional experience as a Software Engineer
  • Experience in multi-system integration environments
  • Telecom domain exposure (ACS, NMS, OSS, BSS)

What does the recruitment process look like?

  1. Intro video-call with HR (45 min) – expectations, background, role context + basic technical check
  2. Technical and managerial interview [combined] (~3h) – programming, APIs, networking fundamentals + project discussion and working style
  3. Final decision and feedback

The whole process usually takes 2–3 weeks