Staff Product Engineer - Americas

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Need to extract content from posting. Let's parse the posting. It starts with intro from Abhik, then "What Ashby gives you in return..." etc. Then "About The Role And How We Work". Then a long description of engineering culture, examples, etc. Then "What We’re Building". Then "Why You Should or Shouldn’t Apply" with bullet points (list). Then "Engineering Culture" with subsections: Minimal Process & Lots of Ownership, Collaboration is Natural & Communication is Deliberate (cut off). Also earlier sections: "About At Ashby, we’re building an environment..." etc. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to see if posting includes specific content for each. - About the role: Likely the section "About The Role And How We Work" and maybe "About At Ashby, we’re building an environment..." That's about role and work. So we can put that under About the role. - Responsibilities: The posting includes examples of what product engineers have done: designed and built automated interview scheduling, built generalized declarative filter architecture, specced, designed, and implemented a feature for signing offers. Also description: "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." That's responsibilities. - Requirements: The "Why You Should or Shouldn’t Apply" lists traits: not afraid to tackle any part of stack, tackled projects with product and technical ambiguity, balance speed and quality, ambitious, excellent collaborator, seek to create leverage. Also "You’re not afraid to tackle any part of a technology stack." etc. Those could be requirements or qualifications. Also "You’ve probably seen this role posted before..." not needed. - Qualifications: Might be similar to requirements. Could combine? But we need separate sections only if there is real specific content. The posting doesn't explicitly list qualifications like years of experience, degree, etc. So maybe we skip Qualifications. - Skills: Could list technical skills: full-stack, frontend/backend, infrastructure, design system, SRE, etc. Not explicit list but implied. Might be thin. - Benefits: The posting mentions "What Ashby gives you in return is the best of both early and growth-stage environments." Then describes agency, no-nonsense, product-market fit, scale, notable customers, growth metrics, tens of millions ARR, >100% YoY, low churn, many years runway. Also "We’ll share more details once we meet." Also "We read every application and aim to respond within 3-4 days." That's more about process. Benefits could be described: autonomy, impact, high growth, notable customers, etc. So we can include Benefits. - Pay: No specific pay mentioned. So skip Pay. - Schedule: No mention of schedule (e.g., remote, hours). So skip Schedule. Thus we will output sections: About the role, Responsibilities, Requirements (maybe combine with Qualifications?), Benefits. Possibly Skills if we can extract. Let's extract specific content for each. About the role: Combine paragraphs under "About The Role And How We Work" and maybe "About At Ashby, we’re building an environment..." but that is more about environment. However we can put that under About the role as description of role and work environment. Let's capture: "About The Role And How We Work 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. 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. About 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." That seems good. Responsibilities: The bullet examples: "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." Also earlier: "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." We can combine. Requirements: The "Why You Should or Shouldn’t Apply" bullet list (the positive side). Let's extract those bullet points: - 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. Also maybe "You’ve probably seen this role posted before..." not needed. We could treat these as Requirements. Skills: Could list specific skills: full-stack development, frontend/backend, infrastructure, design system, SRE, product spec writing, wireframing, competitor research, SQL, etc. But not explicit list. Might be thin. Safer to omit Skills. Benefits: Extract from "What Ashby gives you in return is the best of both early and growth-stage environments." Then details: - 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: 100,000+ weekly active users who depend on your software and eagerly await your next feature. - Notable customers like Notion, Linear, Shopify, and Snowflake. - 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. - We read every application and aim to respond to yours within 3-4 days (often sooner). Also maybe "We’ll give you the room to do your best work, and you'll be our guide!" That's more about culture. We can put Benefits section with those points as list. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not repeat job title as heading. Not include Job ID etc. We must not include boilerplate like EEO etc. Not present. We must not create sections with filler like "commensurate with experience". Not present. We must ensure we only include sections with real content. Thus output:

  About the role

  ... (the combined paragraph)

  Responsibilities

  • ... each responsibility as li

  Requirements

  • ... each requirement as li

  Benefits

  • ... each benefit as li
  We need to ensure we preserve all substantive information, not invent or summarize away detail. So we need to keep the details as close as possible. Let's craft the About the role paragraph: Use the text we captured, maybe split into multiple paragraphs for readability but still within

  . Could be multiple

  tags but rule says use

  for prose. Could have multiple

  under same heading? Probably okay. We'll just put one

  with the combined text, but ensure we keep line breaks? HTML will ignore line breaks. It's fine. Responsibilities: We'll create

  with
  • items: - 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). Research competitors, write product specs, make wireframes, and more. - Designed and built automated interview scheduling: 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; 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: involved talking to customers to understand requirements, deciding technologies, building a prototype, working with other team members