You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
14 days ago
warning
Heads-up
Requirements and responsibilities
Hi 👋🏾 I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for a versatile, persistent product engineer who’s not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so. At Ashby, all our engineers ship features end-to-end at a high pace. Example is the best leadership. We’ll give you the room to do your best work, and you'll be our guide! If that speaks to you, read on.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.We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best-in-class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. We’ll share more details once we meet.You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).About the Role and How We WorkOur 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. 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.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 BuildingScheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others.So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with.Why You Should or Shouldn’t ApplySoftware 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. 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. 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.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.Put another way, you shouldn’t apply if: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.You need company-driven process and structure to get your projects across the finish line.You only want to do exciting work. Customer issues and investigations are distributed across the team.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 haven’t led or taken ownership of projects before.You want to mentor earlier-career engineers. Mentorship opportunities are very limited.Engineering CultureOur engineering culture is motivated by Benji’s and my belief that a small, talented team, given the right environment, can build high-quality software fast (and work regular hours!). We do it through:Minimal process with ownership over decisions normally made by product and designNatural collaboration and deliberate communicationInvesting in tools and abstractions that give us leveragePutting effort into building a diverse teamMinimal Process & Lots of OwnershipAt Ashby, every Engineer runs their project. Product Managers (and Designers) build strategy, do customer research, and hand off problem briefs to Engineers. Engineers take on the rest: they research the problem, write product specs, build wireframes, and implement their solution end-to-end.Collaboration is Natural & Communication is DeliberateFocus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in <2h meetings per week.We also meet in person at least twice a year, once as a department and once as a company. You also have a small budget to meet up with folks in your city/region.Increase Leverage, not Team SizeWe’ve done this through investment in:Great developer tooling. CI/CD takes ~10m, and we deploy at least 15x a day.Building blocks to create powerful and customizable products fast. Common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve.AI-powered tooling. Auto-triage customer issues, suggest fixes, prototype ideas, generate production-ready code, and conduct code reviews.Put Effort into DiversityDiverse teams drive innovation and better outcomes. Today, 25% of engineers and 50% of our engineering leaders at Ashby are from underrepresented groups. We are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more.Interview ProcessThere are no leetcode or whiteboard exercises. Our interview process is three rounds:Introduction call with Hiring Manager (15 to 30m, live)A technical screen where we pair in our actual codebase (1h, live)Three non-coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days)Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter.Your hiring manager will be your main point of contact and prep you for interviews.Your First Three Months at AshbyYour dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. Your manager will do a 30, 60, and 90-day review to give feedback.It’s a team effort to get you successfully onboarded; you’ll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.Technology StackTypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.BenefitsCompetitive salary and equity.10-year exercise window for stock options. (You shouldn’t feel pressure to purchase stock options if you leave Ashby.)Unlimited PTO, and we will encourage you to take it.A minimum of 12 weeks of fully paid parental leave, covered by Ashby. For folks outside the US, it may be longer to be in line with regional requirements.Generous equipment, software, and office furniture budget.$100/month education budget with more expensive items (like conferences) covered with manager approval.If you’re in the US, top-tier health insurance for you and your dependents, with 100% of premiums covered by Ashby. In other countries, high-quality supplemental health insurance for you and your dependents, also fully covered by us.
Optionally, you can add more information later (benefits, pre-screening questions, etc.)