Senior Software Engineer
The Flex · San Marino, CA · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
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 need to parse the posting.
The posting includes:
- About Us (company description)
- What You'll Build (description of role)
- Your Mission (list of bullet points)
- Tech Stack (list)
- You Might Be a Great Fit If (list of qualifications)
- Bonus Points For (list)
- What Success Looks Like (list)
- Why Join Us (list)
- This Role Is Not For You (list)
- etc.
We need to map to sections: About the role (maybe combine About Us and What You'll Build?), Responsibilities (Your Mission bullet points), Requirements/Qualifications/Skills (You Might Be a Great Fit If, Bonus Points For, Tech Stack?), Benefits (Why Join Us?), Pay (none), Schedule (none). We must not create Pay/Schedule unless present. There's no explicit pay or schedule. So omit those sections.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information, not invent or summarize away detail. Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
The posting includes:
- About Us (company description)
- What You'll Build (description of role)
- Your Mission (list of bullet points)
- Tech Stack (list)
- You Might Be a Great Fit If (list of qualifications)
- Bonus Points For (list)
- What Success Looks Like (list)
- Why Join Us (list)
- This Role Is Not For You (list)
- etc.
We need to map to sections: About the role (maybe combine About Us and What You'll Build?), Responsibilities (Your Mission bullet points), Requirements/Qualifications/Skills (You Might Be a Great Fit If, Bonus Points For, Tech Stack?), Benefits (Why Join Us?), Pay (none), Schedule (none). We must not create Pay/Schedule unless present. There's no explicit pay or schedule. So omit those sections.
We must not repeat job title as heading. No Job ID.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide sections:
- About the role: could include About Us description and What You'll Build? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly combine Requirements and Qualifications? But we can separate if content distinct.
We have:
- About Us: description of company.
- What You'll Build: description of role.
- Your Mission: bullet list of responsibilities.
- Tech Stack: list of technologies.
- You Might Be a Great Fit If: list of qualifications/experience.
- Bonus Points For: additional qualifications.
- What Success Looks Like: expectations.
- Why Join Us: benefits/perks.
- This Role Is Not For You: maybe not needed; could be considered as anti-qualifications but we could drop as not required? It's substantive but maybe we can include under Requirements? However instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that info somewhere. Could be under Requirements or a separate section like "Not a fit". But we only have predefined headings; we could put it under Requirements or Qualifications as a bullet list of what not to do. Probably acceptable.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. None seen.
Thus produce HTML:
About the role
Base360.ai is the AI operating system for short-term rental businesses, helping property managers run their operations on autopilot. Born out of The Flex, a short-term rental operator that scaled to an eight-figure business using its own software, Base360.ai is now launching as a standalone platform for short-term rental operators worldwide. We bring reservations, guest communication, pricing, payments, cleaning, maintenance, and reporting into one platform—helping operators automate manual work, reduce costs, increase revenue, and scale their portfolios. We're looking for a highly ambitious Senior Software Engineer who wants to build systems that solve real problems at scale. You'll build, ship, automate, and deliver products that directly impact property managers, their teams, and their guests. If you're excited by APIs, automation, AI agents, cloud infrastructure, and building products from the ground up, we want to meet you.
Maybe also include What You'll Build paragraph? Could merge.
Better: About the role includes company description and role overview. Then Responsibilities: bullet list from Your Mission.
Responsibilities: bullet list items:
- Build the Core Platform: Design and develop scalable applications, services, and APIs that power reservations, availability, pricing, payments, guest experiences, and property operations.
- Create Powerful Automations: Build event-driven workflows that eliminate repetitive work—from scheduling cleaning after a booking to sending check-in instructions and generating owner statements.
- Develop AI-Powered Systems: Use LLMs and AI agents to automate guest communication, triage maintenance requests, support pricing decisions, and help operators manage their portfolios more efficiently.
- Design API-First Architecture: Create robust APIs that connect internal services, booking channels, third-party providers, and customer systems.
- Integrate the Ecosystem: Build and maintain integrations with platforms including Airbnb, Hostaway, Stripe, Twilio, OpenAI, Google, and other strategic partners across the short-term rental ecosystem.
- Scale Infrastructure: Deploy and manage cloud-native infrastructure designed for reliability, performance, and global growth across multiple property management businesses.
- Solve Complex Operational Problems: Build Solutions For Real-time reservation and availability synchronization, Dynamic pricing intelligence, Smart lock access and key management, Automated guest communication across channels, Operational forecasting, Cleaning and maintenance automation, Owner reporting and financial workflows, AI-powered monitoring and alerts.
- Move Fast and Own Delivery: Own projects end-to‑end—from understanding an operator’s problem to architecture, implementation, deployment, and ongoing improvement. Bring senior engineering judgment to technical decisions, code reviews, and the reliability of the systems you build.
We need to keep each bullet as - . Could combine some.
Then Requirements/Qualifications/Skills: we have Tech Stack, You Might Be a Great Fit If, Bonus Points For, What Success Looks Like (maybe expectations), Why Join Us (benefits). Also This Role Is Not For You.
We need to decide sections: Requirements, Qualifications, Skills, Benefits.
We could put:
- Requirements: Tech Stack (list of technologies) maybe as skills.
- Qualifications: You Might Be a Great Fit If (list).
- Skills: Bonus Points For (list) maybe.
- Benefits: Why Join Us (list).
- Also include What Success Looks Like as maybe "Expectations" but not a predefined heading; could be under Responsibilities? But it's about success metrics; maybe we can put under Qualifications as additional expectations.
But we must not create sections with filler. We have content for each.
Thus:
Requirements
- Strong experience building and owning production-grade software systems
- Experience with FastAPI, Python, React, or similar frameworks
- Strong understanding of APIs, distributed systems, and cloud architecture
- Experience designing scalable backend systems and reliable data models
- Ability to work independently and make sound technical decisions
- Strong problem-solving skills and a product mindset
- Curiosity about AI, automation, and operational efficiency
- Bias toward action, shipping, and learning from real users
- Ability to balance delivery speed with maintainability and reliability
Qualifications
- Tech Stack: Python, FastAPI, React, TypeScript, Supabase, PostgreSQL, AWS, Serverless architecture, OpenAI APIs, Twilio, Stripe, Docker, GitHub Actions
But maybe better to put Tech Stack under Skills.
Let's define:
- Skills: Tech Stack list.
- Qualifications: You Might Be a Great Fit If.
- Bonus Points: Bonus Points For.
Benefits: Why Join Us.
Also include What Success Looks Like maybe under Responsibilities? But it's about outcomes; could be under "Expectations" but not a standard heading. Could incorporate into Responsibilities as additional bullet? Might be okay to add a section "Expectations" but not in list. Safer to put under Responsibilities as additional bullet? But it's not a duty; it's success metric. Could add a separate section "What Success Looks Like" but not in allowed headings; but we could treat it as part of Responsibilities or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine What Success Looks Like into Qualifications or Benefits? It's about what success looks like after 12 months; could be under Benefits? Not exactly. Could be under Qualifications as expected outcomes. I'd add a subsection under Qualifications maybe as a paragraph.
But we must not invent headings. So we can add a under Qualifications describing success metrics.
Similarly, "This Role Is Not For You" could be added as a paragraph under Qualifications or as a separate section "Not a fit" but not allowed. Could add under Qualifications as a note.
Thus final HTML:
About the role
Base360.ai is the AI operating system for short-term rental businesses, helping property managers run their operations on autopilot. Born out of The Flex, a short-term rental operator that scaled to an eight-figure business using its own software, Base360.ai is now launching as a standalone platform for short-term rental operators worldwide. We bring reservations, guest communication, pricing, payments, cleaning, maintenance, and reporting into one platform—helping operators automate manual work, reduce costs, increase revenue, and scale their portfolios. We're looking for a highly ambitious Senior Software Engineer who wants to build systems that solve real problems at scale. You'll build, ship, automate, and deliver products that directly impact property managers, their teams, and their guests. If you're excited by APIs, automation, AI agents, cloud infrastructure, and building products from the ground up, we want to meet you.
Responsibilities
- Build the Core Platform: Design and develop scalable applications, services, and APIs that power reservations, availability, pricing, payments, guest experiences, and property operations.
- Create Powerful Automations: Build event-driven workflows that eliminate repetitive work—from scheduling cleaning after a booking to sending check-in instructions and generating owner statements.
- Develop AI-Powered Systems: Use LLMs and AI agents to automate guest communication, triage maintenance requests, support pricing decisions, and help operators manage their portfolios more efficiently.
- Design API-First Architecture: Create robust APIs that connect internal services, booking channels, third-party providers, and customer systems.
- Integrate the Ecosystem: Build and maintain integrations with platforms including Airbnb, Hostaway, Stripe, Twilio, OpenAI, Google, and other strategic partners across the short-term rental ecosystem.
- Scale Infrastructure: Deploy and manage cloud-native infrastructure designed for reliability, performance, and global growth across multiple property management businesses.
- Solve Complex Operational Problems: Build solutions for real-time reservation and availability synchronization, dynamic pricing intelligence, smart lock access and key management, automated guest communication across channels, operational forecasting, cleaning and maintenance automation, owner reporting and financial workflows, AI-powered monitoring and alerts.
- Move Fast and Own Delivery: Own projects end‑to‑end—from understanding an operator’s problem to architecture, implementation, deployment, and ongoing improvement. Bring senior engineering judgment to technical decisions, code reviews, and the reliability of the systems you build.
Requirements
- Strong experience building and owning production-grade software systems
- Experience with FastAPI, Python, React, or similar frameworks
- Strong understanding of APIs, distributed systems, and cloud architecture
- Experience designing scalable backend systems and reliable data models
- Ability to work independently and make sound technical decisions
- Strong problem-solving skills and a product mindset
- Curiosity about AI, automation, and operational efficiency
- Bias toward action, shipping, and learning from real users
- Ability to balance delivery speed with maintainability and reliability
Skills
- Python, FastAPI, React, TypeScript, Supabase, PostgreSQL, AWS, Serverless architecture,
for prose. We need to decide sections: - About the role: could include About Us description and What You'll Build? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly combine Requirements and Qualifications? But we can separate if content distinct.
We have:
- About Us: description of company.
- What You'll Build: description of role.
- Your Mission: bullet list of responsibilities.
- Tech Stack: list of technologies.
- You Might Be a Great Fit If: list of qualifications/experience.
- Bonus Points For: additional qualifications.
- What Success Looks Like: expectations.
- Why Join Us: benefits/perks.
- This Role Is Not For You: maybe not needed; could be considered as anti-qualifications but we could drop as not required? It's substantive but maybe we can include under Requirements? However instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that info somewhere. Could be under Requirements or a separate section like "Not a fit". But we only have predefined headings; we could put it under Requirements or Qualifications as a bullet list of what not to do. Probably acceptable.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. None seen.
Thus produce HTML:
About the role
Base360.ai is the AI operating system for short-term rental businesses, helping property managers run their operations on autopilot. Born out of The Flex, a short-term rental operator that scaled to an eight-figure business using its own software, Base360.ai is now launching as a standalone platform for short-term rental operators worldwide. We bring reservations, guest communication, pricing, payments, cleaning, maintenance, and reporting into one platform—helping operators automate manual work, reduce costs, increase revenue, and scale their portfolios. We're looking for a highly ambitious Senior Software Engineer who wants to build systems that solve real problems at scale. You'll build, ship, automate, and deliver products that directly impact property managers, their teams, and their guests. If you're excited by APIs, automation, AI agents, cloud infrastructure, and building products from the ground up, we want to meet you.
Maybe also include What You'll Build paragraph? Could merge. Better: About the role includes company description and role overview. Then Responsibilities: bullet list from Your Mission. Responsibilities: bullet list items: - Build the Core Platform: Design and develop scalable applications, services, and APIs that power reservations, availability, pricing, payments, guest experiences, and property operations. - Create Powerful Automations: Build event-driven workflows that eliminate repetitive work—from scheduling cleaning after a booking to sending check-in instructions and generating owner statements. - Develop AI-Powered Systems: Use LLMs and AI agents to automate guest communication, triage maintenance requests, support pricing decisions, and help operators manage their portfolios more efficiently. - Design API-First Architecture: Create robust APIs that connect internal services, booking channels, third-party providers, and customer systems. - Integrate the Ecosystem: Build and maintain integrations with platforms including Airbnb, Hostaway, Stripe, Twilio, OpenAI, Google, and other strategic partners across the short-term rental ecosystem. - Scale Infrastructure: Deploy and manage cloud-native infrastructure designed for reliability, performance, and global growth across multiple property management businesses. - Solve Complex Operational Problems: Build Solutions For Real-time reservation and availability synchronization, Dynamic pricing intelligence, Smart lock access and key management, Automated guest communication across channels, Operational forecasting, Cleaning and maintenance automation, Owner reporting and financial workflows, AI-powered monitoring and alerts. - Move Fast and Own Delivery: Own projects end-to‑end—from understanding an operator’s problem to architecture, implementation, deployment, and ongoing improvement. Bring senior engineering judgment to technical decisions, code reviews, and the reliability of the systems you build. We need to keep each bullet asRequirements
- Strong experience building and owning production-grade software systems
- Experience with FastAPI, Python, React, or similar frameworks
- Strong understanding of APIs, distributed systems, and cloud architecture
- Experience designing scalable backend systems and reliable data models
- Ability to work independently and make sound technical decisions
- Strong problem-solving skills and a product mindset
- Curiosity about AI, automation, and operational efficiency
- Bias toward action, shipping, and learning from real users
- Ability to balance delivery speed with maintainability and reliability
Qualifications
- Tech Stack: Python, FastAPI, React, TypeScript, Supabase, PostgreSQL, AWS, Serverless architecture, OpenAI APIs, Twilio, Stripe, Docker, GitHub Actions
under Qualifications describing success metrics. Similarly, "This Role Is Not For You" could be added as a paragraph under Qualifications or as a separate section "Not a fit" but not allowed. Could add under Qualifications as a note. Thus final HTML:
About the role
Base360.ai is the AI operating system for short-term rental businesses, helping property managers run their operations on autopilot. Born out of The Flex, a short-term rental operator that scaled to an eight-figure business using its own software, Base360.ai is now launching as a standalone platform for short-term rental operators worldwide. We bring reservations, guest communication, pricing, payments, cleaning, maintenance, and reporting into one platform—helping operators automate manual work, reduce costs, increase revenue, and scale their portfolios. We're looking for a highly ambitious Senior Software Engineer who wants to build systems that solve real problems at scale. You'll build, ship, automate, and deliver products that directly impact property managers, their teams, and their guests. If you're excited by APIs, automation, AI agents, cloud infrastructure, and building products from the ground up, we want to meet you.
Responsibilities
- Build the Core Platform: Design and develop scalable applications, services, and APIs that power reservations, availability, pricing, payments, guest experiences, and property operations.
- Create Powerful Automations: Build event-driven workflows that eliminate repetitive work—from scheduling cleaning after a booking to sending check-in instructions and generating owner statements.
- Develop AI-Powered Systems: Use LLMs and AI agents to automate guest communication, triage maintenance requests, support pricing decisions, and help operators manage their portfolios more efficiently.
- Design API-First Architecture: Create robust APIs that connect internal services, booking channels, third-party providers, and customer systems.
- Integrate the Ecosystem: Build and maintain integrations with platforms including Airbnb, Hostaway, Stripe, Twilio, OpenAI, Google, and other strategic partners across the short-term rental ecosystem.
- Scale Infrastructure: Deploy and manage cloud-native infrastructure designed for reliability, performance, and global growth across multiple property management businesses.
- Solve Complex Operational Problems: Build solutions for real-time reservation and availability synchronization, dynamic pricing intelligence, smart lock access and key management, automated guest communication across channels, operational forecasting, cleaning and maintenance automation, owner reporting and financial workflows, AI-powered monitoring and alerts.
- Move Fast and Own Delivery: Own projects end‑to‑end—from understanding an operator’s problem to architecture, implementation, deployment, and ongoing improvement. Bring senior engineering judgment to technical decisions, code reviews, and the reliability of the systems you build.
Requirements
- Strong experience building and owning production-grade software systems
- Experience with FastAPI, Python, React, or similar frameworks
- Strong understanding of APIs, distributed systems, and cloud architecture
- Experience designing scalable backend systems and reliable data models
- Ability to work independently and make sound technical decisions
- Strong problem-solving skills and a product mindset
- Curiosity about AI, automation, and operational efficiency
- Bias toward action, shipping, and learning from real users
- Ability to balance delivery speed with maintainability and reliability
Skills
- Python, FastAPI, React, TypeScript, Supabase, PostgreSQL, AWS, Serverless architecture,