Staff Software Engineer

We need to output HTML fragment with sections: About the role? The posting includes intro about company, then "The Role", "What You'll Be Doing", "Who You Are", "Qualifications", "Why Choose Us". Also maybe "Benefits" from Why Choose Us. Pay and Schedule not mentioned. So we should not include Pay or Schedule sections. Use

for each section heading. Use

• for lists. Use

  for prose. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes some lines like "If you need assistance..." and visa sponsorship, scam warning. Those are boilerplate; we should remove them. Also remove duplicated lines. Keep substantive info. We need to preserve all substantive information. Let's extract sections: Company intro: "We’re Changing the Rentals Industry ..." up to "... Rentable could be a great fit for you." That's about the company. Could be "About the company" but not requested heading. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list About the company, but we could still use a heading? They said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings if applicable. The posting has "The Role", "What You'll Be Doing", "Who You Are", "Qualifications", "Why Choose Us". We can map: "The Role" maybe as About the role? Or we could keep as is? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those headings if they exist. But we can also use other headings if they match content? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That seems to indicate we should use those specific headings for sections. However, the posting doesn't have exactly those headings; we could still create sections with those headings if content matches. For example, "About the role" could encompass the description of the role (The Role, What You'll Be Doing, Who You Are). "Responsibilities" could be the bullet list of duties. "Requirements" could be Qualifications. "Skills" maybe not needed. "Benefits" from Why Choose Us. "Pay" and "Schedule" not present, so omit. Thus we should produce sections: About the role, Responsibilities, Requirements, Benefits. Possibly also "Skills"? Not needed. We need to preserve all substantive information. Let's parse content. About the role: combine "The Role" paragraph and maybe "Who You Are"? Actually "Who You Are" is about candidate traits, could be part of Requirements or Skills. But we can treat "Who You Are" as part of About the role? Might be better to put under Requirements (qualities). However instructions: Use headings as per list; we can decide. Let's extract: The Role paragraph: "Our customers use ApartmentIQ to decide what to charge for real apartments. That number comes out of a pipeline you would own: data pulled from the property management systems that run the industry, fed through demand and renewal models, and surfaced as pricing recommendations that get acted on the same day. We're hiring a staff-level engineer to own that path end to end. It's a wide role by design - Python for the ML and ingestion services, Terraform for everything they run on, Ruby for the application layer that customers touch. Often all three in one change. If you like owning a system rather than a layer, this is that job." What You'll Be Doing: bullet list of responsibilities (multiple paragraphs each starting with a bold phrase). We need to convert to

  • . Who You Are: bullet list of traits (each starting with bold). Could be considered as part of Requirements or Skills. We'll treat as part of Requirements maybe. Qualifications: list of qualifications (Proven Track Record, Python Depth, etc.) plus Nice to Have. Why Choose Us: list of benefits (Remote-First, Competitive Compensation, Paid Time Off, Your Health Matters, Peace of Mind (On Us), Protection for Your Whole Crew, Invest in Your Future). Also note about accommodation etc which we should remove as boilerplate. We must not include sections like Pay or Schedule. Now produce HTML. We need to ensure we don't repeat job title as heading (not present). No Job ID. We must not include markdown fences. Let's craft. First, maybe a short paragraph for company intro? Not required but we could include as a preamble before sections. The instruction: Output ONLY the HTML fragment. It didn't forbid extra prose outside sections. But better to include it as a

    before sections? Not sure. The posting includes company intro; we should preserve it. Could put it as a

    before any headings. Thus:

    We’re Changing the Rentals Industry We’re a profitable, growth-stage company building industry-leading martech and data products for the rentals industry. While originally known for building and operating one of the U.S.’s largest rental marketplaces - Rentable, our focus has shifted to our category-leading AI and data SaaS products with triple-digit growth rates. We’re a fully remote team of 100+ spread across the U.S. from coast to coast. We operate on a strict no a**holes policy and are proud to have built a community of highly performing people that take our work seriously, but not ourselves. While we’ve raised $30MM+ to date from some of the world’s best investors, we’re profitable with a strong balance sheet and an indefinite runway. We pride ourselves on achieving rapid growth without having to incinerate capital. If you like the idea of joining an industry-changing company made up of people who genuinely like each other, Rentable could be a great fit for you.

    Then sections. About the role: combine The Role paragraph maybe plus Who You Are? Actually Who You Are is separate. Let's put About the role as the description of the role (The Role paragraph). Then Responsibilities as the bullet list from What You'll Be Doing. Then Requirements as Qualifications + Who You Are? Or we could split: Requirements (hard qualifications) and Skills (soft traits). But we have no separate Skills heading; we could put Who You Are under Requirements as well. Better: About the role: The Role paragraph. Responsibilities: bullet list from What You'll Be Doing. Requirements: Qualifications (hard) plus Who You Are (soft). Benefits: Why Choose Us list. Let's extract bullet points. What You'll Be Doing bullet points (each bold phrase then explanation): - Own a system that sets rents. Demand models, renewal probability, price elasticity, compliance scoring - you'll own the pipeline that produces them and be accountable for the recommendations landing correctly. - Solve a genuinely hard data problem. Property management systems are walled gardens with inconsistent APIs and no shared identity model. Getting clean, reconciled lease and charge data out of them is the core technical challenge of this role, and we're rebuilding it from scratch right now. - Build the infrastructure you depend on. Every database, queue, and role is in Terraform, and you'll write it. No ticket to another team to get a table provisioned. - Build the orchestration layer. Ingestion, inference, and the downstream daily jobs need to run in the right order, gate on their inputs being ready, and recover cleanly when something upstream is late. You'll own that coordination layer end-to-end — today it's cron and careful timing; you'll make it a real pipeline. - Prove the numbers are right. Build out the observability and alerting across the data architecture — pipeline health, data freshness, and recommendation drift — so a bad number gets caught before a customer prices a lease against it. - Work across the whole stack, for real. Python, Terraform, and Ruby are all first-class parts of this job, not a "some exposure to" bullet. - Set the bar on AI-assisted engineering. A large and growing share of what we merge is AI-assisted. We want someone with strong opinions about how to do that well and the review judgment to enforce them. We need to keep each as
  • . Who You Are bullet points: - You want scope, not scaffolding. You're looking for a system to own outright, and you'd rather have a hard problem and autonomy than a well-defined ticket queue. - You care that it's correct. These outputs move real money. You build the checks that prove it, and you notice when a number looks wrong. - You go end to end. Empty repo to production, including the alarms, the backfill, the runbook, and the migration nobody scoped. - You raise the level around you. Your reviews make other people's code better, and work quietly moves off other plates once you're there. - You have strong opinions on AI-assisted engineering. You lean on it to ship to customers faster but you have the discipline to uphold code quality standards. Qualifications (hard): Proven Track Record: 8+ years building and operating production systems, with real ownership of something significant. Python Depth: Strong Python in a serverless or service context - AWS Lambda, container images, dependency and runtime management, multi-stage job orchestration. Infrastructure as Code: Hands-on Terraform. You've stood up a production data store yourself, including the IAM, encryption, networking, and alarms around it. Data & SQL depth: Fluent in analytical SQL and data modeling - you've built and debugged multi-stage warehouse pipelines (ours run on Redshift) and reconciled messy source data into something trustworthy. You've worked across the major database paradigms - relational, key-value/document, and search — and know what one is the best tool for the job at hand. Ruby on Rails: You can own changes across a large Rails codebase, even if it's not where you've spent the most time. Cloud Native: Deep AWS across Lambda, S3, SQS, Kinesis, EventBridge, DynamoDB, Aurora/RDS, Redshift, and IAM. ML in Production: You've kept models serving correctly over time - versioning, dependency drift, feature plumbing, explainability. You don't need to have trained them. Adaptable & Autonomous: Experience navigating a fast-paced, growth-stage environment where priorities shift and ownership is expected. Nice to Have (list): - Golang experience - Web scraping at scale (Playwright or similar) - OpenSearch index management and tuning - SOC 2 or similar compliance and security remediation work - xgboost, scikit-learn, or SHAP - Multifamily, PropTech, or revenue management domain experience We could include Nice to Have under Requirements as a sublist or separate? Could add a subsection but not required. We'll include them as part of Requirements maybe as a separate
    with note "Nice to have". But we must not invent headings. Could just include them as part of Requirements list. Benefits (Why Choose Us): - Remote-First: We offer the freedom to work from home across most of the U.S. You’ll enjoy the flexibility of remote work, balanced with high-energy in-person offsites to build real connections and celebrate our wins together. - Competitive Compensation: We believe in hiring the best and paying accordingly. You’ll receive a competitive salary that reflects your impact and expertise. - Paid Time Off: Take the time you need with our flexible vacation policy and dedicated paid parental leave to support you and your family’s biggest milestones. - Your Health Matters: Stay healthy with high-quality Medical, Dental, and Vision insurance plans for you and your family. - Peace of Mind (On Us): We fully invest in your security with 100% company-paid Short-Term Disability, Long-Term Disability, and Basic Life Insurance. - Protection for Your Whole Crew: Access supplemental insurance for the unexpected, plus specialized coverage to keep your pets happy and healthy,