At a Glance
- Tasks: Join a collaborative team to develop exciting fintech projects using Ruby on Rails.
- Company: A scaling fintech client with a strong market presence.
- Benefits: Competitive salary, hybrid working, and opportunities for professional growth.
- Other info: Work closely with customers in a supportive environment.
- Why this job: Make a real impact in fintech while enhancing your engineering skills.
- Qualifications: Mid-level Ruby development experience; frontend skills are a bonus.
The predicted salary is between 45000 - 55000 £ per year.
Ruby Developer - FinTech - Up to 55k
I’m working exclusively with a scaling fintech client (so you won\'t hear this via another recruiter) who are expanding their footprint in the market. They’re looking for multiple Mid-Level Ruby Developers to join their small, collaborative team
Salary: £45,000 – £55,000
Working Arrangements : Hybrid in London (3 days a week in the office)
Tech Stack: Ruby on Rails, JavaScript, DevOps tooling\'s, AWS
This is a backend focused role although any frontend experience is a bonus.
It\'s a great opportunity to work on exciting projects in an environment which will support you and help you grow as an engineer. You will also be working very closely with their customers and this is experience that they really value.
If this is of interest, please get in touch ASAP - will be moving quickly!!
Ruby Developer - FinTech - Up to 55k
Ruby on Rails Developer in Sheffield employer: Oliver Bernard
Join a dynamic fintech company that prioritises employee growth and collaboration, offering a supportive environment where you can thrive as a Ruby on Rails Developer. With a hybrid working model in London, you'll enjoy the flexibility of working three days in the office while engaging in exciting projects that directly impact customers. This is an excellent opportunity to enhance your skills and advance your career in a rapidly expanding industry.
StudySmarter Expert Advice🤫
We think this is how you could land Ruby on Rails Developer in Sheffield
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Oliver Bernard or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Oliver Bernard.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Oliver Bernard.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Oliver Bernard that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Ruby on Rails Developer in Sheffield
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Oliver Bernard.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Oliver Bernard and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Oliver Bernard
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Oliver Bernard uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.
