Senior Software Engineer - Local Server Systems
⚲ Kraków
26 880 - 31 920 PLN (B2B)
Wymagania
- Python
- VMware
- Documentation skills
- Java (nice to have)
- SRE (nice to have)
- DevOps (nice to have)
- Hardware (nice to have)
- AWS (nice to have)
Opis stanowiska
O projekcie:
Our solutions run in the cloud and connect to our devices (tags and gateways). But for safety-critical solutions — we need software that works all the time, even when connectivity to our cloud drops. This role owns that Local Server: software that runs on-site and keeps these systems running independent of cloud connectivity.
Key difference from typical cloud engineering: we don't have remote access to the hospital's machine once it's deployed. You have to get it right up front, because troubleshooting after the fact means working from logs and documentation, not a terminal.
Wymagania:
What You Have:
- Senior-level experience, ideally full-stack, with hands-on work deploying and managing services in remote containers- Comfort with Python or Java (Python preferred, either is fine)- Working knowledge of both containers and VMs- Strong documentation skills- Comfort operating with limited visibility and control over the deployment environment
Bonus Points if You Have:
- Hardware exposure (even hobbyist), - Background at a company with embedded or on-prem deployment patterns, - Basic SRE and/or networking experience, - AWS familiarity.
Codzienne zadania:
- You'll build the Local Server as a bridge between our cloud and on-site devices, replicating just enough cloud logic locally to keep safety-critical features running offline
- Package it as a container (standard) or VM (some hospital customers require VMs specifically)
- Build in strong self-reporting (logs, health metrics) so issues can be diagnosed remotely
- Write clear, detailed documentation — hospital IT installs and operates this using only what you write
- Coordinate with the engineer owning the cloud-side app to keep feature parity between what works online and what works offline
Our solutions run in the cloud and connect to our devices (tags and gateways). But for safety-critical solutions — we need software that works all the time, even when connectivity to our cloud drops. This role owns that Local Server: software that runs on-site and keeps these systems running independent of cloud connectivity.
Key difference from typical cloud engineering: we don't have remote access to the hospital's machine once it's deployed. You have to get it right up front, because troubleshooting after the fact means working from logs and documentation, not a terminal.
Wymagania:
What You Have:
- Senior-level experience, ideally full-stack, with hands-on work deploying and managing services in remote containers- Comfort with Python or Java (Python preferred, either is fine)- Working knowledge of both containers and VMs- Strong documentation skills- Comfort operating with limited visibility and control over the deployment environment
Bonus Points if You Have:
- Hardware exposure (even hobbyist), - Background at a company with embedded or on-prem deployment patterns, - Basic SRE and/or networking experience, - AWS familiarity.
Codzienne zadania:
- You'll build the Local Server as a bridge between our cloud and on-site devices, replicating just enough cloud logic locally to keep safety-critical features running offline
- Package it as a container (standard) or VM (some hospital customers require VMs specifically)
- Build in strong self-reporting (logs, health metrics) so issues can be diagnosed remotely
- Write clear, detailed documentation — hospital IT installs and operates this using only what you write
- Coordinate with the engineer owning the cloud-side app to keep feature parity between what works online and what works offline
🔍 Dekoder Ogłoszenia
🔴
You have to get it right up front, because troubleshooting after the fact means working from logs and documentation, not a terminal.
Oznacza to, że będziesz miał bardzo ograniczony dostęp do rozwiązywania problemów na miejscu, co wymaga dużej precyzji i przewidywania błędów.
🔴
Comfort operating with limited visibility and control over the deployment environment
Będziesz musiał radzić sobie z sytuacją, w której nie masz pełnego wglądu ani kontroli nad tym, jak i gdzie Twoje oprogramowanie jest uruchamiane.
🟡
Package it as a container (standard) or VM (some hospital customers require VMs specifically)
Może to oznaczać, że będziesz musiał pracować z różnymi technologiami wirtualizacji i kontenerów, w zależności od specyficznych wymagań klientów.
🟡
Build in strong self-reporting (logs, hea
Wymaga to od Ciebie zaprojektowania systemu, który będzie samodzielnie raportował problemy, co jest kluczowe przy braku zdalnego dostępu.
🔴
Key difference from typical cloud engineering: we don't have remote access to the hospital's machine once it's deployed.
Podkreśla to unikalność roli i potencjalne wyzwania związane z brakiem możliwości zdalnego zarządzania i debugowania wdrożonych systemów.