Brno Hat

Jiri Eischmann's Blog

Hiring for Flatpak Automation

,
, ,

The desktop team in Red Hat has another open position. We’re looking for someone to work on Flatpak automation, for someone who enjoys working on infrastructure. Although the job description states 2+ years of experience, it’s suitable for juniors. Formal experience can be replaced by relevant open source contributions. Being onsite in Brno, Czech Republic is preferred, but not required. We’re open to hiring good candidates elsewhere, too.

If you’d like to know more about the job before formally applying, don’t hesitate to contact me on Mastodon, Signal, Matrix (@eischmann at fedora.im), or email.

10 responses to “Hiring for Flatpak Automation”

  1. Adil Arif Avatar
    Adil Arif

    @brnohat Wahoo! Is this a net new position on the desktop team or a backfill? If it is a net new, it will probably be the biggest news of the year that Red Hat is growing the desktop team.

  2. lebout2canap ⏚ Avatar
    lebout2canap ⏚

    @brnohat I quickly read the job offer, and it didn’t seem to me that there was the answer to the following question: when you talk about “Flatpak automation”, do you talk about the possibility of automating the installation of flatpaks on an entire computer park (with the building of versions customized by the administrator), or is it a question of improving all the building process of Red Hat’s Flatpak repository?

    1. Jiří Eischmann Avatar
      Jiří Eischmann

      @lebout2canap @brnohat it's mostly, but not solely about the build pipeline for flatpaks we use in RHEL.

      1. lebout2canap ⏚ Avatar
        lebout2canap ⏚

        @sesivany Ok, thanks for the answer.

        @brnohat

  3. James Just James Avatar
    James Just James

    @brnohat For the infra aspects would you be willing to use https://github.com/purpleidea/mgmt/ or is it forced to use Ansible/Kube/Terraform?

    1. Jiří Eischmann Avatar
      Jiří Eischmann

      @purpleidea @brnohat we as a team have to use what Red Hat infra uses, this isn't really in our control.

  4. Kevin Karhan :verified: Avatar
    Kevin Karhan :verified:

    @brnohat @sesivany #remite candidates from within the #EU are welcome, I guess?

    #Relocation may not be an option for most andd seems quite unnecessary given the nature of #SoftwareDevelopment!

    1. Jiří Eischmann Avatar
      Jiří Eischmann

      @kkarhan @brnohat onsite is preferred (it's a company policy to rebuild site communities), but not required. However, the budget for the position is for the Czech Republic which makes it really difficult to meet demands of candidates from high income locations.

      1. Kevin Karhan :verified: Avatar
        Kevin Karhan :verified:

        @sesivany @brnohat onsite would be a clear no-go for anyone I know who’s even remotely talented, even if they were within communting distance.

        Corporations forcing people to socialize is cringe af. Either one has a good culture and people want come together or not.

        Not to mention it’s ableist af to any non-neurotypical or disabled person.

        This ain’t like TechSupport onsite at clients’ datacenters or plumbing where it makes sense to have personnel onsite to be able to reach clients AFAP.

        It’s not a matter of money either. I did reject a position paying 50% higher… All I’d care is getting legally employed under German law for healthcare and tax reasons.

        Still wishing only the best of luck and success at filling said vacancy!

        1. Jiří Eischmann Avatar
          Jiří Eischmann

          @kkarhan @brnohat I understand, but the policy isn't something I can directly influence. However, it's a very soft preference. Our engineering has always been very distributed with many people working remotely, especially the desktop team where most people work remotely. I don't think it's a major obstacle. If we have two very similarly qualified candidates, we may prefer the one who can be in Brno, otherwise we'd just pick the better one no matter where they work from.

Leave a Reply

Your email address will not be published. Required fields are marked *