<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Spacecraft Digital - Medium]]></title>
        <description><![CDATA[Award winning creative web agency. Part of the @jadu group of companies. - Medium]]></description>
        <link>https://medium.com/spacecraft-digital?source=rss----a271f336b4fe---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Spacecraft Digital - Medium</title>
            <link>https://medium.com/spacecraft-digital?source=rss----a271f336b4fe---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:20:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/spacecraft-digital" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Delivering a website and tenant’s portal for Oxford City Council’s unique mix of audiences]]></title>
            <link>https://medium.com/spacecraft-digital/delivering-a-website-and-tenant-s-portal-for-oxford-city-council-s-unique-mix-of-audiences-dff52092f645?source=rss----a271f336b4fe---4</link>
            <guid isPermaLink="false">https://medium.com/p/dff52092f645</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[website-design]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Spacecraft Digital]]></dc:creator>
            <pubDate>Wed, 13 Jan 2016 10:18:48 GMT</pubDate>
            <atom:updated>2016-01-13T10:32:06.469Z</atom:updated>
            <content:encoded><![CDATA[<p>By Rachael Johnston, Spacecraft Digital</p><p>The natural tendency for organisations is to design for themselves (or their stakeholders) rather than designing for the target audience. However, from the outset Oxford City Council was adamant that their new site must be tailored to the people of the city and the ways they specifically wished to access services online.</p><p>In line with this brief, Spacecraft Digital has launched a new Oxford City Council website and tenant’s portal designed to meet the needs of a unique mix of users including a diverse population of 158,000, a large commuting workforce, the highest student population in England and Wales and 9.5 million visiting tourists each year.</p><p>Delivering a design solution that meets the needs of such a diverse group requires a wide variety of research techniques beforehand, during and post launch. User Experience (UX) research happens before and during the design phase and, in this case, included analysis of data provided by the council. During this discovery phase we quickly uncovered several key findings that would heavily influence the design of the new site.</p><p>A fundamental issue was that 40 percent of website visitors were accessing the old website from mobile devices but it was never designed to be accessed in such a way. A large percentage of users were accessing via high-end Apple devices, which correlated with demographic data showing that a large portion of the population were young, affluent people, presumably a high percentage of which were studying at the various prestigious Universities within the city. However, demographics also showed sharp geographical divides in the city across social indicators and we were acutely aware of the need to accommodate all levels of technical abilities. This of course necessitated a responsive design, fit for use across devices but one that also served the majority accessing via desktops.</p><p>But it wasn’t just those that lived and worked in the area that needed to be accommodated. Over half of the Council’s website traffic comes from users outside of the city, much of which from outside of the UK. Because of its rich history, the city of Oxford is a popular tourist destination and consideration had to be made for visitors looking for information on transport links, parking, visitor attractions and events happening within the city. A content audit revealed that some pages had become overly text heavy and this lead to a website rewrite to make pages shorter, clearer and easier to read.</p><p>Web analytics were also used to reveal the popular areas of the site and how they could be improved. For example, disparity between content linked-to from the homepage and popular search terms and results. We knew that one of the most popular areas on the existing site was ‘planning’, however the planning pages linked-to from the homepage had very high bounce rates, meaning that visitors quickly left after arriving. However, when ‘planning’ was searched for, the returned results resulted in far fewer bounce rates. Therefore we were able to quickly infer that by simply replacing the links for planning on the homepage, we could improve the journey and experience for users and reduce the reliance upon searching.</p><p>The site has been redesigned from the ground up to provide quick and easy access and is a big part of meeting Oxford City Council’s targets of increasing the proportion of contact that is online to almost 40 percent by 2018. Currently they’re at 26%.</p><p>Getting universal agreement on such a redesign can be one of the most tricky parts of the process because it is so subjective and we all have different perspectives. Within large organisations design approval can get caught up in the prioritisation of content. However analysis turns the data collected during research into actionable information and has helped inform the design process with complete objectivity. The result is a site that meets the specific needs of a diverse audience, backed-up by UX research. However, now that the website has gone live, real-world user testing will kick into action to make sure the website truly delivers what is needed.</p><p><a href="http://www.oxford.gov.uk/">www.oxford.gov.uk</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lp_SgKvZtsAAb86aHL27zg.png" /><figcaption>Oxford.gov.uk</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dff52092f645" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spacecraft-digital/delivering-a-website-and-tenant-s-portal-for-oxford-city-council-s-unique-mix-of-audiences-dff52092f645">Delivering a website and tenant’s portal for Oxford City Council’s unique mix of audiences</a> was originally published in <a href="https://medium.com/spacecraft-digital">Spacecraft Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we hire developers at Spacecraft]]></title>
            <link>https://medium.com/spacecraft-digital/how-we-hire-developers-at-spacecraft-33c150f8cef8?source=rss----a271f336b4fe---4</link>
            <guid isPermaLink="false">https://medium.com/p/33c150f8cef8</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Richard Backhouse]]></dc:creator>
            <pubDate>Mon, 04 Jan 2016 09:33:23 GMT</pubDate>
            <atom:updated>2016-01-07T16:56:57.748Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sAso76geS9M1J1_y6XHYFw.png" /></figure><p>We have been interviewing developers for a long time now. Our process has evolved from asking a few set questions to one where we cover the important stuff while trying to be open and participative along the way.</p><p>It may be trite to say but hiring is a two-way process. It is just as important for a candidate to learn enough about us as it is for us to find out about them. Hiring is about fit. We want people to be happy in their role at Spacecraft.</p><p>We think it is important to be fair and open with the interview process. We do not believe in quizzes and trick questions. In that spirit we would like to share some insights into our process and the types of questions we ask so that candidates can feel comfortable and prepared when speaking to us.</p><h4>Process</h4><p>We usually start the interview process with a short telephone call, 10–15 minutes. In this we ask a few basic questions about web development (e.g. telling us about a recent project) and also give the candidate the opportunity to ask any questions about the role.</p><p>After the phone interview we ask candidates to <a href="https://github.com/spacecraft-digital/rss-reader">write a small application</a> to get a feel for the type of code they write. An equivalent sample of code, e.g. on GitHub, would also be fine. We ask that frameworks and libraries are not used for this code; we want to get a feel for how someone architects an application that is not just plugging code into a framework.</p><p>The general structure and topics of an interview are the same whatever the level of experience of the candidate. This makes it easier to assess where someone is at with their own knowledge and compared to other developers in the team. We would expect a far deeper level of knowledge and discussion the more experienced a developer is. For people earlier in their careers, such as graduates, we like to give as much guidance as possible before the interview about the types of things we will be talking about. For junior developers, how they go about finding information and what they are able to learn is much more relevant than what they currently know.</p><h4>Current / recent position</h4><p>We like to find out what candidates do in their current or most recent position — it gives a good indication of the gap in knowledge, experience, tools and processes between what they do now and how we work. We’re not looking for an exact match or even a close fit — all organisations work differently — but it’s a good basis for a discussion. Are there code reviews? What form do they take? Are they useful? What do you look for in a review? So questions may start off about current practices but evolve into more general discussions.</p><h4>General knowledge about the Internet and web development</h4><p>There is certainly something to be said for hiring smart developers who can get things done despite not using the exact technologies we use. What is very useful though is some foundational knowledge about what makes the Internet tick. What happens when a user makes a request from their browser? What role does JavaScript play?</p><h4>Security</h4><p>We bake security considerations into our development process. When bugs, security and performance issues do occur, we don’t really care about a specific mistake an individual might have made. We would rather consider how we can improve the way we work to avoid similar things happening again. While it is important for the process to prevent and catch potential problems it is good to know what a candidate’s approach to and level of knowledge around security is.</p><p>It would be unfair for a candidate to have the same level of knowledge as our combined knowledge and experience of web security (although it would be nice!) but we would expect a reasonable level of discussion around the potential security vulnerabilities in web applications and how they can be prevented.</p><h4>Performance</h4><p>Like security, performance is a subject where a little knowledge can go a long way. We try to assess whether a candidate’s knowledge of performance matches with the types of applications they have worked on, i.e. are they aware of the performance implications and constraints for their code or do they just bang out code for the performance pixies to pick up if a problem arises?</p><h4>Code design</h4><p>Anyone can write code but writing elegant, testable and maintainable code takes skill and experience. A lot of code design questions will be answered by seeing the code a candidate writes, which at the least will give us the opportunity to discuss in a code-review-like scenario.</p><h4>After the interview</h4><p>When the interview, or sometimes interviews, are complete we get together for a quick chat and come to a decision. This is generally not a lengthy process. If someone is a good fit for us and we are a good fit for them we make an offer.</p><p>Here are some books and blog posts that have influenced our process over the years:</p><ul><li><a href="http://www.joelonsoftware.com/items/2007/06/05.html">Smart and Gets Things Done</a></li><li><a href="http://www.jasonbock.net/jb/News/Item/7c334037d1a9437d9fa6506e2f35eaac">If Carpenters Were Hired Like Programmers</a></li><li><a href="http://www.amazon.co.uk/How-Google-Works-Eric-Schmidt-ebook/dp/B00J379F3O">How Google Works</a></li><li><a href="http://blog.codinghorror.com/why-cant-programmers-program/">Why Can’t Programmers… Program?</a></li></ul><p>If you would like to join us, say <a href="/service/mailto:hello@spacecraft.co.uk">hello@spacecraft.co.uk</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=33c150f8cef8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/spacecraft-digital/how-we-hire-developers-at-spacecraft-33c150f8cef8">How we hire developers at Spacecraft</a> was originally published in <a href="https://medium.com/spacecraft-digital">Spacecraft Digital</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>