You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Gcore

Software Python Engineer (Billing)

  • Remote
  • English (B2)

Salary

Not stated

Similar roles pay €70K - 105K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The team builds and runs a billing product and needs a Python engineer to work on its back-end.

The role sits in a production team and focuses on dependable, efficient services and the architecture behind them.

Responsibilities

  • You will build and maintain efficient back-end features in Python alongside the production team.
  • You will make applications faster and more reliable.
  • You will design REST APIs and connect them to the company's solutions.
  • You will help shape architecture and design decisions aimed at an efficient distributed application and services setup.
  • You will help improve delivery pipelines and processes.

Requirements

  • You know software development principles well and understand the full software development lifecycle.
  • You are an expert in Python and have substantial experience with Django.
  • You have extensive experience with relational databases, especially Postgres, and can write, analyze and optimize SQL queries.
  • You have experience with message brokers such as RabbitMQ and asynchronous task queues such as Celery.
  • You can create and consume APIs.
  • You understand modern CI/CD practices, observability tooling and basic DevOps principles.
  • You communicate well in spoken and written English and can work remotely with a global, international team.
  • Nice to have: working knowledge of containerization and orchestration with Kubernetes.
  • Nice to have: a strong grasp of software engineering best practices, including Agile and test-driven development.
  • Nice to have: knowledge of other backend technologies and frameworks.
  • Nice to have: experience with system monitoring tools and performance optimization techniques.
  • Nice to have: a proactive approach to improving and scaling a complex system.
  • Nice to have: prior experience with billing or payment systems.

Conditions

Equal opportunity applies; the company welcomes applicants regardless of background.

Benefits

  • Competitive compensation.
  • Flexible working hours, with hybrid or remote options depending on your role.
  • Work from anywhere in the world for up to 45 days per year.
  • Private medical insurance for you and your family.
  • Extra paid vacation and sick leave days.
  • Support for important life moments and celebrations.
  • Language courses.
  • Modern offices with snacks, drinks and entertainment.
  • Team sports and social activities.

About the company

Gcore

4 of their 4 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 1 red flag

Still hiring?

13 checks

No red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation, Employment, Requirements
Tech stack
  • Python
  • SQL
  • PostgreSQL
  • Kubernetes
  • CI/CD
Type
Full-time
Specialty
Backend
Region
Europe
Pay period
Annual
Show 4 more factsShow less

Role

Category
Development
Specialty
Backend
Tech stack
  • Python
  • SQL
  • PostgreSQL
  • Kubernetes
  • CI/CD

Location

Work model
Remote
Region
Europe

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Requirements

Languages
  • English (B2)

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason