INTERVIEW PROCESS (<2 WEEKS)

• Application: We’re looking to see how your skills and experience align with our needs.
• Culture interview (30 min video call): Our goal is to explore your motivations to join our team, learn why you’d be a great fit, and answer questions about us.
• Technical interview (45 min video call): You’ll meet your manager who will evaluate skills needed to be successful in your role. Varies by role.
• Sailia Sea Trial (Paid day of work): You’ll meet a few more members of the team and work on an independent project. It’s challenging and fun! (£200 for a full day)
• Offer: Time to celebrate (Once you’ve signed).

WHO WE’RE LOOKING FOR

We’re hiring two Product Engineers to join the founding team.
We’re looking for at least one person who is heavily design focused and can make assets too

REQUIREMENTS

• Strong understanding of web application architecture
• Full-stack experience with technologies. e.g. PHP or similar, Python or similar, JS/React or similar, Git. Experience with logic and complex systems
• Experience taking a project from 0 to 1. You might have led a project, been a founder previously, or built an impressive side project.
• Strong writing skills. The ability to communicate your ideas and make persuasive arguments is essential.

• Building new features. Owning products and features from beginning to end. This means originating ideas based on your intuition, talking to users, and understanding our strategy and goals. It means testing MVPs in production with real users. It means iterating on their feedback, owning pricing, and ensuring the ongoing success of your work.
• Talking to users. Good product engineers read feedback from users and iterate quickly. Great product engineers have users they’re friendly with, talk with them frequently, bounce ideas off them, and iterate with them when they ship new things.
• Doing support. Giving users support from real engineers, and shipping fixes and improvements in real-time, is one of the best ways to spark joy in users. This role will also include some on-call time too.
• Writing docs. The best person to document a new feature is the person who built it.