DEVOPS MINDED ENGINEER
Ysoftcorporation·Anywhere within commuting distance of Brno, Ostrava
mid
Sign in to applyFree account, takes a minute.
Job description
<p><strong>We are building a new R&D team focused on cross-cutting infrastructure challenges such as cloud governance, security, disaster recovery, operational readiness and cost visibility. This isn't a classic DevOps role - we're looking for someone who codes, not just configures, and treats infrastructure as something you build, test and maintain like any other software.</strong></p>
<p>If you'd like to work remotely, no problem - but it helps if you're within driving distance of Brno or Ostrava. The team likes to meet up in person from time to time.</p>
<h2>WHAT WE OFFER</h2>
<ul>
<li><strong>Systemic impact.</strong> What you build here doesn't serve one team - it becomes the pattern other teams rely on.</li>
<li><strong>Real ownership without being a bottleneck.</strong> You'll solve production-grade infrastructure problems, not gatekeep other teams' changes.</li>
<li><strong>A manager-less structure.</strong> No micromanagement, no status pyramids.</li>
<li><strong>A team that decides and owns what it builds </strong>- including hiring and promotions.</li>
<li style="font-weight: bold;"><strong>No bulls**t KPIs.</strong></li>
<li>Learning and knowledge sharing is part of the job, not a side activity.</li>
</ul>
<h2>WHAT YOU'LL WORK ON</h2>
<ul>
<li>Infrastructure is a shared R&D responsibility - any R&D team can propose and implement changes across the stack, including Terraform modules, cloud environments, account foundations and future landing zones.</li>
<li>You'll independently analyse production infrastructure problems and deliver safe changes in your area of expertise.</li>
<li>Broader architecture and cross-platform decisions are made collaboratively - you won't be expected to redesign or own the entire infrastructure alone.</li>
<li>Your focus: solving systemic problems together with other teams and turning working solutions into reusable patterns, automation and documented practices - not becoming the approval gate for everyone else's changes.</li>
</ul>
<h2>WHAT WE EXPECT FROM YOU</h2>
<ul>
<li>A strong mid-level to senior infrastructure engineer profile, with a <strong>developer mindset and development experience</strong>.</li>
<li>Strong practical experience with <strong>at least two</strong> of: <strong>AWS, Azure, GCP/Kubernetes, Terraform/OpenTofu</strong>.</li>
<li>The ability to write maintainable automation and infrastructure code.</li>
<li>Developer habits: <strong>testing, code review, versioning, CI/CD, validation and rollback</strong>.</li>
<li>A solid understanding of <strong>Linux, IAM/RBAC, networking and infrastructure security.</strong></li>
<li>The ability to work across repositories and teams, document decisions and share knowledge.</li>
<li>Fluent Czech + English at a conversational/working level (at least B2)</li>
</ul>
<p>NICE TO HAVE</p>
<ul>
<li>AWS Organizations, IAM Identity Center</li>
<li>GitOps</li>
<li>Disaster recovery, observability, FinOps</li>
<li>OpenStack/OTC or other compliance-driven infrastructure</li>
</ul>
<p> </p>
<p><strong>No one is expected to be an expert in every area from day one.</strong></p>
<p><strong>If this sounds like your kind of work, let's talk.</strong></p>