Full Stack Engineer - Evergreen Posting

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to extract content from posting. We have: - About Us (company description) – maybe not needed as a section? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. "About Us" could be considered "About the role"? Actually "About the role" is a heading for description of role. The posting includes a description: "We’re looking for talented Full Stack Software Engineers...". That could go under About the role. Responsibilities: list under "What You’ll Do". That's responsibilities. Requirements: maybe "What You’ll Need". That's requirements. Qualifications: maybe overlapping with requirements; but we can treat "What You’ll Need" as Requirements. Qualifications maybe not separate; but we could include Qualifications if there is specific content like degree, years experience. However we should avoid duplicate. The instruction: prefer few substantive sections over many thin ones. So we can combine Requirements and Qualifications into one? But headings are predefined; we can still include both if they have distinct content. However "What You’ll Need" includes degree, years experience, etc. That's both requirements and qualifications. Could split: Requirements (hard requirements) and Qualifications (preferred). The posting includes "Experience working in or interest in regulated environments (e.g., fintech, healthcare, education) is a plus, but not required" – that's a preferred qualification. Also "Technical Experience (some combination of):" list. That could be Skills. Thus we can have: - About the role: description paragraph(s) about role and mission. - Responsibilities: bullet list from "What You’ll Do". - Requirements: bullet list from "What You’ll Need" (the core requirements: degree, 5+ years experience, full-stack experience, customer-first mindset, care for craft, CI/CD comfort, collaboration, communication). Also maybe include "Bachelor’s degree..." etc. - Qualifications: bullet list for preferred qualifications: experience in regulated environments (plus), maybe also "Technical Experience (some combination of):" but that is more Skills. - Skills: bullet list for technical experience: languages/frameworks, frontend, databases, cloud, devops. - Benefits: bullet list from "What We Give in Return": Competitive cash and equity compensation, Health benefits (medical, dental, vision) and 401(k), Commuter benefits, Flexible PTO policy, Collaborative mission-driven team with strong technical mentorship, Opportunities to grow your skills and career as Clasp scales. - Pay: salary range: $135,000 to $165,000 annually, plus equity component. Also mention competitive cash and equity compensation. We'll include that. - Schedule: remote policy details: limiting to Eastern/Central timezones, expectation Boston hours, must be within 1 hour of medium/large airport with multiple daily flights to Boston, targeting broader New England area, frequent travel to Boston for onboarding and ongoing collaboration. Also note no visa sponsorship. That's schedule/location info. We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Closing" section that talks about senior designer (mismatch) – that seems like a mistake; but it's part of posting. It says "Closing If you are a senior designer who cares about craft..." That's irrelevant to Full Stack Engineer; but it's still content. However it's likely a boilerplate mistake; but we should preserve ALL substantive information; do not invent or summarize away detail. Should we include it? It's not relevant to the role but it's in the posting. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include it if it's substantive. However it's mismatched; but it's still in the posting. It might be considered boilerplate? It's not navigation/legal/EEO/etc. It's a closing paragraph encouraging applicants. It's somewhat generic but still part of posting. The instruction also says remove duplicated lines, and application instructions. This closing includes a call to action: "Join us in connecting healthcare students with meaningful careers..." That's application encouragement. Might be considered application instructions? It's not explicit instruction to apply, but it's encouraging. Safer to maybe include it under About the role? But we already have About the role. Could incorporate as part of About the role description. However the instruction says do not repeat job title as heading; we can include paragraphs. We need to output only HTML fragment, no markdown fences. We'll structure:

About the role

... paragraphs ...

Responsibilities

• ... each bullet ...

Requirements

• ... each bullet ...

Qualifications

• ... each bullet ...

Skills

• ... each bullet ...

Benefits

• ... each bullet ...

Pay

... salary range and equity ...

Schedule

... remote policy ...

We must ensure we don't include empty sections. All have content. Now extract precise bullet points. From "What You’ll Do": - Build, enhance, and maintain features across our application management and loan repayment platform, contributing to both frontend and backend systems - Leave the codebase and systems better than you found them by improving clarity, reliability, documentation, and developer experience as you work - Develop polished, accessible user experiences for students and administrators, and reliable APIs for internal and external partners - Build with a strong sense of customer empathy, considering usability, accessibility, and long-term maintainability in everyday engineering decisions - Collaborate with product managers, designers, and fellow engineers to understand requirements and translate them into well-designed, maintainable solutions - Write high-quality, well-tested code and participate in code reviews to continuously improve team standards - Contribute to system reliability and performance by improving existing services, fixing bugs, and addressing technical debt - Participate in our DevOps culture by owning the services you build, supporting deployments, and helping maintain production stability - Learn and grow by taking on increasingly complex problems over time, with support and mentorship from senior engineers - Participate in on-call rotations as needed, contributing to resilient, observable, and well-monitored systems That's 10 bullets. From "What You’ll Need": - Bachelor’s degree in Computer Science, Software Engineering, Information Systems, or equivalent practical experience (bootcamp or professional experience) - 5+ years of experience building web applications in a production environment (startup or fast-paced product team preferred) - Experience contributing to full-stack systems, including frontend, backend, and basic cloud infrastructure - A customer-first mindset and a sense of ownership over the quality and durability of the work you ship - Care for craft—taking pride in improving existing systems, not just shipping new features - Comfort working with modern CI/CD pipelines and deployment workflows (e.g., GitHub Actions, CircleCI, Jenkins) - Ability to collaborate effectively with cross-functional partners and communicate technical ideas clearly - Experience working in or interest in regulated environments (e.g., fintech, healthcare, education) is a plus, but not required That's 8 bullets. The last is a plus; we could put that under Qualifications. Thus Requirements could be first 7 (excluding the plus). Qualifications could be the plus. But also there is "Technical Experience (some combination of):" which is a list of languages/frameworks etc. That's Skills. Let's extract Skills: Languages & Frameworks: JavaScript / TypeScript, React, Next.js, Python (Django, Flask, FastAPI, or similar) Frontend: HTML, CSS, responsive design principles; familiarity with Figma designs Databases: SQL (PostgreSQL preferred) Cloud: AWS or Google Cloud DevOps: CI/CD pipelines, basic cloud and container tooling We could format each as bullet: maybe combine into one bullet per category. Thus Skills bullets: - Languages & Frameworks: JavaScript / TypeScript, React, Next.js, Python (Django, Flask, FastAPI, or similar) - Frontend: HTML, CSS, responsive design principles; familiarity with Figma designs - Databases: SQL (PostgreSQL preferred) - Cloud: AWS or Google Cloud - DevOps: CI/CD pipelines, basic cloud and container tooling Now Benefits: From "What We Give in Return": - Competitive cash and equity compensation - Health benefits (medical, dental, vision) and 401(k) - Commuter benefits - Flexible PTO policy - A collaborative, mission-driven team with strong technical mentorship - Opportunities to grow your skills and career as Clasp scales That's 6 bullets. Pay: From Salary paragraph: "The salary range for this position is competitive and will be commensurate with the candidate's experience, qualifications, and industry knowledge, ranging between $135,000 to $165,000 annually. In addition to the base salary, we offer an attractive equity component as part of our compensation package, providing an opportunity for eligible employees to share in the success and growth of our company. We are committed to offering competitive compensation and benefits packages to attract and retain top talent." We should keep that as a paragraph. Schedule/Remote Policy: From Remote Policy paragraph: "To ensure smooth collaboration with the Boston-based team, we are limiting to Eastern/Central timezones with the expectation that it will be Boston hours. Additionally, they must be within 1 hour of a medium hub/ large airport with multiple daily flights to Boston. We are targeting the broader New England area to start as we expect that the candidate to have frequent travel to Boston for onboarding and ongoing collaboration." Also note visa sponsorship note: "Please note: We are not able to provide visa sponsorship of any kind at this time, including for current or future employment." That's not schedule but a constraint; could be included in Schedule paragraph or maybe as a note. It's substantive; we should include it. Could add to Schedule paragraph. Thus Schedule paragraph includes timezone, location, travel, no visa sponsorship. Now About the role: we need to combine the initial description paragraphs: "About Us Clasp is a venture-backed, mission-driven startup transforming access to education and career pathways. We are revolutionizing the way employers attract and retain critical talent and the way colleges and universities support their students through education financing — all while tackling the student debt crisis. (Yep, we think BIG.) We like to think of ourselves as more than a fintech; we're a catalyst for economic mobility. A Forbes Fintech 50 company, portfolio company of SHRM (Society of Human Resource Management — the world's largest HR professional society), and one of Business Insider's "43 Start-Ups to Bet Your Career On in 2025," Clasp is driven by our commitment to social impact and innovation. Full Stack Engineer - Evergreen Posting This posting is evergreen, meaning we're building a pipeline of strong candidates for anticipated openings on this team rather than filling a single, immediate role. We may reach out now or in the future as positions become available. Please note: We are not able to provide visa sponsorship of any kind at this time, including for current or future employment. We’re looking for talented Full Stack Software Engineers to join our Engineering team as we scale our product to serve tens of thousands more students and expand partnerships with alternative education providers and employers. This role is ideal for an engineer who enjoys building end-to-end features, collaborating closely with product and design, and growing their technical depth in a production environment. We