serp_jobs.error_messages.no_longer_accepting

Senior Software Engineer - Product Engineering, EMEA (Alloway)

AshbyAlloway, NJ, US

job_description.job_card.variable_hours_ago

serp_jobs.job_preview.job_type

serp_jobs.job_card.part_time

job_description.job_card.job_description

About The Role And How We Work

Our engineering culture strives to recreate the environments where we did our best work as individual contributors - where we had the ownership and agency to impact our users with creative and innovative software.

I started my career building software for artists in the visual effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand-ups, no t-shirt sizing, no planning meetings.

I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.

Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer's force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of Agile processes like sprint planning. In those companies, I felt like a JIRA jockey.

At Ashby, we're building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. 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. To ground it with examples, product engineers at Ashby have :

Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the Calendar Tetris problem I talk about in What We're Building.
Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user-facing features use it.
Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features.

What We're Building

Talent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. To accomplish this, recruiters perform thousands of daily tasks to coordinate and relay information between candidates, interviewers, and hiring managers. Teams struggle to keep up!

Scheduling a final round is an excellent example of our customers' challenges. A recruiter needs to collect availability from the candidate, identify potential interviewers, perform Calendar Tetris to find who is available to interview the candidate, schedule on the earliest date possible, and perform any last-minute adjustments as availability changes. They must perform this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. ????

Ashby provides talent teams with intelligent and powerful software that provides insights into where they're failing and automates or simplifies many of the tasks they're underwater with. We put a lot of effort into designing products that are approachable to beginners but mastered and extended by power users. In many ways, spreadsheets set the bar here (and are what we often replace!).

Why You Should Or Shouldn't Apply

Software engineers come in many flavors, 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 do what's necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We'll provide a supportive environment to do it successfully (e.g., design system, SRE team).

You've tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We're not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.

You know how to strike the right balance between speed and quality. Ashby wasn't built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn't infinite, especially for a startup, so we still move with urgency-we've built the equivalent of three or more VC-backed startups with a very small team.

You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you've experienced in the past. To thrive (and level up), you'll need to be open to feedback (and we give lots of it).

You're an excellent collaborator and communicator. Ownership and freedom don't mean you work in a vacuum. You'll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!

You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow support to debug before engineering, new lint rules to prevent common bugs, etc.

Put another way, you shouldn't apply if :

You need company-driven process and structure to get your projects across the finish line. Sprint planning and well-defined project management processes are things you need or look to others to lead. You'd rather focus on the technical details and challenges.

You only want to do exciting work. We're building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.

You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.

You haven't led or taken ownership of projects before. You're used to working with tech leads and taking on tasks distributed by them.

You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.

To you, a tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it's not a requirement, nor do engineers need their sign-off.

Engineering Culture

Our engineering culture is motivated by Benji's (my co-founder and CEO) and my belief that a small talented team, given the right environment, can build high-quality software fast (and work regular hours!).

Collaboration Is Natural & Communication Is Deliberate

Our engineering team (and the team at large) consists of lifelong learners who are humble and kind (meet them here!). These attributes create an environment where collaboration happens naturally (we filter for it in interviews). We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in

Increase Leverage, Not Team Size

We built Ashby with the quality, breadth, and depth that many customers would expect from much larger teams over larger time scales. We've done this through investment in :

Great developer tooling. Our

serp_jobs.job_alerts.create_a_job

Senior Software Engineer • Alloway, NJ, US