Full Stack Engineer (Laravel)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting and decide sections. Content includes: - Why Join Housr? (company description) -> could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly. We have: - About the role: description of opportunity, what you'll own, what you could work on, our current technology. - Responsibilities: maybe "What You'll Own" bullet list. - Requirements/Qualifications/Skills: "What Good Looks Like In You" bullet list. - Benefits: "What we offer" bullet list. - Pay: mention "A genuinely competitive base salary + stock options/meaningful equity (full details to be shared during initial interview)". That's pay info, though not exact numbers. It's still content. Should we include Pay section? The rule: include a section ONLY when 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. Here they state base salary + stock options, though not specific numbers. Is that considered specific? It says "genuinely competitive base salary + stock options/meaningful equity (full details to be shared during initial interview)". That's somewhat vague but still mentions salary and equity. It's not "commensurate with experience" but it's still vague. However it's still stating they offer salary and equity. I'd include Pay section with that sentence. - Schedule: "The ability to work from our central Chicago office four days a week, with Thursday as the company-wide remote day." That's schedule info. So include Schedule section. We also have interview process details; but instruction says remove application instructions. Interview process is maybe considered application instructions? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Interview process could be considered application instructions. Safer to remove it. Also "Introductory call with Talent partner..." etc. Remove. Also remove duplicated lines? Not seeing duplicates. Now we need to format using

for section headings,

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

  for prose. We need to decide which content goes into which section. Let's outline: Section: About the role (maybe

  About the role

  ) containing prose about why join Housr, opportunity, etc. Could be a few paragraphs. But we also have "What You'll Own" which is responsibilities. Could be under Responsibilities. We have "What You Could Work On" maybe also responsibilities or maybe part of About the role. We have "Our current technology" maybe part of About the role. We have "What Good Looks Like In You" which is requirements/qualifications/skills. Could be split into Requirements and Skills? But we can combine into one section maybe Requirements. However instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Let's map: - About the role: company description, opportunity, tech stack. - Responsibilities: "What You'll Own" bullet list + maybe "What You Could Work On" bullet list (these are duties). Could combine. - Requirements: "What Good Looks Like In You" bullet list (skills, experience). Could also include "Experience in a startup..." etc. - Benefits: "What we offer" bullet list. - Pay: sentence about base salary + stock options. - Schedule: sentence about hybrid work. We must not repeat job title as heading. Good. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's extract details. From posting: Why Join Housr? paragraph: "Housr is a Series A technology company making off-campus student housing simpler for students, parents, colleges and property partners.The company started after co-founders Harry Panter and Ben Clayton experienced first-hand how stressful and outdated student renting could be. Today, Housr operates across the UK and US, with a global team across Manchester, Chicago and New York. In 2025, we reached $10 million in annual recurring revenue and raised a $10 million Series A to support the next stage of growth. Our products help students find properties, book tours, request leases, find roommates and access perks. We also build tools for colleges, parents and property partners. With hundreds of colleges signed and the platform expected to serve up to 750,000 active students over the next year, there is plenty to build and improve." That's substantive. The Opportunity paragraph: "We're hiring our first US-based engineer to join Housr's global product and engineering team. Our US business is growing quickly and the team needs an experienced technical partner working in the same time zone.You'll be based with our wider US team in Chicago while staying closely connected to engineering, product and design colleagues in Manchester, UK. Part of each day will involve working independently while the UK team is offline. You'll be the engineering point of contact for US colleagues, helping them understand what's possible, turning requests into clear technical work and dealing with issues that arise during US business hoursThis isn't a separate US codebase or a support-only position. You'll build the same products, work to the same engineering standards and contribute to planning, code reviews and technical decisions across the wider team." That's also substantive. What You'll Own bullet list (converted to prose? but we need list). Items: - Build and maintain backend services and APIs using modern PHP and Laravel. - Develop web and mobile product experiences across React, Next.js and React Native using Expo. - Deliver US product priorities, integrations and new features alongside work on the wider Housr platform. - Act as the first engineering point of contact for colleagues in the US office, asking the right questions and explaining technical decisions clearly to non-technical people. - Balance planned project work with smaller requests that need a quick response, without losing sight of quality or longer-term priorities. - Work closely with Product and Design, making good use of the daily overlap with the Manchester engineering team. - Review code, share context and help keep the codebase clean, modular and maintainable. - Use AI development tools where they help, while reviewing and validating the output rather than accepting it at face value. What You Could Work On bullet list: - The US roadmap already includes: - The Housr student app and the core property search, tour and lease journeys. - Portals for property partners, colleges and parents. - Upgrading AI tooling across the product stack - Integrations with major US property management platforms. - A new ticketing experience for the US market. - A recently rebuilt student perks portal and further local product improvements as new colleges go live. Our current technology paragraph: "Laravel, React and Next.js, React Native and Expo, MySQL, AWS: EC2, App Runner, CodePipeline, S3 and RDS, AWS Bedrock, MCP and AI-assisted development tools" What Good Looks Like In You bullet list: - Strong commercial full stack engineering experience (ideally 3+ exp of strong ownership) - Strong hands-on experience building backend services and APIs in PHP and Laravel. - Commercial frontend experience with React, ideally including Next.js and/or React Native. - Experience working with AWS and relational databases such as MySQL. - The confidence to work independently for part of the day, make sensible calls and ask for help early when you need it. - Clear communication with technical and non-technical colleagues. You should be comfortable translating in both directions without overcomplicating things. - A practical approach to production issues, prioritization and context switching. - Care for code quality, performance and maintainability, even when the business needs to move quickly. - Comfort using tools such as Cursor, Claude or GitHub Copilot as part of your workflow, alongside sound engineering judgment and QA. - The ability to work from our central Chicago office four days a week, with Thursday as the company-wide remote day. - Experience in a startup, scale-up or distributed engineering team would be useful, particularly if you've previously worked as the main technical contact for a local office. It isn't essential if you can show the same level of ownership in another environment. What we offer bullet list: - A genuinely competitive base salary + stock options/meaningful equity (full details to be shared during initial interview) - Eligibility to participate in Housr's stock option plan, subject to the plan terms. - A hybrid setup with four days in our central Chicago office and Thursday working remotely. - Regular team lunches and company socials. - Direct access to the founders and the chance to influence how engineering develops in the US. - 20 days paid time off plus federal holidays. - 100% employer-paid medical, dental, and vision cover, with options for dependents. - 401(k) match (100% match on first 3%, 50% match on next 2%), life, and disability cover. - Flexibility & trust with autonomy to do your best work and direct access to founders. Interview process: we will remove. Now we need to map to sections. About the role: include Why Join Housr? + The Opportunity + maybe Our current technology? Could be part of About the role. Responsibilities: What You'll Own + What You Could Work On (these are duties). Could be combined. Requirements: What Good Looks Like In You (experience, skills). Could be Requirements. Skills: maybe we could separate but we prefer few sections. Could combine Requirements and Skills into one section called Requirements (or Qualifications). But we have both Requirements and Qualifications headings allowed. We could use Requirements for experience, and Skills for technical skills. However to avoid thin sections, we could combine. But we have separate headings allowed: Requirements, Qualifications, Skills. We could use Requirements for experience (years, ownership), Qualifications for education? Not present. Skills for technical skills. However we have limited content; better to have one Requirements section covering both experience and skills. Benefits: What we offer (excluding pay and schedule? Actually pay and schedule are also in that list but we will separate them into Pay and Schedule sections). So Benefits section will include other benefits: regular team lunches, direct access to founders, 20 days PTO, medical/dental/vision, 401k match, flexibility & trust, eligibility to participate in stock option plan (though that's equity, maybe part of Pay). But we already have Pay section for base salary + stock options. The eligibility to participate in stock option plan is similar; maybe we keep it in Benefits? But to avoid duplication, we could keep stock option mention only in Pay section. The Benefits section can include other items. Pay: "A genuinely competitive base salary + stock options/meaningful equity (full details to be shared during initial interview)". Also maybe mention eligibility to participate in stock option plan? Might be redundant. We'll keep just that sentence. Schedule: "The ability to work from our central Chicago office four days a week, with Thursday as the company-wide remote day." Also note hybrid setup mentioned in benefits; but we will put schedule there. Now we need to ensure we don't create sections with filler. All sections have real content. Now produce HTML fragment. We'll need to wrap each section:

  About the role

  then

  ... maybe multiple paragraphs. For lists:

  • ...
  . We must not include any extra text outside HTML. Let's craft. About the role: