Senior React Engineer

You'll form a key part of a team of developers building React-based components and applications to support our SaaS eCommerce and headless platforms.

As an example of what you'll be working on: we're building headless eCommerce sites with Gatsby and rich interactive product customisers with Next.js on Vercel.

You start your day in a team Stand Up discussing progress you made yesterday, listening to your team members describe their current issues and dropping some knowledge bombs on how you “solved this last time”. You’re working from home today, so you pay the pet tax and encourage your four-legged-friend wave to the camera before logging off.

First up you’ve got a pair-programming session with a Junior Developer in your team to help them through a tough search component that they’ve been working on. They’ve been steadily improving under your experienced wing and are turning into a really productive team member.

After lunch you’ll set your Slack status and turn on Do Not Disturb for a couple of hours while you debug a weird issue with a customer’s site. There’s been a change to the out of stock logic recently to support multiple warehouses. You update your unit test suite to cover this unexpected scenario and tell the Project Manager the good news! You push your feature branch to Bitbucket and watch Bitbucket Pipelines build your artifact and prove that your tests pass.

Your JIRA issue has automatically transitioned to “In Code Review” and you open your pull request, studying your diff carefully before assigning it to your team mate for a sanity check.

Tomorrow (assuming all is well!) you’ll merge your pull request into a release branch and let Pipelines deploy it to Staging where it will be regression tested by the QA Team and their bank of automated tests. It should be out to Production by the end of the week, providing we can get through the testing and get client sign off by 2pm on Thursday.

If you read this and it sounds like your ideal job — we want you on the team!

The following should give you an idea of how you’ll be expected to typically be spending your time. It’s not set in stone and it may change from week-to-week, but it gives an idea of what is expected from the role.

The majority of your time will be spent working with your team to deliver software that meets the needs of our customers. This isn’t time that you’ll spend entirely in your editor, there’s stand up, sprint planning, scoping, architecting and designing that you’ll take part in to make sure we’re building exactly what we need in the right way.

Given your experience, a portion of this time is expected to be spent assisting other team members in delivering their work effectively.

Making sure that we don’t sit still and keep evolving the way we build and deliver software is a critical investment of time, particularly from a team member with your experience. Use this time to try that tool you read about and see if it’s worthy of being a part of our toolchain.

Keeping up with new software releases, development practices, horror stories and post mortems are an essential part of any Software Developer’s time! Use this time to push forward your objectives and research tools and techniques you need to stay productive.

Be sure to mention the words PELICAN ABILITY HAMSTER when applying to show you read the job post completely. This is a beta feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.