Scala Engineer

You will:
• Write actually functional code in 2025–2026 without apologizing for it
• Treat EitherT[IO, DomainError, HappyPath] like a normal Tuesday
• Not write 47-line for-comprehensions that could be 3 lines of .map + .flatMap + .recoverWith
• Understand that tagless-final is not a personality trait (but we still want you to know how & when to use it)
• Stop saying „but in Java we did it this way“ in every single PR

You probably should be comfortable with at least 4 of these without googling:
• Cats / Cats-Effect 3 / FS2
• Http4s + Circe / Tapir + Iron / ZIO + zio-json
• Typelevel programming that doesn't make the team hate you
• Tagless Final vs Free vs MTL vs whatever new flavour-of-the-month algebra appeared last month
• Testing that isn't just „it compiles therefore it's correct“
• Not deploying config-drift hand grenades to production

Bonus points if you can:
• Explain variance without crying
• Write a lawful typeclass instance in under 8 minutes
• Say „this should be a profunctor“ in a room and not get punched
• Survive a 2-hour debate about whether ReaderT is still cool in 2026

We offer:
• Real money (not startup funny money)
• People who actually read & comment on PRs
• No Jira points attached to your soul
• The sacred right to say „no, we are not rewriting this in Rust / Go / TypeScript“
• A non-toxic amount of Scala in your life