Senior Software Engineer, Product Engineering, UK

Requirements

• experience for me as a software engineer because success relied on my ability to be a product manager and designer.
• I studied computer science to solve problems, not tickets, and this felt exactly like that.
• In those companies, I felt like a JIRA jockey.
• 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.
• 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.
• So, we built and continue to build Ashby to give TA teams the highest standard of tooling.
• Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with.
• 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.
• 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.
• At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve.
• Each improvement to a common component cascades throughout our app (short video below). - AI-powered tooling.
• We think of AI as a way to automate the mundane parts of building and maintaining high-quality software.
• We write in detail about our philosophy, current use of AI, and future plans for AI in Engineering here https://www.ashbyhq.com/blog/engineering/ai-ashby-engineering-and-the-future.
• There are no leetcode or whiteboard exercises.
• At Ashby, your 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.
• experience in it (but a love of typed languages is helpful 😀): TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.