Sr. Software Development Engineer

We need to output HTML fragment with sections only when posting has real specific content. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: Immigration/Work Authorization notice? That's substantive? It says applicants must be authorized to work in US, iSpot not able to sponsor visa. That's a requirement. Should we include it? Probably under Requirements or Qualifications. It's a requirement. We'll keep. We need sections: About the role (intro paragraph). Responsibilities (list). Requirements (maybe experience). Qualifications (maybe education). Skills (maybe tech stack). Benefits (maybe equity, standard benefits). Pay (cash compensation range). Schedule (hybrid & flexible workplace policy). Must only include sections if posting has real specific content. Let's parse posting: - Immigration/Work Authorization notice: requirement. - iSpot competes for best talent. compensation packages consist of salary and equity in one of Seattle’s hottest start-ups, as well as other standard benefits. Most importantly, we provide a really interesting working experience, and the chance to contribute to the success of something great. -> This is about role/benefits. - What You’ll Be Part Of At iSpot.tv, we deal with BIG data, operating in a high-scale AWS environment with thousands of servers processing massive streams of media metadata. As a Senior SDE, you are a foundational pillar of our engineering team. You don’t just write code; you own entire domains, drive scalable solutions, and act as a “go-to” expert. We are currently looking for an AI-native engineer—someone who views AI not as a novelty, but as a core component of their development lifecycle—to help lead our mission-critical data evolution, and contributing to the vision of the Creative, Audience, and Outcomes pillars. -> About the role. - Responsibilities: list bullet points under headings: Technical Excellence & Domain Ownership, AI-Driven Productivity & Innovation, Operational Excellence & Data Strategy, Leadership & Collaboration. Each has sub-bullets. - Qualifications And Education Requirements: includes Experience, Architectural Leadership, Platform Engineering, Cloud Native, Tech Required, AI Native, Soft Skills. - Preferred Skills: Experience with IaC (Terraform) and CI/CD concepts (CircleCI). A track record of identifying trends... - Target cash compensation range: $140,183 - $179,436 USD Annually ... includes base salary, variable commission, annual bonus targets. Equity plan, stock options. Non-exempt roles eligible for overtime. - Hybrid & Flexible Workplace Policy: description. - EEO etc boilerplate to remove. Thus sections: About the role: paragraph(s) describing role. Responsibilities: list of duties (maybe combine subpoints into

• ). Requirements: maybe the "Experience: Significant experience developing software..." etc. Could be under Requirements. Qualifications: maybe education? Not much explicit education. Could combine with Requirements? But we need separate headings only if content. Skills: tech stack list: Java, Spring Boot, MySQL, RabbitMQ, Kubernetes/EKS, Docker, CI/CD pipelines, AI coding assistants, etc. Also Preferred Skills. Benefits: equity, standard benefits, interesting working experience, chance to contribute, etc. Also mention "standard benefits". Could list. Pay: cash compensation range. Schedule: hybrid & flexible workplace policy. We must not include sections with filler like "commensurate with experience". We have actual content. We must not repeat job title. No markdown. We must output only HTML fragment. Let's craft. Structure:

  About the role

  ... paragraphs ...

  Responsibilities

  • Technical Excellence & Domain Ownership: ...
  ... etc. But we need to preserve all substantive detail. Could break each bullet into subpoints? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have top-level li for each responsibility area, and inside we could have further detail maybe as text within li (not nested list). That's okay. We must preserve all detail: So each responsibility bullet should include the subpoints. Let's extract responsibilities sections: Technical Excellence & Domain Ownership: - Coding & Debugging: Design domains with testability and multiple teams in mind, creating extensible and shareable codebases. Provide prescriptive code reviews that suggest more acceptable code patterns and contribute to company-wide style guidelines. - Quality & Release: Maintain a high standard of quality, setting the example for the team. Develop the architecture for our automation systems and expertly debug complex issues within the CI/CD pipeline. Implement secure deployment strategies, especially for large-scale, high-risk projects. AI-Driven Productivity & Innovation: - AI-First Mindset: Be “AI-native.” Actively explore and learn about AI technologies that enhance the efficiency of the entire team’s work. - Leading Adoption: Don’t just use AI; “create space” for teammates to improve their AI tooling through pairing, providing demos, and writing documentation. - Creative Problem Solving: Act as a pioneer in critical technologies, bringing creative solutions to complex, large-scale projects and ensuring your contributions can be extended far into the future. Operational Excellence & Data Strategy: - Data-Driven RCA: Propose and implement viable domain measurement solutions. Play a lead role in researching external solutions and leading root cause analysis (RCA) for complex, multi-domain incidents. - Operational Efficiency & Toil Reduction: Proactively improve the current state of operations by identifying and reducing toil. Apply a “Platform Engineering” mindset to automate repetitive manual tasks, ensuring the team remains focused on high-value engineering. - Scalability & Influence: Build internal networks to improve organizational speed and the quality of technology solutions, removing obstacles for the team as they arise. Serve as the “go-to” person for the team, identifying trends and introducing broad solutions to address systemic issues. - Cost-Conscious Engineering: Drive a mature cost-optimization strategy, ensuring that architectural decisions and cloud resource utilization are both performant and cost-efficient. Balance technical excellence with business value, treating cost-consciousness as a core pillar of system reliability. Leadership & Collaboration: - Strategic Alignment: Routinely work cross-functionally to align partners and stakeholders with the project vision and strategy. - Mentorship: Mentor less experienced team members, ensuring your communication promotes clarity and inspires action. Onboard and coach other engineers in adopting an AI-first mindset, focusing on low-risk strategies. - Conflict Resolution: Handle personal conflicts within the team and navigate ambiguity to reach strategic milestones. Now Qualifications And Education Requirements: Experience: Significant experience developing software for shareable features across multiple engineering projects. Experience leading small-to-mid-sized technical initiatives is required. Architectural Leadership: Proven ability to make high-level architectural decisions, including redesigning legacy services to ensure they are highly reliable and operable. Follows industry best practices for high-availability API design and the streamlining of complex database operations. Platform Engineering: Hands-on experience with Platform Engineering principles, focusing on internal developer experience, infrastructure abstraction, and building self-service capabilities for engineering teams. Cloud Native: Expert knowledge of AWS (S3, Lambda, EC2, IAM). Tech Required: Java, Spring Boot, MySQL, RabbitMQ (or similar message broker), Kubernetes/EKS, Docker, CI/CD pipelines. AI Native: Experience using AI coding assistants and LLMs to accelerate development (e.g., Kiro, Gemini, Copilot, Cursor, or similar, Claude Code). Soft Skills: Strong communication skills with the ability to tailor messaging to different audiences (from junior devs to senior leadership). Excellent problem-solving and analytical skills. Preferred Skills: Experience with Infrastructure as Code (Terraform) and CI/CD concepts (CircleCI). A track record of identifying trends in incidents and introducing broad solutions to address them. Benefits: compensation packages consist of salary and equity in one of Seattle’s hottest start-ups, as well as other standard benefits. Most importantly, we provide a really interesting working experience, and the chance to contribute to the success of something great. Also equity plan: all full time iSpotters eligible to participate in iSpot’s equity plan to receive stock options. Non-exempt roles also eligible for (pre-approved) overtime pay. Pay: Target cash compensation range: $140,183 - $179,436 USD Annually. Includes base salary, variable commission for employees in eligible roles, and annual bonus targets for eligible roles. Schedule/Hybrid: Hybrid & Flexible Workplace Policy description. Immigration/Work Authorization notice: Applicants must be currently authorized to work in the United States. iSpot is not able to sponsor or take over sponsorship of an employment visa for this position at this time. We could put that under Requirements or Qualifications. Probably under Requirements as a legal requirement. Now we need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for each. About the role: paragraphs from "What You’ll Be Part Of..." plus maybe the intro about iSpot competes for best talent? That is more about compensation/benefits. We'll keep About the role as description of role and environment. Responsibilities: as above. Requirements: maybe include the immigration notice and maybe "Experience: Significant experience..."? But that seems more qualifications. Could split: Requirements = mandatory requirements (experience, leadership, platform engineering, cloud native, tech required, AI native, soft skills). Qualifications = maybe education? Not much. Could combine but we need separate headings only if content. We could put Requirements as the list of mandatory qualifications (Experience, Architectural Leadership, Platform Engineering, Cloud Native, Tech Required, AI Native, Soft Skills). Qualifications could be Preferred Skills? Or maybe we treat Qualifications as education/degrees? Not present. Could skip Qualifications section if no specific content. But we have Preferred Skills which could go under Skills. Benefits separate. Pay separate. Schedule separate. Thus we could have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Qualifications maybe omitted. But the instruction says use headings for those specific names if we have content. It's okay to omit a heading if no real specific content. So we can omit Qualifications. Skills: list of tech stack and preferred skills. Let's craft. We need to preserve all substantive info: So include all bullet points from responsibilities, requirements, tech required, preferred skills, benefits, pay, schedule, immigration notice. Let's write HTML. We'll need to escape any special characters? Not needed. We'll produce:

    About the role

    At iSpot.tv, we deal with BIG data, operating in a high-scale AWS environment with thousands of servers processing massive streams of media metadata. As a Senior SDE, you are a foundational pillar of our engineering team. You don’t just write code; you own entire domains, drive scalable solutions, and act as a “go-to” expert. We are currently looking for an AI-native engineer—someone who views AI not as a novelty, but as a core component of their development lifecycle—to help lead our mission-critical data evolution, and contributing to the vision of the Creative, Audience, and Outcomes pillars.

    Maybe also include the sentence about iSpot competes for best talent? That is more about compensation/benefits; we could include in Benefits section. Now Responsibilities:

    Responsibilities

    • Technical Excellence & Domain Ownership
      • Coding & Debugging: Design domains with testability and multiple teams in mind, creating extensible and shareable codebases. Provide prescriptive code reviews that suggest more acceptable code patterns and contribute to company-wide style guidelines.
      • Quality & Release: Maintain a high standard of quality, setting the example for the team. Develop the architecture for our automation systems and expertly debug complex issues within the CI/CD pipeline. Implement secure deployment strategies, especially for large-scale, high-risk projects.