Selecting and using modern development methods and following agile practices, you will build top-to-bottom functionality with ReactJS and React Native for the web & mobile front-ends, through to AWS Lambda, API Gateway, Step Functions, Kinesis, Aurora, Cognito, Pinpoint, Cloud Directory, Redshift, SQS, Quicksight… and as much of the rest of the AWS FaaS and platform services as make sense to allow you to focus on building applications rather than plumbing.
You will be part of a new, three-developer team, to deliver a modern application suite that enables companies, public sector organisations, schools and the general public to book and manage the transport they need to get their staff, students and holidaymakers to where they need to be…. think Uber™ for coaches!
Working in harmony with a devops lead, you’ll also need to lend a hand defining the Terraform based configurations, and figuring out the best methods and tech to introduce CI/CD efficiencies.
Based amongst some of your user base in our Cox Green, Maidenhead office, you will have ample opportunity for corridor testing of ideas through prototypes, whilst more formal UAT will be structured to ensure you (and we!) have the confidence your product will deliver in live.
Please note that this is not a home or remote worker role, so you must be commutable to Cox Green, however, as with all developer roles, we expect there will be a number days during each week where you simply need to stay home, get your head down and code!
You love building product that people actually use and just as importantly you care passionately about quality: not just in the end product, but also in delivering code that other developers can maintain, using best-practice design principles and coding standards.
You wouldn’t dream about writing code without an accompanying test, and you treasure the DevOps principles of developers and technical operations working in harmony to embed security, scale and resilience into your continuous delivery strategy.
Teamwork means more to you than just sharing the tea-runs and buying the Haribo™ on your birthday. You actively assist and mentor your peers in their own learning, know when to ask for help yourself, and the two highlights of your sprint cycle are the planning and retrospective sessions, where you both give and take across story definition, personal recognition and constructive suggestions for improvements.
- ReactJS: if you haven’t yet, then you know you want to; and can instead demonstrate your expertise across Angular, Ember, Dojo or Vue.
- React Native: you may have only dabbled, or you may have apps already on the stores, complete with shelling out to native components and SDKs like Geolocation or NFC. Alternatively, if you’ve got some Android Java, SWIFT or ObjectiveC under your belt, then it all counts.
- AWS Lambda, API Gateway, Step Functions… or NodeJS: Let’s be realistic… not every developer has worked for forward-thinking companies that know serverless is the future, so if you haven’t yet had a chance to ditch the [virtual] tin, prove to us instead that you are a NodeJS guru and can learn the modern AWS FaaS methodologies as you go.
- Redux? Webpack? Gulp? Browserify? Flux? Relay? Flow? ImmutableJS?: If you have the skills and can prove the advantage of your preferred libraries to your peers, then consensus will mean go for it (license agreement permitting).
- HTML/CSS/SASS/LESS/REST/JSON: Duh!
- TDD/BDD: we shouldn’t even have to mention it. You’ve been on Github. You know that no self respecting NPM ships without its tests. You practice what you preach and provide unto others what which you expect to consume yourself… and it’s not an afterthought.
- Terraform: if you’ve got it, we’ll take it.
- Security ingrained: You know your CAPTCHAs from your SQL injection from your brute force attacks, how to specify and develop to mitigate them, and under the covers you know your IAM from your KMS from your Secrets Manager and will layer security throughout your application stack. ...PII - encrypt it!
- English Communication Skills: you can debate your technical solutions with developers and business people alike. You won’t be expected to write War & Peace, but you will be expected to keep the development wiki comprehensible