Hello, I’m Paul, also known as @psd and I’ve just joined GDS as a Technical Architect. First impressions are important but soon forgotten, so here are some of mine from the first day of working with the team.
I joined GDS because there’s nothing cooler than working on something that touches so many peoples lives. It’s not just the reach of the services being built for Gov.UK that I found attractive, but the importance placed on high quality, beautiful design and attention to detail. This is perfectly embodied by the “What to do when someone dies” page, which focuses on tasks and provides crucial information quickly and clearly.
The vision of the team here at GDS is ambitious, as encapsulated by Ben Terrett’s post on design. I fully expect to to see the GOV.UK icons on tea towels in heritage shops in years to come.
Working environments matter to me, and the GDS office is centrally located, well maintained and better appointed than most London startups I’ve visited, though sitting on one part of the floor can feel a little like being in a bouncy castle. There’s a nice kitchen that’s only missing one essential bit of kit: we could really do with a dishwasher!
Rather impressively by lunchtime of my first day I’d been given a Cabinet Office Email address (accessible using Google Apps for Business), a laptop (a security hardened 13″ MacBook Air), a mobile phone (an iPhone which I declined) and, most importantly, a building pass so I could go to the loo without a chaperone! Like most developers, I’m extremely picky about my external brain, so have elected to swap the 13″ MacBook for the promise of an 11″ sometime in the future.
Looking across the floor it’s difficult to tell who works for GDS and who doesn’t. There are no silos here; it is apparently not an elitist enclave. We don’t have assigned desks, sitting next to whoever we happen to be working with on a day-by-day basis. To succeed, GDS has to break down walls and work with domain experts regardless of where they’re from — the Whitehall project, which is in full sail, is a hubbub of graphic artists, designers, front-end developers, copy-writers and policy wonks from across government.
As you’d expect, most of our projects are up on github and released as open source, so I had seen and experimented with some of the code even before joining and ahead of James walking me through the emerging platform.
Good people beget good people, and it seems every time I look up from my desk there’s someone new and interesting visiting. It’s easy to become blasé about comings and goings in the office, but I was particularly disappointed when I realised I’d just missed Margaret Calvert’s visit via a github commit message.
In software development, “Architect” can become a term of abuse, implying someone who just assembles packages or engages in abstraction astronautics. After a day shadowing James and Mat, it’s obvious the GDS “Technical Architect” role is more akin to that of a Master Chef, someone who ensures kitchens are working well, menus makes sense across restaurants, thinks strategically and mentors colleagues (though without the enlarged ego). A good chef cares about the ingredients and it was great to hear how a recent technical choice was made with a Ruby versus Scala bake-off, coded by James and Mat.
The Size of The Prize
As a hint of what is in store for me, Etienne and I looked at the documentation for a medium sized government procurement. It’s mind boggling to see tens of millions of pounds allocated to “Software Licences”, and tasks of customising an off-the-shelf software package taking tens of thousands of man-days! There are few economies of scale in enterprise software; big projects are expensive to run because they’re big, but shaving 1% off this budget would pay for ten GOV.UK betas.
Deploy on First Day
Just before heading home we decided to create a commemorative Valentine’s Day homepage for GOV.UK. A Kanban card was added to the sprint wall and Ben quickly came up with a design. I sat with James Weiner and Dafydd Vaughan whilst we built, tested and deployed the new ‘heart-shaped wood’ homepage, meaning I witnessed concept to delivery all in the space of half an hour.
One of Us
Applying to join GDS was relatively straight forward. I spotted the job announcement on Twitter. A few weeks elapsed between submitting a rather lengthy form and being invited for an interview, but I was fortunate to quickly receive an offer, and just over a week later had signed paperwork and was ready to start. I gather the application process is even smoother now, replacing the long Word document with a more conventional CV and covering letter.
Since joining, I’ve had a small insight into the other side of the fence, acting as one of three interviewers for Technical Architect (another me!) and Developer roles. The process strives to be relaxed and fair to all candidates, with a standard interview striking a balance between the competency based questions required by the Civil Service and some straight-forward technology challenges at the whiteboard. Most developers enjoy the pairing exercise as it’s an opportunity to show off what you know, and discuss different approaches to coding.
If you like the sound of working with an amazing team to change the digital face of Government, we’re still hiring for a wide range of positions. Thayer Prime (Thayer.Prime@digital.cabinet-office.gov.uk) is a great point of first contact.