Only good for short-term - Software Developer Blacklight Software Employee Review

Over the several years I worked there we had a varied profile of work consisting of a mix of front and back-end development. As a small-to-medium sized business there is also plenty of opporunity to have contact with the client which may not be for some but it's motivating to see the impact of your work.

If I had to be picky I'd say the locaiton wasn't always the best having moved further away from where I live. The nearest train station is only one stop away from Leeds but is a 15 min walk from the office.

- Relatively small company, can establish better relationships with colleagues and directors - Directors/senior management are always friendly and approachable, you can approach them with a concern and they will take it into account - Flexible working (home working, flexible hours etc.) - Decent pay (a bit behind, but nothing major) - Developers have a good amount of autonomy in regards to architecture / implementation of a project (however key elements such as use of Dynamics, mentioned in Cons, are often out of developer's control as they are part of the sale/requirements doc)

- Heavy focus on scoring projects with dependancies on Dynamics 365 and SharePoint, even in cases where it's not the most practical solution - Not Blacklight specific, however working with Microsoft's cloud business solutions in recent years can be a pain with outdated (or lack-of) documentation and off-putting functionality, especially when looking at extending functionality as a developer - At time of leaving, internal project documentation was fragmented across several wikis and was often out-dated and/or not detailed enough. This was more down to not having the time dedicated to write it. However, I am aware that there was an initative to improve on that around the time I left, so this could have already improved. - There is a chance you'd be spread across multiple projects at a time once you enter your 2nd year of employment, attending 2/3 standups and having to prioritise work between each of them individually. Often a case when you've dipped your toes in a few projects over the past year, change requests come through for said projects and you're assigned based on previous experience with the original project, despite also being on a larger project with a new client (this is based on personal experience, I am aware that not all developers had these experiences so mileage might vary)