Solutions Engineer, Post-Sales (remote, US East Coast)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the job posting. Let's extract sections: - About the role: The first paragraph describing role? "This role starts where the sale ends. You will onboard new customers, train their engineering teams, and stay close to those accounts as their use of Checkly grows. You are the technical counterpart in the account, and you run your own customer meetings." Also earlier description about Checkly. Probably "About the role" includes description of role and company context. - Responsibilities: bullet list of duties: "You will learn Checkly and the monitoring space deeply, then help customers solve real reliability problems. You will own technical onboarding for new accounts: implementation, configuration, and getting their first monitoring into production. You will run workshops and trainings for customer engineering teams. You will be the technical counterpart in existing accounts, supporting adoption, troubleshooting, and growth alongside the sales team. You will run your own customer meetings, from technical deep dives to account check-ins. You will contribute to technical documentation and internal playbooks as you learn what works. You will speak with customers directly and share your learnings with Product Engineering and Marketing." - Requirements: maybe "Around 2 years of experience in a post-sales technical role: customer onboarding, workshops and trainings, and helping accounts grow. Solutions engineering, professional services, customer success engineering, technical account management, or a similar path all work. Hands-on experience with monitoring, observability, or automated testing. Strong technical skills that allow you to read, write, and debug code (Javascript/Node.js preferred). Ability to use AI tools to accelerate customer-facing work: researching a customer's stack, generating tailored example code, building proof-of-concept repos, drafting technical responses. We build with Claude Code, Codex, and similar tools. Genuine interest in working directly with customers. You enjoy talking to people, running workshops and demos, driving a meeting yourself, and explaining technical concepts clearly. Excellent spoken and written English skills Ability to be autonomous and self-motivated in an async-work environment, while you also enjoy getting to know your colleagues and helping others. Based on the US East Coast, in Eastern Time (ET). Able to travel occasionally to customers. Startup experience is helpful, but not required." - Qualifications: Might overlap with requirements. Could separate: maybe "Qualifications" includes education? Not present. Could skip Qualifications if no distinct content. - Skills: maybe "Hands-on experience with monitoring, observability, or automated testing. Strong technical skills that allow you to read, write, and debug code (Javascript/Node.js preferred). Ability to use AI tools to accelerate customer-facing work: researching a customer's stack, generating tailored example code, building proof-of-concept repos, drafting technical responses. We build with Claude Code, Codex, and similar tools. Genuine interest in working directly with customers. You enjoy talking to people, running workshops and demos, driving a meeting yourself, and explaining technical concepts clearly. Excellent spoken and written English skills Ability to be autonomous and self-motivated in an async-work environment, while you also enjoy getting to know your colleagues and helping others." But we need to avoid duplication. The instruction: Use sections only when posting has real specific content. We can combine overlapping content into appropriate sections. Typically: About the role (overview), Responsibilities (duties), Requirements (experience needed), Qualifications (maybe education/certifications), Skills (technical skills), Benefits, Pay, Schedule. We have info about Pay: "Fair, competitive, and transparent pay is very important for us. Therefore we work with a standardized salary calculator that includes several factors such as seniority level as well as location. For this role, there’s a 70% base salary - 30% commission split. The range is $107k-$155k OTE for someone in the US. $134k-$185k OTE for someone in US Tier 1 locations like NYC, Boston." Also later "Compensation Range: $80K - $185K". There's some inconsistency. We need to preserve all substantive info; do not invent or summarize away detail. So we should include both statements? The posting includes both a description and then a compensation range line. We should include both as they are substantive. However we must avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include both pieces, even if they overlap. We can include them in the Pay section as separate sentences. Benefits: "Transparent salary (more info below)Become part of a fast-growing, and international team where your work matters. Your impact won’t get lost in layers of bureaucracy. Stock optionsFlexible paid vacationPaid sick leave & up to 14 weeks of paid parental leaveUS: Medical, Dental, Vision, FSA, long- and short-term disability, life insurance, 401(K) and moreAnnual company on-site Find out more here." We need to parse benefits: Stock options, Flexible paid vacation, Paid sick leave & up to 14 weeks of paid parental leave, US: Medical, Dental, Vision, FSA, long- and short-term disability, life insurance, 401(K) and more, Annual company on-site. Also "Transparent salary (more info below)" maybe part of benefits but we already have Pay. Schedule: Not explicitly mentioned. There's "Based on the US East Coast, in Eastern Time (ET). Able to travel occasionally to customers." That's location, not schedule. No explicit schedule like full-time, remote, etc. The posting mentions remote? At top: "(Remote, US East Coast, Series B DevTools SaaS, synthetic monitoring)". So remote work. Could we infer schedule? Not given. Should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time", "40 hours/week". So we should omit Schedule. Now we need to output HTML with headings

for each section. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which content goes into lists vs paragraphs. Responsibilities: list of duties ->

  • each duty. Requirements: list of experience/qualifications -> could be list. Skills: maybe list. Benefits: list. Pay: prose. About the role: prose. We must not repeat job title. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes lines like "Apply If this sounds interesting, please apply! Studies by several different sources..." That's application instructions and encouragement to apply; we should remove that. Also "We'd love to hear from you! We're all about being transparent..." etc. Also "Find out more here." etc. Also "Compensation Range: $80K - $185K" maybe part of pay but it's near the end; we can keep as part of Pay. We need to ensure we don't include any application instructions like "Apply If this sounds interesting, please apply!" etc. Also "Studies by several different sources..." etc. Also "We'd love to hear from you!" etc. Also "We're all about being transparent..." etc. Also "Find out more here." etc. Also "If you're not sure you're the right fit, apply anyway..." etc. Also "We'd love to hear from you!" etc. Also "We're all about being transparent..." etc. Also "That's why we've put together our hiring playbook and open-sourced our employee handbook." etc. Also "Compensation Range: $80K - $185K" maybe keep as part of Pay. We need to preserve all substantive information: that includes the description of role, responsibilities, requirements, skills, benefits, pay. Also the location (Remote, US East Coast) maybe part of About the role or Requirements? It's location requirement. Could be in Requirements (Based on US East Coast). We'll include that in Requirements. Now let's extract substantive content precisely. Original text: "(Remote, US East Coast, Series B DevTools SaaS, synthetic monitoring) The best developers don't wait for a customer to tell them something's broken. They catch it first, in the pull request, in staging, or in the checkout flow at 3am, before a single user notices. That instinct is Checkly's whole reason to exist. We give developers and their agents the tools to own reliability the way they own their code: end-to-end tests and synthetic monitoring defined as code, powered by OpenTelemetry and Playwright, versioned and reviewed like everything else they ship. From pull request to post-mortem, in one place. Thousands of them, from modern AI companies like Mistral and resolve.ai to large engineering orgs like LinkedIn, Citi, and 1Password, build with us. In 2024 we raised $20M in Series B funding from Balderton, CRV and Accel. Here's the thing about 2026: AI agents and coding assistants are shipping more software, faster, than any team could review by hand, and more of it is breaking in ways nobody has seen before. LLM-backed features fail probabilistically. Agents take actions no runbook anticipated. "Is my app healthy?" is becoming an unanswerable question for a whole generation of AI-native software. That’s where you come in. This role starts where the sale ends. You will onboard new customers, train their engineering teams, and stay close to those accounts as their use of Checkly grows. You are the technical counterpart in the account, and you run your own customer meetings." Then "What you’ll do" heading (but we should not repeat heading as h3? Actually we will use our own headings). The content after "What you’ll do": "We're looking for a Solutions Engineer to make sure customers get real value out of Checkly after they sign. You will learn Checkly and the monitoring space deeply, then help customers solve real reliability problems. You will own technical onboarding for new accounts: implementation, configuration, and getting their first monitoring into production. You will run workshops and trainings for customer engineering teams. You will be the technical counterpart in existing accounts, supporting adoption, troubleshooting, and growth alongside the sales team. You will run your own customer meetings, from technical deep dives to account check-ins. You will contribute to technical documentation and internal playbooks as you learn what works. You will speak with customers directly and share your learnings with Product Engineering and Marketing." Then "What you should have": "Around 2 years of experience in a post-sales technical role: customer onboarding, workshops and trainings, and helping accounts grow. Solutions engineering, professional services, customer success engineering, technical account management, or a similar path all work. Hands-on experience with monitoring, observability, or automated testing. Strong technical skills that allow you to read, write, and debug code (Javascript/Node.js preferred). Ability to use AI tools to accelerate customer-facing work: researching a customer's stack, generating tailored example code, building proof-of-concept repos, drafting technical responses. We build with Claude Code, Codex, and similar tools. Genuine interest in working directly with customers. You enjoy talking to people, running workshops and demos, driving a meeting yourself, and explaining technical concepts clearly. Excellent spoken and written English skills Ability to be autonomous and self-motivated in an async-work environment, while you also enjoy getting to know your colleagues and helping others. Based on the US East Coast, in Eastern Time (ET). Able to travel occasionally to customers. Startup experience is helpful, but not required." Then "Why us?" heading: content: "Transparent salary (more info below)Become part of a fast-growing, and international team where your work matters. Your impact won’t get lost in layers