Ljubljana, Slovenia

Staff Software Engineer

Salary: unknownStaffSoftware engineering (general)

GolangJavaJavaScriptRustSQLScalaTypeScriptPostgreSQLMongoDBRedisKafkaAWS

Original posting ↗Apply ↗Company job board ↗See this job in Telegram

Plume, a software company in real estate, construction and proptech, has an open position for Staff Software Engineer. The job is based in Ljubljana, Slovenia. We classify it under software engineering (general). The stack in the posting includes PostgreSQL, MongoDB, Redis, Kafka, AWS and GCP. Plume has 14 open positions on this site, 9 of them in IT and engineering.

Posted today · Last checked 2026-11-10

About Plume

Real estate, construction and proptech Software product company 14 open positions, 64% in IT and engineering. Most open roles: Software engineering (general) (7), Customer success and support (2), Data and machine learning (1).

All open jobs at Plume →

Similar jobs

Junior Software Engineer - DR Delivery TeamTeads · LjubljanaHybrid Infrastructure Operations EngineerJobgether · SloveniaRemote Senior Software EngineerPlanet · Ljubljana, SloveniaEUR 57.7K–72.1K / year Software EngineerPlanet · Ljubljana, SloveniaEUR 45.6K–57K / year Senior Software Engineer - Data Solutions - Privacy TeamTeads · LjubljanaHybrid SaaSOps Engineer ($80,000/year USD), @CXT SoftwareCXT Software · Slovakia | Croatia | Lithuania | Latvia | Estonia | Slovenia | GeorgiaRemote Senior Software Engineer | AI Agents & Cloud Platform (Cast Pilot team)Cast AI · Bulgaria; Croatia; Hungary; Moldova; North Macedonia; Romania; SloveniaEUR 6,500–9,000 Solutions Engineering Leadbunny.net · Ljubljana, SloveniaRemote

18 open software engineering (general) jobs in Slovenia All open jobs at Plume →

Workplace	Workplace not stated
Seniority	Staff
Role	Software engineering (general)
Countries	Slovenia
Languages	GolangJavaJavaScriptRustSQLScalaTypeScript
Key facts	Stack: Golang, Java, JavaScript, Rust, SQL, Scala, TypeScript, PostgreSQL, MongoDB, Redis, Kafka, AWS · Schedule: on-call

The full description is on the original posting. Labels are set automatically and can be wrong. About the data