Pre zobrazenie detailov spoločnosti je potrebné prihlásenieVyčerpali ste limit zobrazení spoločností. pre neobmedzený prístup.
Pracovné ponuky vychádzajú z reálnych inzerátov, ich štruktúru a požiadavky však zjednocujeme pomocou umelej inteligencie (AI). Občas tak môže vzniknúť drobná nepresnosť spôsobená AI alebo nejasným zadaním v pôvodnom inzeráte. Pri odpovedi sa, prosím, držte celkového zmyslu ponuky a reagujte čo najkonkrétnejšie.
Odporučte konkrétneho kandidáta alebo zdieľajte tento inzerát. Vyberte si spôsob a odmena je Vaša.
CandiDating je súčasťou personálnej agentúry Synerta Personnel, ktorá už takmer 15 rokov spája talenty s príležitosťami.Odporučte konkrétneho kandidáta alebo zdieľajte tento inzerát. Vyberte si spôsob a odmena je Vaša.
From 5 000 EUR/month
Information about the position
Job description, responsibilities and duties
Specialized Infrastructure as a Service solutions are delivered for organizations where performance, scalability, and reliable execution are essential. Deep infrastructure expertise contributes to a broader cloud technology organization serving businesses worldwide.
The platform provides compute, storage, and networking services across multiple regions, with access to premium server hosting solutions in more than 26 data centers globally. It supports leading enterprises and high-growth companies across industries including Big Data, AdTech, FinTech, Gaming, iGaming, Blockchain, and Streaming.
Overview
Cloud Services delivers data protection, security, and edge services — SSL, email, EADN, and CDN/WAF — that keep customers’ applications safe and performant.
You will own features end to end: the specification, the code, the tests and how it behaves in production. This is an individual contributor role with no direct reports, and you are the engineer who answers for whether what you shipped actually works.
The pull request is the visible part. The job is the machine behind it: turning a loosely worded need into something precise enough to build against, naming what can break before it does, proving the change is correct rather than asserting it, and staying with it once it is live.
Business alignment and focus come first.
Engineering here exists to move the business, not to be busy. You will know which few things matter most this month and why, say so when the work in front of you is not one of them, and land what you committed to on dates the business can plan around, at a quality that does not come back as an incident or a customer escalation.
Predictable, reliable delivery of quality software is the output of this job, and everything below is in service of it.
This job gets more hands-on every quarter, not less. The volume of code goes up while the time you spend typing it goes down, so the value moves to the two ends of it: what you specify, and what you verify. You will stay close to production, run the AI harness daily, read code you did not write, and keep your technical judgment current rather than remembered.
Whoever ships it owns it, regardless of what wrote it. Most code is AI-generated now, so the judgment moved to either side of it: specifying exactly what to build, and verifying that what came back is correct, secure and operable. An agent wrote it is not a defense. Your name is on the merge.
You do not need to own the roadmap to know why the work matters. You will not be the Product counterpart at this level and you are not expected to be. You are expected to understand what the customer gets and what the business gains from the thing you are building, and to ask before you build the wrong thing correctly.
You go on call for what you build, and you take your turn on the rotation. Engineering declares risk and timelines in writing for the business to accept, and that includes yours: when a date is at risk you say so early, with evidence, rather than quietly.