We're looking for a Senior Ruby on Rails Developer to join a project for a US-based HealthTech client.
You'll write and review code, contribute to architecture decisions, optimize performance and care about code quality, working closely with PMs, designers and other developers. You'll use AI every day to move faster, and you'll be the one who makes sure the code is actually correct, secure and maintainable before it gets merged. "AI generated it" isn't done. In healthcare, a subtle bug or a missed edge case costs more than time.
What you'll do
- Design and build web applications in Ruby on Rails, including relational database design
- Work with cross-functional teams to define, design and ship new features
- Write automated tests that cover edge cases and overall reliability
- Fix bugs and improve performance
- Review code with the same standards, whether a person or AI wrote it
- Help define and improve internal standards for maintainability and style
- Talk directly with the client when needed: clarify requirements, discuss technical solutions and present your work
- Test new tools and workflows, and share what works with the team
Kogo poszukujemy?
- 5+ years commercial Ruby and Ruby on Rails
- Relational DBs (PostgreSQL); experience with NoSQL, caching, message brokers
- Client comms: REST API, WebSockets; auth: JWT, cookies, OAuth
- CI/CD, deployment tools, Docker, Git
- Design patterns, SOLID principles
- Automated tests with RSpec or similar
- Architecture contribution: business/functional/non-functional requirements, scalability
- Daily use of AI tools; ability to review AI-generated code
- Code review: giving and receiving
- Fluent English (client calls, demos, technical discussions)
- Fluent Polish (internal)
- Interest in HealthTech; focus on quality, security, compliance
Nice to have
- JS framework: Vue or React
- AWS or similar cloud platform
- Web servers (Nginx)
- HealthTech/pharmacy: HIPAA, e-prescribing, insurance, FHIR
- Experience embedded with client, consulting, FDE, or startup multitasking
This role probably isn't for you if:
- You treat a ticket as done when code runs rather than tested, reviewed, maintainable long-term
- You prefer an unchanged stack/workflow for years; we adopt better tools regularly
- You avoid responsibility for merges; here you sign off final code