At a Glance
- Tasks: Join us to develop innovative software solutions and tackle real customer challenges.
- Company: Dynamic startup with a culture of ownership and creativity.
- Benefits: Flexible work environment, competitive salary, and opportunities for professional growth.
- Other info: Collaborative team with a focus on innovation and minimal meetings.
- Why this job: Make a significant impact on products used by thousands of users daily.
- Qualifications: Experience in full-stack development and a passion for problem-solving.
The predicted salary is between 63000 - 77000 £ per year.
We’re looking for an ambitious full‑stack engineer who is laser‑focused on solving customer problems and making the right long‑term investments to solve them not only today but in our future features and products. What Ashby gives you in return is the best of both early and growth‑stage environments. The agency and no‑nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost‑no‑meeting culture. While also the product‑market fit and scale of a growth‑stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature.
Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end‑to‑end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more.
As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform "Calendar Tetris" to find who is available to interview the candidate, schedule on the earliest date possible, and make any last‑minute adjustments as availability changed.
Software Engineers come in many flavours, not all of which fit our model. Here are some things to help you decide if this fits you and what you’re looking for:
- You’re not afraid to tackle any part of a technology stack.
- You’ve tackled projects with a lot of product and technical ambiguity.
- You know how to strike the right balance between speed and quality.
- You are ambitious and always looking to improve your skills.
- You’re an excellent collaborator and communicator.
- You seek to create leverage in your work.
Put another way, you shouldn’t apply if:
- You need company‑driven process and structure to get your projects across the finish line.
- You’d rather focus on the technical details and challenges.
- You like everything to be planned upfront.
- You haven’t led or taken ownership of projects before.
- You want to mentor earlier‑career engineers.
Our Engineering Culture is motivated by the belief that a small, talented team, given the right environment, can build high‑quality software fast. We do it through minimal process with ownership over decisions normally made by product and design, natural collaboration and deliberate communication, and investing in tools and abstractions that give us leverage.
Senior Software Engineer, Product Engineering, UK in Cambridge employer: Ashby
At Ashby, we pride ourselves on fostering a dynamic and inclusive work culture that empowers Design Engineers to thrive. With a commitment to minimal process and maximum ownership, our team enjoys the unique opportunity to shape a product that impacts over 100,000 users weekly, while benefiting from continuous growth and collaboration in a supportive environment. Join us in creating innovative solutions that not only meet user needs but also push the boundaries of design and technology.
StudySmarter Expert Advice🤫
We think this is how you could land Senior Software Engineer, Product Engineering, UK in Cambridge
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Ashby or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Ashby.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Ashby.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Ashby that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Senior Software Engineer, Product Engineering, UK in Cambridge
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Ashby.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Ashby and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Ashby
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Ashby uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.
