Junior Backend Developer

Planso builds AI-powered decision-intelligence products for the global architecture, engineering and construction industry. We work on complex problems involving enterprise data, documents and domain-specific reasoning. **Responsibilities** Build and maintain backend services and APIs. Develop backend logic for data processing and AI-powered applications. Work with databases, data models and backend workflows. Build integrations and APIs to support product and AI/ML capabilities. Debug issues and improve the performance and reliability of backend systems. Work closely with AI engineers, frontend engineers and domain specialists to take features into production. Write clean, maintainable and well-documented code. Contribute to technical discussions and engineering best practices. **What we are looking for** Strong programming fundamentals. Proficiency in Python, Node.js, Java, Go or a similar backend language. Understanding of REST APIs and backend development. Familiarity with SQL and relational databases. Basic understanding of data structures, algorithms and system design. Ability to work with structured and unstructured data. Strong problem-solving ability, ownership and curiosity. Relevant internship, academic or personal projects are valued. **Good to have** Experience with Python and FastAPI. Familiarity with PostgreSQL, Redis or other databases. Exposure to AWS, GCP or Azure. Familiarity with Docker and CI/CD. Exposure to AI/ML applications, LLMs or RAG systems. Experience building APIs or data-processing pipelines. **What you will gain** Experience building production-grade backend systems. Exposure to enterprise AI and complex real-world data. Opportunity to work closely with the founding and engineering teams. Significant ownership and a fast learning environment. Opportunity to work on challenging, real-world engineering problems. **Application** Share your résumé, GitHub or portfolio, and a short note about a backend project you built—including one challenge you encountered and how you addressed it.