Product Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Artos", "The Role", "What You’ll Do", "What We’re Looking For", "Nice to Have", "You’ll Be Successful If", "Other Information". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - About Artos: description of company. Could map to "About the role"? Actually "About the role" is a heading for role description. But we have "About Artos" which is company overview. Could we treat as "About the role"? Not exactly. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those categories. We have: - Responsibilities: "What You’ll Do" list. - Requirements/Qualifications: "What We’re Looking For" (required) and "Nice to Have" (preferred). Could combine into Requirements and Qualifications? Might split: Requirements (must-have) and Qualifications (nice-to-have). Or we could have Requirements section for must-have, and Qualifications for nice-to-have. - Skills: maybe not explicit separate; could be part of requirements. - Benefits, Pay, Schedule: Not mentioned except "Other Information" includes: Very comfortable working in a fast-paced and intense startup environment; Willing to work in-person in our office in Mission Bay 4-5 days/week; Likes matcha KitKats, believes every LLM prompt is just Schrödinger’s cat waiting to be observed, and knows too many random facts about the Mongol postal system. That's not benefits/pay/schedule. No explicit benefits, pay, schedule. So we should NOT create those sections. Thus we will have sections: About the role? Actually we have About Artos description; could be placed under About the role? Might be better to have a section "About the role" containing the role description (The Role). But we also have About Artos separate. Could we combine About Artos into About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid having an About the company section. But they gave examples of headings; maybe we can still use other headings if needed? Safer to stick to given headings. We could treat About Artos as part of About the role (maybe a brief intro). But we have separate "The Role" heading which is basically role overview. So we could map: - About the role: combine About Artos + The Role? Might be odd but okay. - Responsibilities: What You’ll Do. - Requirements: What We’re Looking For (must-have). - Qualifications: Nice to Have. - Skills: maybe not needed; could omit. We must not create empty sections. So we will include About the role, Responsibilities, Requirements, Qualifications. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Requirements (must-have) we need a list. For Qualifications (nice-to-have) we need a list. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include each bullet point exactly as given, maybe as list items. Let's extract content. About Artos: "At Artos, we build tools that help biopharma companies create and manage their R&D documentation in a fraction of the time. If you’re looking to join a team whose mission is to fundamentally change the way that drug development gets done, we’d love to talk to you." The Role: "We’re looking for a technically strong Product Manager to help drive the development, delivery, and continuous improvement of the Artos platform. You’ll work closely with our founders, Engineering, and customer-facing teams to translate product requirements into well-defined, tested, and production-ready functionality. This is a hands-on role combining product management with technical project management. You’ll help define requirements, coordinate development, establish product analytics, and ensure that what we build delivers meaningful customer outcomes. You’ll also help establish the processes that support how we develop software, bringing structure and visibility to a fast-moving engineering organization without introducing unnecessary bureaucracy." What You’ll Do (Responsibilities): list: - Own the product lifecycle for assigned features, from requirements and development through testing, validation, and release. - Partner with Engineering and customer-facing teams to translate product ideas and customer needs into clear specifications and acceptance criteria. - Work with our founders and technical leadership to support product prioritization and translate strategic direction into executable development plans. - Coordinate feature testing, ensuring the right stakeholders, datasets, and validation criteria are in place. - Define and implement product analytics to measure adoption, evaluate feature performance, and identify opportunities for improvement. - Track features, bugs, dependencies, blockers, and outstanding decisions across the development lifecycle. - Maintain clear product documentation, testing results, known limitations, and release notes. - Establish lightweight, repeatable processes that improve collaboration, accountability, and visibility across teams. What We’re Looking For (Requirements): list: - 4+ years of relevant professional experience, including both software engineering and product management. - Previous hands-on experience as a software engineer. - Experience building and shipping B2B software products as a Product Manager. - Strong understanding of the software development lifecycle, including requirements, development, testing, and release. - Technical fluency and the ability to engage meaningfully with engineers on architecture, APIs, data, and technical trade-offs. - Experience translating ambiguous requirements into structured, actionable development plans. - Experience defining product metrics and using analytics and customer feedback to drive improvements. - Strong organizational, communication, and documentation skills. - A bias toward ownership and the ability to drive cross-functional work through completion. - Comfort operating in an early-stage startup where priorities evolve and processes are still being built. Nice to Have: list: - Experience building AI-native or LLM-powered enterprise products. - Familiarity with LLMs, RAG, AI agents, or evaluation frameworks. - Experience in pharmaceutical, biotech, life sciences, or other highly regulated industries. - Previous startup or founder experience. - Experience establishing product development processes within an early-stage company. You’ll Be Successful If: paragraph: "Engineering has clearer requirements, features are consistently tested and validated, product decisions are supported by meaningful data, and teams have better visibility into development. Most importantly, you’ll help Artos build a more efficient and scalable product development organization while ensuring the functionality we ship delivers real value to our customers." Other Information: list-ish: "Very comfortable working in a fast-paced and intense startup environment; Willing to work in-person in our office in Mission Bay 4-5 days/week; Likes matcha KitKats, believes every LLM prompt is just Schrödinger’s cat waiting to be observed, and knows too many random facts about the Mongol postal system." We need to decide if we include "You’ll Be Successful If" and "Other Information". They are not in the prescribed headings but could be considered part of Responsibilities or Requirements? Probably not. The instruction says prefer a few substantive sections over many thin ones. We could incorporate "You’ll Be Successful If" into Responsibilities or maybe as a separate section like "Expectations"? But not in list. Could we omit it? It is substantive; we should preserve. Maybe we can include it under a section like "Success Metrics" but not in allowed headings. However we could treat it as part of Responsibilities (outcomes). Or we could create a section "Expectations" but not in allowed list; risk of being considered not following instruction. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we could use other headings if needed, but better to stick to those. However we can incorporate the success criteria into Responsibilities as bullet points? It's more of outcome. Could add as a paragraph under Responsibilities. Other Information: includes work schedule (in-person 4-5 days/week) and personal quirks. The schedule is mentioned: "Willing to work in-person in our office in Mission Bay 4-5 days/week". That's schedule info. So we could create a Schedule section with that detail. Also "Very comfortable working in a fast-paced and intense startup environment" could be part of Requirements or Qualifications? It's more about environment preference. Could be part of Requirements (maybe as a soft skill). The quirky personal statements are not relevant to job; but they are substantive? Might be considered fluff; but we must preserve ALL substantive information. However they are not really job-related; but they are in posting. Should we keep? Probably yes, but we could put them in a short paragraph under Other Information or maybe under About the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not boilerplate; it's personal quirks. Might be considered irrelevant but still substantive. We'll keep. We could create a Schedule section with the in-person days. Also we could include a Benefits section? No benefits mentioned. So we skip Benefits and Pay. Thus sections: About the role (company + role overview), Responsibilities, Requirements, Qualifications, Schedule. We need to use

    for each section heading. Inside each section, we need to use

    for prose and

    • for lists. For About the role: we have two paragraphs: About Artos and The Role. Could combine into one

      containing both sentences? Better to keep as two

      elements. For Responsibilities: list of 8 items. For Requirements: list of 10 items. For Qualifications: list of 5 items. For Schedule: we have "Willing to work in-person in our office in Mission Bay 4-5 days/week". Also "Very comfortable working in a fast-paced and intense startup environment" maybe also schedule/environment. Could be part of Schedule or maybe a separate section like "Work Environment". But we can put both in Schedule as a list? Actually schedule is about days; environment is about comfort. Could be separate

      items. We'll create Schedule section with a

      for each sentence. Now ensure we don't repeat job title as heading. We don't have job title. Now output only HTML fragment. Let's craft.

      About the role

      At Artos, we build tools that help biopharma companies create and manage their R&D documentation in a