Software Engineer, Open to flexible working
At BGL Group you'll be working across two products, Bean and a new open banking project. Bean set out to help people save money and optimise their outgoings through scanning their bank transactions and identifying recurring spend. Our purpose is to ensure people only spend what they need to spend by cancelling what isn't needed and switching to better alternatives. Ultimately, we want to help people improve their finances and take the stress out of it. We're now scaling the technology to fully embrace open banking and build a platform to support opportunities across the group.
What will you be responsible for as a Software Engineer at BGL Group?
- Make design decisions together
- Deliver quality software
- Make incremental improvements
- Practise the agile manifesto
- Resist process for process sake
- Use the right tools for the job
- Share ideas and knowledge. Continuously learn, improve and grow
- Learn from our successes and failures
- Hammock driven development (look it up - excellent talk by Rich Hickey)
What will it take to be successful as a Software Engineer within the Open Banking team?
- Someone who wants to use their skills to help people
- Has a passion for their craft but also a degree of pragmatism with great problem solving
- Get satisfaction from customers using their work
- Not scared of learning new things. Can bring their new learnings to their job and team
- Is team-orientated. We deliver as a team, we fail as a team. No rockstars or ninjas
- Understands that not everything needs to be solved with a 'technical hammer'
- Polyglot developers (specialism in Ruby is essential as a minimum. Elixir, React Native, and Elm is an additional bonus)
- Tech we currently use:
- Ruby on Rails, Elixir, Elm, Rspec, AWS, Terraform, Postgres, React, React Native, Redux, Rxjs, Express, Git. Generally, if we can justify it, we can use it
- Experience of using some or any of the above is also highly advantageous. (We're not expecting you to know everything. We just want good engineers who are eager to learn)
What we don't do:
- Ivory tower architecture
- Ignore tech debt
- Add more tech debt
- Work around problems
- Deliver the wrong solution
- Use techs because they look good on our CVs
- Take ourselves too seriously