> Markdown version of [/jobs/ext/2033634-senior-software-engineer-setrade](https://www.wearedevelopers.com/jobs/ext/2033634-senior-software-engineer-setrade). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer - SEtrade - **Company:** VISPIRON GmbH - **Location:** München, Germany - **Experience:** Expert - **Salary:** €70,000.0 - €100,000.0 - **Contract:** Permanent contract - **Skills:** PHP (Programming Language), Automation of Tests, Code Review, Continuous Integration, Intrusion Detection Systems, Python (Programming Language), Laravel, PostgreSQL, File Transfer Protocol (FTP), ReactJS, Git, Docker - **Published:** August 12, 2026 - **Apply:** https://www.adzuna.de/details/5836465009 ## About the Role * You've guided at least one system through a scaling leap and were the one who made the architectural decisions. Five years of professional experience is our rule of thumb, not a requirement. If you've achieved this in three years, that's just as good for us. * You've worked with time series in the billions and know what a poor partitioning scheme feels like when it's two years old. * You've built a pipeline that runs overnight without you. And you've seen what happens when it doesn't. * PHP with Laravel, React, PostgreSQL. Comparable experience in other languages counts just as much. We don't hire anyone based on a framework, and we don't fire anyone because of one. * Git, Docker, CI/CD, automated testing, observability. Craftsmanship, not just a project. * German at the C1 level or higher, because you'll be communicating with grid operators, customers, and market partners. Fluent English. * You consider a code review a gift. What we explicitly do not require A specific degree. Certificates. A minimum number of years of experience. And "energy industry" on your resume. You'll learn about direct marketing, balancing energy, balancing groups, and billing logic here in a matter of months. We won't teach you technical judgment. ## Description WHAT YOU'LL ACTUALLY BE DOING * You'll decide how our systems are structured-not in a committee, but by proposing a solution, defending it, and then implementing it. Those who make the decisions help build the system. * PostgreSQL and TimescaleDB, schedules, metrics, market data. Schema, partitioning, aggregation, query plans. If a query takes eight seconds, that's a bug for us-not a feature. * Forecasting, optimization, schedule transmission. Retry, idempotence, alerting. The standard is simple: If something goes wrong at night, no one should have to fix it manually in the morning. * Connecting systems. PV, storage, hydrogen, charging infrastructure. ModbusTCP, REST, SFTP. You'll be on the phone directly with the customer's technicians, troubleshooting the issue together instead of opening a ticket. * At the end of the month, those same time series turn into revenue. Market premiums, PPA and storage remuneration, surcharges, charging processes, GHG quotas. Grid operators submit meter readings, correct them, and resubmit them a year later. Your scripts must handle this and deliver the same result on the second run as on the first. * PHP with Laravel, React, PostgreSQL/TimescaleDB, Python. Testing, CI/CD, and monitoring are part of the implementation-not something you do afterward. * We work productively with Claude and similar tools-not just as demos. You know from your own experience where they're useful and where they produce nonsense, and you share that insight with the team. TRADING AND SETTLEMENT ARE ONE SYSTEM The time series that determines the schedule at 2:30 p.m. determines what the customer is paid at the end of the month. If the two processes yield different numbers, that's no longer a monitoring issue. The auditor will find that out. That's why, in this role, both sides are handled by a single person. Up front, speed is key; behind the scenes, reproducibility is key: A billing run must be restartable after a year with corrected network operator data and must provide a transparent explanation of why the result has changed. Versioned tariff and remuneration logic, idempotent repeat runs, clean mapping via MaLo IDs. Anyone who separates these creates two truths. ## Related Videos - [Migrating half a million users to a new payment service provider](https://www.wearedevelopers.com/videos/730-migrating-half-a-million-users-to-a-new-payment-service-provider) - [The Laravel Core - Demystify The Beast](https://www.wearedevelopers.com/videos/98-the-laravel-core-demystify-the-beast) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Navigating the Corporate Jungle: Life as a Developer in a large Company](https://www.wearedevelopers.com/videos/621-navigating-the-corporate-jungle-life-as-a-developer-in-a-large-company) - [API Platform: From Rest & GraphQL APIs to state-of-the-art standards in seconds](https://www.wearedevelopers.com/videos/1968-api-platform-from-rest-graphql-apis-to-state-of-the-art-standards-in-seconds) ## Related Articles - [Where to Find Entry-Level Software Engineering Jobs](https://www.wearedevelopers.com/magazine/397-where-to-find-entry-level-software-engineering-jobs) - [The Biggest German Tech Companies](https://www.wearedevelopers.com/magazine/424-the-biggest-german-tech-companies) - [Where To Find Software Engineering Jobs](https://www.wearedevelopers.com/magazine/396-where-to-find-software-engineering-jobs) - [System change: restart as developer?](https://www.wearedevelopers.com/magazine/39-system-change-restart-as-developer) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [How to Find Tech Jobs in Vienna](https://www.wearedevelopers.com/magazine/292-how-to-find-tech-jobs-in-vienna)