My workplace is migrating from Ruby/Rails to Java/Spring but I really dislike Java

Backend
1

UPDATE: Just to clarify, I have experience with multiple programming languages throughout my career including JavaScript, Python, and Go. I specifically looked for a Ruby position because I know what works for me.

What’s the best way to navigate this situation when the programming language I use daily significantly affects my job satisfaction?

I’ve been working at my current company for about 12 months as a Ruby on Rails developer. Recently management announced that Java will become our primary backend technology and all future development will use Java/Spring framework. They’ve already hired contractors to create several microservices in Java, so this transition is definitely happening.

I have more than a decade of development experience across various technologies, working on both client-side and server-side applications. After exploring different options, I deliberately chose a backend role focused on Ruby because I discovered what I enjoy most.

I can see three possible paths: 1) accept the change and learn Java 2) request more frontend responsibilities 3) look for opportunities elsewhere. Am I overlooking any alternatives?

After working on several Java tasks, I’m really not enthusiastic about option 1. Does anyone have suggestions for managing this transition? Particularly if I want to pivot toward more frontend development.

What makes this more challenging is that I’m at a senior level and received feedback about increasing my influence beyond just completing assigned work. It’s difficult to focus on broader impact when I need to invest significant time learning Java and Spring. Plus I just got moved to a different team during a recent reorganization, so I’m no longer mentoring junior Ruby developers where I was starting to take on leadership duties.

Maybe there’s a way to focus more on technical leadership and project coordination roles that would let me do minimal Java development while avoiding heavy coding tasks?

2

totally feel you on this! if you’re not into java, def consider looking for other roles that align with your skills and passion. it’d be a shame to stay somewhere that makes you unhappy. keep your options open and network!

3

have you thought about pitching a tech lead or architect role to management? since you want more influence, you could guide the java transition without getting stuck doing all the coding. what’s your company like when it comes to creating new positions?

4

Use your Ruby skills as leverage during this transition. Most companies totally underestimate how complex it is to migrate existing Ruby code while keeping it running alongside new Java services. Position yourself as the bridge between old and new systems - focus on integration architecture and data migration. You’ll stay valuable without diving deep into Java, and you’ll show the senior-level impact your management wants. I went through something similar moving from Python to .NET. Becoming the integration specialist gave me serious leverage in tech decisions. The trick is framing your Ruby knowledge as essential for a successful migration, not outdated tech.