Senior Software Engineer
Job description
Original text imported from Reed
We now have an exciting opportunity for a Senior Software Engineer to join the Operational and Regulatory Technology department for an award-winning investment platform, offering a collaborative team working environment, training and excellent career progression.
Our strategy is to have a cross functional development team, with team members working on all areas of our technology stack and propositions.
What to expect:
- Agile methodologies and a passion for continuous improvement and building a high-performance engineering team
- Guide and mentor the team to design and deliver high quality products
- Consider architectural and non-functional requirements and work with the team to deliver
Tech Competency
- Significant commercial experience developing services and APIs with C#, .NET core, Mongo and/or SQL with techniques such as domain-driven design and MVC.
- Strong technical background in web development with Angular/React/VueJs.
- Experience in developing HTTP-based APIs and implementation of RESTful services with JSON.
- Thorough understanding of CI/CD pipelines
- Practices Test Driven Development and is comfortable with various test frameworks and concepts.
- A proven record in developing scalable, highly available and highly performing middle-tier components.
- Familiarisation with containerisation and tools like Docker and Kubernetes
- Experience of developing, deploying, and maintaining Cloud-Based solutions on AWS
- Understand principles behind highly performing web pages
- Experience/Familiarity with Entity framework core.
- Experience/Familiarity with communications technologies (Web API, Google Protocol Buffers) and message queues (e.g. RabbitMQ, SQS)
Soft skills:
- Agile / SCRUM / SAFe
- Strong communication skills, written and verbal
- Very motivated with high levels of drive and enthusiasm
- E-commerce and/or financial services experience
About AJ Bell
AJ Bell is one of the UK’s fastest-growing investment platform businesses, providing award-winning solutions for everyone, from professional financial advisers to first-time investors.
Today, over 644,000 customers trust us to manage more than £103.3 billion of assets. By continually striving to make investing simpler and more accessible, we’re helping more people take control of their financial futures.
We’re proud to be recognised as one of the UK’s Best 100 Companies to Work For for six consecutive years, and a Great Place to Work in 2025 and 2026 a reflection of our supportive and collaborative culture.
What we offer
- 26 days holiday, increasing with service + buy/sell scheme + bank holidays
- 7% Pension with matched contributions
- Discretionary bonus scheme
- Share schemes (including free shares and BAYE)
- Health Cash Plan and discounted private healthcare
- Free onsite gym
- Enhanced family leave (subject to qualifying criteria)
- Travel and bike loan schemes
- Employee Assistance Programme
Life at AJ Bell
- Regular social events including summer and Christmas parties
- Learning and development opportunities tailored to you
- Casual dress code
- Friendly, supportive team environment
Our ways of working
We offer hybrid working, with a minimum of 50% of your working time per month spent in the office.
For new starters, there’s an initial period of full-time office working to help you settle in and build relationships.
Inclusion & diversity
We’re committed to creating an inclusive environment where everyone feels respected and able to be themselves at work.
We welcome applications from all backgrounds and make hiring decisions based on skills, experience and potential.
Key skills
AI-extracted from the job advert
Application advice
5 AI-generated recommendations to maximise your chances.
⭐ Lead with your C# and .NET Core experience in your Professional Summary or opening section, as this is the primary tech stack mentioned first in the requirements.
🏗️ Emphasise your architectural experience: include specific examples of scalable, highly available systems you've designed or refactored, with measurable outcomes (e.g. "Architected microservices reducing latency by 40%").
🎓 Highlight mentoring and team leadership achievements in a dedicated section or within your role descriptions—the advert explicitly values guiding and mentoring engineers.
🔄 Quantify your CI/CD and DevOps contributions: instead of "implemented CI/CD", write "Implemented CI/CD pipelines using [tools], reducing deployment time from X to Y minutes".
💼 If you have financial services or e-commerce sector experience, feature this prominently, as AJ Bell values domain knowledge in investment platforms and fintech.
Interview questions
10 questions generated from this advert.
Technical
- ›Walk us through a complex microservice architecture you've designed using C# and .NET Core. How did you handle scalability and high availability?
- ›Describe your approach to implementing RESTful APIs with JSON. What design patterns or principles (e.g. Domain-Driven Design) did you apply?
- ›Tell us about your experience with CI/CD pipelines. What tools have you used, and how have you optimised them to improve deployment frequency or reliability?
- ›How have you used Docker and Kubernetes in a production environment? What challenges did you face and how did you resolve them?
- ›Explain your experience with message queues such as RabbitMQ or SQS. In what scenarios have you chosen one over the other, and what were the trade-offs?
Behavioural
- ›Describe a time when you mentored a junior or mid-level engineer. How did you approach their development, and what was the outcome?
- ›Tell us about a situation where you had to balance architectural best practices with commercial or time pressures. How did you communicate your recommendations to the team?
- ›Give an example of how you've fostered a high-performance engineering culture in your team. What practices or initiatives did you introduce?
- ›Describe your experience working in Agile or SCRUM environments. How do you ensure continuous improvement within your team?
- ›Tell us about a cross-functional project where you worked with non-technical stakeholders. How did you communicate technical concepts and manage expectations?