New Discussion

Notifications

You’re not receiving notifications from this thread.

New Position Senior engineer, where to start?

3
Tips

Hi everyone,
I am starting a new position as a senior software engineer. I was told that it is very ruby on rails environment. I want to know what is the best way to get started with learning intermediate to advanced level ruby/rails knowledge? What are best practices? Is there a suggested roadmap? I have about a month before I start. Any guidance is appreciated.

Hey, congrats on the new role! I was in a similar spot recently.

If you’ve got a month, I’d focus less on basics and more on how Rails apps are structured in real life:

  1. Deepen core Rails concepts

MVC is obvious, but really understand:
ActiveRecord (associations, scopes, callbacks)
background jobs (Sidekiq/ActiveJob)
service objects / POROs (since most real apps use them)

  1. Read real code

Clone a solid open-source Rails app (like Discourse or similar)
Follow a request from controller → model → view → background job
This helped me more than tutorials

  1. Testing

Get comfortable with RSpec + factories
Learn how people structure tests (request specs, model specs)

  1. Common patterns in production apps

Service objects
Form objects
Authorization (Pundit/CanCanCan)
API design (if they use Rails as backend)

  1. Do a small project

Build something simple but “production-like”:
auth
background job
API endpoint
tests

  1. Bonus (huge plus as senior)

Read about performance (N+1 queries, indexing)
Caching basics
Code review best practices

Honestly, the biggest shift at “senior” level is not syntax, it’s reading code, making decisions, and understanding trade-offs. @sports games

Congrats on the new role! A month is actually solid prep time. Here's what I'd focus on:
Ruby first, Rails second. If your Ruby fundamentals are shaky, Rails will feel like magic you can't control. Go through The Well-Grounded Rubyist or just grind exercism.io/tracks/ruby for a week.
Then Rails: the official guides (guides.rubyonrails.org) are genuinely great — don't skip them. Focus on ActiveRecord, routing, and the request/response cycle.
For intermediate/advanced: look into service objects, concerns, background jobs (Sidekiq), and how to keep fat models slim. The Rails AntiPatterns book is old but gold.
Testing — learn RSpec basics. Most serious Rails shops live and die by it.
Good luck, you'll hit the ground running!

Join the discussion
Create an account Log in

Learning Ruby on Rails? Join our newsletter.

We won't send you spam. Unsubscribe at any time.