At a Glance
- Tasks: Design and develop cutting-edge instrument control software for scientific products.
- Company: Join a leading society focused on research software engineering.
- Benefits: Competitive salary, flexible working hours, and opportunities for professional growth.
- Other info: Collaborative team environment with exciting projects and career advancement.
- Why this job: Make a real impact in the scientific community with your coding skills.
- Qualifications: Experience in C++ and a background in mass spectrometry or relevant fields.
The predicted salary is between 55000 - 70000 £ per year.
Society of Research Software Engineering is seeking a Senior C++ Software Engineer to join a cross-disciplinary team working on instrument control software across scientific products.
You will design and develop new technologies while enhancing existing platforms for mass spectrometry, chromatography and informatics.
Senior/principal candidates with mass spectrometry/scientific background are ideal; mid-level applicants with relevant experience will also be considered.
#J-18808-Ljbffr
Senior C++ Software Engineer - Instrument Control employer: Society of Research Software Engineering
The British Library is an exceptional employer, offering a vibrant work culture that fosters innovation and collaboration within the Digital Research Team. With a commitment to inclusivity and diversity, employees benefit from flexible working arrangements, generous holiday allowances, and opportunities for professional growth in a prestigious environment dedicated to advancing digital scholarship and public outreach.
Contact Details:
Society of Research Software Engineering Recruitment Team
StudySmarter Expert Advice🤫
We think this is how you could land Senior C++ Software Engineer - Instrument Control
✨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 Society of Research Software Engineering 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 Society of Research Software Engineering.
✨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 Society of Research Software Engineering.
✨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 Society of Research Software Engineering 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 Senior C++ Software Engineer - Instrument Control
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 Society of Research Software Engineering.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Society of Research Software Engineering 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 Society of Research Software Engineering
✨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 Society of Research Software Engineering 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.
