
Client
Website



Most candidates entered the sites on phones, and that's already where the problems started. Everything was spread across three separate sections: pilot, paratrooper and mySPHAIR, each one organised differently, with no single process holding it together.
SPHAIR assumed the visitor already knew what they did and whether they wanted to be a pilot or a paratrooper. So a clear entry point needed to be provided that streamlines the process and gives the necessary information.




Each of these fixes had to work identically across pilot, paratrooper, and drone, at mobile and desktop. The Figma prototype needed frequent updates, so I maintained a sitemap and component library.









