Principal Software Engineer

We need to output HTML fragment with sections: headings

for each section present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where posting has real specific content. Let's parse posting. Content includes: - Intro about company: "Arboreal Management is looking for an exceptional software engineer..." This 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 need to map content. We have description of role: "The role You will work directly with our CEO..." That's responsibilities. We have "What You'll Do" list: bullet points. We have "Who We're Looking For": qualifications/requirements. We have "Our technology": maybe skills. We have "Why this might be interesting": maybe benefits? Not exactly benefits but could be "Why this might be interesting" as maybe "Benefits"? But we need actual benefits like pay, schedule. Not present. There's location: Seattle, preference for in-person. No explicit pay or schedule. So we should not include Pay or Schedule sections because no specific content. Benefits: maybe we could include "Why this might be interesting" as benefits? But the instruction says only include section when posting has real, specific content for it. Benefits could be things like health insurance, remote work, etc. Not present. So we should not include Benefits unless we have something like "Why this might be interesting" which is more about the role appeal, not benefits. Safer to omit Benefits. Thus sections: About the role (maybe intro), Responsibilities (What You'll Do), Requirements/Qualifications (Who We're Looking For), Skills (Our technology). Possibly also "About the role" could be the initial paragraph about company and mission. Let's decide. We need to avoid repeating job title as heading. No job title given explicitly, but we can ignore. We must use

for each section heading. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details. Let's extract content. Intro paragraph: "Arboreal Management is looking for an exceptional software engineer to become the senior technical builder on a small, unusually ambitious internal software team. We are a property management firm with ambitions to remake the industry. In four years we have grown to managing over 9,000 homes, doubling each year. Our industry is slow-moving and technologically backwards. We think there is an enormous opportunity to do things differently. We are winning by combining genuine care for our residents and clients with a willingness to build and deploy new technology very quickly. Over the last several years, we have been building our own software platform, Maynard, to run more and more of the company. It now touches leasing, property operations, communications, maintenance, document processing, reporting, and other core workflows. We are increasingly building systems that touch all business domains and incorporate the latest AI enabled workflows. We are not trying to be a software company, and we don't plan to build a big engineering organization because that will slow us down. We are looking for someone who is extremely good at building software and excited about having it make an impact in the world, fast." That's suitable for About the role. Responsibilities: The role section after "The role You will work directly with our CEO..." plus "What You'll Do" list. Let's capture: "The role You will work directly with our CEO, who has a computer science background and is deeply involved in designing and building Maynard. We have a high level vision and roadmap for Maynard. Your job is to take that vision and turn it into excellent production software. Sometimes that means taking an idea and running with it. Sometimes it means looking at something we've already built and saying, 'This needs to be rebuilt before we depend on it.' We want someone with enough technical judgment to know the difference. You will be the technical owner for our hardest and most consequential engineering work. One example is Maynard Treasury, a new system we're building to control and account for the movement of money across a company with thousands of residents, more than 100 properties, and hundreds of bank accounts. Systems like this need more than code that works. They need thoughtful architecture, security boundaries, auditability, reliability, and careful handling of failure cases." Then "What You'll Do" list: - Design and build major parts of Maynard - Own architecture for technically difficult or high-risk systems - Turn rough product concepts and prototypes into reliable production software - Make pragmatic decisions about where we need engineering rigor and where we should simply move fast - Establish sensible standards around testing, deployment, observability, security, and reliability - Review and improve existing systems as Maynard grows - Work closely with our Product Engineer, who supports our roughly 200 internal users and turns their feedback into product improvements - Use modern AI development tools aggressively to increase engineering velocity - Continue writing a lot of code We need to keep these as list items. Requirements/Qualifications: "Who We're Looking For" paragraph plus bullet-like sentences. Let's extract: "You are an excellent software engineer who wants substantially more ownership than you have today. You have built and operated real production systems and have developed strong opinions about what makes software reliable, maintainable, and understandable. You are comfortable working across the stack. Our problems don't fit neatly into frontend, backend, infrastructure, data, or AI boxes, and neither should you. You don't need a particular degree or pedigree. We care much more about what you've built and how you think. You should be excited about working directly with a highly involved CEO. This is important. You'll get a lot of context, ideas, prototypes, and opinions, often quickly. We already have a strong vision for where we want to take Maynard, but we need your technical judgment about how to get there. You need to be comfortable taking an idea and running with it, pushing back when you think we're heading down the wrong technical path, and ultimately owning the quality of what we put into production. We want someone with strong opinions, low ego, and a bias toward building." We could treat this as Requirements (or Qualifications). Since we have both Requirements and Qualifications headings possible, but we should avoid thin sections. We could combine into one section, maybe "Requirements". Or we could have "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have both requirements and qualifications content; we could put them under "Requirements". Or we could split but risk thin sections. Better to have one section "Requirements" containing all that. Skills: "Our technology" paragraph. Extract: "Our technology Our current stack includes JavaScript/Node.js, SvelteKit, Postgres, Azure, Cloudflare, and a growing collection of AI models and services. We integrate heavily with third-party APIs and are steadily augmenting and replacing legacy SaaS software with systems we control ourselves. We know AI is fundamentally changing how software gets built, and we are leaning into that change rather than cautiously experimenting around the edges. You should already be using AI extensively in your own development workflow and be excited about figuring out how a very small engineering team can build and operate systems that previously would have required a much larger organization. Experience with our exact stack is not required. Strong engineers learn tools." We can make a list of technologies maybe as

  • . But the instruction says use
    • for any list of duties/requirements/benefits. For skills, it's also a list; we can treat as list. Thus we can output:

      About the role

      ...intro paragraph...

      Responsibilities

      ...the role paragraph before list...

      • Design and build major parts of Maynard
      ...

      Requirements

      ...who we're looking for paragraph...

      Skills

      • JavaScript/Node.js
      • SvelteKit
      • Postgres
      • Azure
      • Cloudflare
      • AI models and services
      • Third‑party API integration
      • Experience with AI development tools

      Experience with our exact stack is not required. Strong engineers learn tools.

      We must not include Benefits, Pay, Schedule. Check for any duplicated lines: ensure we didn't repeat. We must preserve all substantive information: Did we miss any? Let's verify. From intro: we captured all. From responsibilities: we captured the paragraph before list and list items. From who we're looking for: we captured paragraph. From technology: we captured list and note about experience not required. We omitted "Why this might be interesting" section. That includes: "This is an unusual engineering job. You won't spend six months getting permission to change a service that does one small thing. You will have direct access to the people running the business and the ability to ship software that changes how hundreds of employees work and how thousands of apartments are operated. We're a real operating company, not a software startup trying to discover a business model. The problems are concrete, the users sit down the hall, and when you build something good, you'll see it being used almost immediately. For the right engineer, the scope is enormous. Location: Seattle. We strongly prefer someone who can work with us in person regularly. If you're an exceptional builder who wants ownership, speed, and hard real-world problems, we'd like to talk." This is substantive content about benefits/appeal. Could be placed under "Why this might be interesting" but we don't have that heading. Could we put under "Benefits"? Not exactly benefits but could be considered "Why this might be interesting" as a section about role appeal. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list "Why this might be interesting". So we must map that content to one of the allowed headings if we include it. Could be "Benefits" (though not typical benefits). Or maybe we could incorporate into "About the role" or "Responsibilities". But the instruction says prefer a few substantive sections over many thin ones. We could add a section "Benefits" containing that content. However, the content includes location and preference for in-person, which could be considered "Schedule"? Not really. Location could be a detail but not a heading. Given we already have About the role, Responsibilities, Requirements, Skills. Adding Benefits would be a fourth section, still few. It's appropriate to include location and appeal under Benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state location and preference for in-person, which could be considered a benefit (work location). So we can create a Benefits section with that content. Thus we add:

      Benefits

      Location: Seattle. We strongly prefer someone who can work with us in person regularly. ... (rest of why this might be interesting)

      We need to include all of that "Why this might be interesting" paragraph. Let's extract that paragraph fully: "Why this might be interesting This is an unusual engineering job. You won't spend six months getting permission to change a service that does one small thing. You will have direct access to the people running the business and the ability to ship software that changes how hundreds of employees work and how thousands of apartments are operated. We're a real operating company, not a software startup trying to discover a business model. The problems are concrete, the users sit down the hall, and when you build something good, you'll see it being used almost immediately. For the right engineer, the scope is enormous. Location: Seattle. We strongly prefer someone who can work with us