Full Stack Product Engineer

Plutus; United Kingdom; Remote; GBP 40,000 - 70,000; Full time

Job summary

Join a dynamic and innovative remote-first company as a full stack engineer, where you'll have the opportunity to create beautiful user experiences. You'll take full ownership of features, collaborating closely with a small team of dedicated professionals. This role offers a unique chance to grow your skills and make a real impact in a startup environment. With a focus on quality and user experience, you'll be part of a team that values experimentation and flexibility. If you're passionate about building functional products and eager to learn, this is the perfect opportunity for you.

Benefits

Flexible working hours

Remote work opportunities

10% time for personal projects

Team retrospectives for process improvement

Qualifications

• 3+ years of experience as a software engineer.
• Strong experience with JavaScript and React.
• Familiarity with backend technologies is a plus.

Responsibilities

• Build and manage features from start to finish with ownership.
• Collaborate with designers and product managers on feature planning.
• Contribute to support queries and product roadmap planning.

Skills

JavaScript

React

Backend Development

Ruby

AWS

Tools

Rails

AWS Lambda

Notion

Slack

Job description

We're looking for full stack engineers to build beautiful and functional products from start to finish. We’re flexible about when you work and believe in experimentation – whether that’s with how we build things or how our teams work. We’d love to chat with you if you like the sound of this and love to build great user experiences!

We are a "remote-first" company and there's no requirement for anyone to come into the zeroheight office on a regular basis - more details on what remote-first looks like

What would you be doing?

We're still small (14 product engineers, 60 people total) so you'd be working on building all types of features teaming up with a designer and product manager. You'll have start-to-finish ownership of the features – this brings accountability but also an awesome sense of pride when users love your work. You'll be involved in planning scope to ensure we deliver value to our users quickly.

Here are some examples of recent features to give a taste of what you could be working on:

1. New ways of storing, managing, and exporting design tokens, aligned to the W3C spec.
2. Integrating zeroheight with communication platforms like Slack and Microsoft Teams.
3. Adding theming capabilities to our platform so users can better document things like dark and light modes.

You'll also be included in some things that are outside the traditional "software engineering" domain. Things like helping with support queries, planning the product roadmap, project management for your features, and contributing to wider company processes. There’ll also be plenty of opportunities to share your work, new technologies you’ve been exploring, and things you’ve learnt with the team. Joining now is great if you want to broaden your skills or you'd like to create your own startup at some point.

If you're interested, here's a more detailed idea of what you'd be up to in the first 6 months

How is zeroheight different?

Here's what we think zeroheight does differently compared to another job you might be considering:

1. A focus on QA and UX – we take UX quality seriously and make sure everything is excellent before we ship. This also means we have to be careful about scope-creep to ensure we have time to polish.
2. Ownership – you'll own a feature from start to finish. This means you have the freedom to choose how to build it and you're responsible for the implementation and release.
3. Everyone plans – we try to get everyone involved in planning and scoping features to prevent a top-down approach where engineers are just pumping out feature specs.
4. Document all the things – we use Notion for our process documentation and try to keep communication on Slack as open as possible.
5. 10% time – we set aside a day every 2 weeks to work on whatever you like.

Our tech stack

We use React to build any new UI components, paired with Storybook to work on them in isolation. We then integrate them into the main product. Some of our older codebase is written in Marionette (Backbone.js) and we're working on a smooth transition (instead of a massive rewrite).

On the backend, our main server is in Rails (Ruby). We host our database and cloud infrastructure on AWS and use serverless functions (AWS Lambda) for a few things.

One word of warning – if you're super passionate about a particular tech, our startup might not be the right place for you. We're focused on getting things done and shipping an amazing product; we'll use whatever tech helps us get there.

Are we a good match?

If these points mostly resonate, let's have a chat:

1. You love creating beautiful UIs with precision and attention to detail; you understand how important design is to a successful product.
2. You're curious to learn about the design process and design systems.
3. You relish the excitement of a startup – you have a proactive attitude and a strong desire to succeed in an environment where you'll need to be efficient and adaptable to change.
4. You're looking for somewhere to grow – you want to get stuck in and have a real impact in the company's future. You're flexible and not afraid of taking on more responsibility as we grow.

What we're looking for

Required experience

1. 3 years or more working as a software engineer.
2. Experience with JavaScript and React.
3. Some experience with backend.

Useful / Bonus experience

1. Ruby.
2. AWS / Servers.

How do we work?

Each of our teams has autonomy to work in a way that is best for them, experimenting with their processes freely. In general, teams tend not to have traditional standups and instead share plans and updates over Slack – we really value flexibility and this kind of thing allows people to read the updates in their own time. Hours are flexible – we have a recommended weekly total and times we try to keep our meetings between, but we’re keen you can fit your work around things you might need to do at home.

We have regular retrospectives to take a look at how we can improve our processes – both at a team level and across Engineering. Teams also do sprint planning either weekly or fortnightly to schedule work, and we tend to rotate responsibility for facilitating these around the team.

The feature roadmap is planned quarterly by the whole team. We base it on a consolidation of the feedback from our users and our strategic plans.