2,001 to 2,025 of 2,080 Software Engineer Jobs in the UK excluding London

SoftInWay Inc is seeking a Software Developer to join their team in Bristol, UK, focusing on the development of advanced functions within the AxSTREAM platform, a leading tool for turbomachinery analysis. Ideal candidates will have a Master's degree and a minimum of 2 years in engineering software ...

Working within the Data & AI capability team, this role designs, builds, and operates full-stack, AI-enabled software, with a strong frontend focus. You build the user-facing products and interfaces that make McLaren's data and AI usable: chat experiences, engineering assistants, dashboards, and internal digital products, backed ...

Oxford Cancer is seeking a Research Data Integration and Software Developer to join the OCDEM team at Churchill Hospital, Oxford. You will help develop and maintain cancer data information systems underpinning precision medicine research. Based in Oxford, the role involves working with researchers across the UK, using R/ ...

looking for driven and pragmatic product-minded software engineers, who care about user experience and have experience of scaling consumer applications - in particular of ensuring a consistently great experience for users regardless of what device they're on. About Flok More than a billion people a year suffer unnecessarily ...

Join bet365 Group in Stoke-on-Trent as a Software Developer, where you will be an essential part of a talented team. The role emphasizes creating high-quality scalable solutions while leveraging agile methodologies. Your skills in languages like Golang and experience in web and server-side development will ...

Country: United Kingdom Location: Gloucester, South Gloucestershire Position Role Type: Onsite Our client have a full time, perm opportunity for a Senior Software Engineerto join our specialist teams in Manchester, Gloucester or London working fully onsite click apply for full job details ...

Central is looking for 3 talented Software Engineers to help shape the future of our core insurance platform. Working in a Scrum team, you’ll design, develop and support features that deliver real value to customers and colleagues. This is an exciting opportunity to work with modern technologies ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...

times in half for the whole team writing an RFC that becomes the pattern we use for all event-driven services pairing with another engineer to help them reason through FoundationDB transaction semantics owning card issuing from initial RFC through to processing the first live transaction - making every architecture … built, then own getting it into production Setting technical direction - your code reviews, implementation patterns, and architectural choices influence how the wider team builds software Production responsibility - the systems you build are yours to monitor, debug, and improve when issues arise Your background You'll fit well here ...