Sr. Software Engineer - Platform Engineering

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Wonder, About The Team, About The Opportunity, The Impact You Will Make, What You Bring To The Table, hybrid model, salary, Benefits, A Final Note (EEO etc). We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop the final note about E-Verify, accommodation, etc. Also drop "Our hybrid model requires 3 days a week in the office..." maybe that's schedule info, we can include schedule section if present. The posting says: "Our hybrid model requires 3 days a week in the office. That said, many team members choose to come in more often to take advantage of in-person collaboration and connection. You're welcome—and encouraged—to be in the office up to 5 days a week if it works for you." That's schedule info. So we can create a Schedule section with that content. Pay: "New York: $176,000 - $191,000 per year. Wonder uses geographic-specific salary structures, which means the salary offered may vary depending on where the job is located. The final salary offer will take into account various factors, such as the candidate's skills, education, training, credentials, and experience." That's pay info. So we can create Pay section. Benefits: there is a Benefits paragraph. We'll keep that. We need headings: About the role? The posting doesn't have an explicit "About the role" heading but we have sections: About Wonder (company description), About The Team, About The Opportunity, The Impact You Will Make, What You Bring To The Table. According to instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings where appropriate. The posting doesn't have explicit Responsibilities but we have "About The Opportunity" describing role. Could treat that as About the role. Or we could create sections: About the role (using About The Opportunity content), Responsibilities (maybe from Impact You Will Make?), Requirements (What You Bring To The Table?), Qualifications (maybe same as Requirements?), Skills (maybe from What You Bring To The Table?), Benefits, Pay, Schedule. We must not create sections with filler. So we need to ensure each section has substantive content. Let's extract: - About the role: could be summary of role: "We're looking for a Senior Software Engineer to help stand up this team from its earliest days and bring AI-enabled development practices to Wonder Engineering." plus description of tasks. We'll combine About The Opportunity and maybe The Impact You Will Make? But Impact is more about what you will make. Could treat Impact as Responsibilities? Actually responsibilities are what you will do. Impact is outcomes. Might be okay to have Responsibilities section from About The Opportunity (design and build solutions...). And maybe a separate Impact section? But we only have allowed headings list; we can add other headings? Instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. Thus we need to map content to those headings. Let's decide: - About the role: brief overview of the role and team. Use content from About The Team and About The Opportunity maybe. - Responsibilities: tasks you will do: design and build solutions to solve context fragmentation, MCPs/CLIs, skills, sub-agents, integrations, AI-assisted workflows (code generation, review, testing, documentation, on-call/incident management). Also from Impact: Build AI-Native Developer Tooling, Bring Outside Patterns In, Raise the Ceiling on Review, Instrument for Efficiency, Guide Technical Outcomes, Communicate Effectively. Could combine. - Requirements: maybe the "What You Bring To The Table" list (education, experience, etc). That's qualifications/skills. - Qualifications: maybe same as Requirements? Could split but we need to avoid duplication. Perhaps Requirements = mandatory experience, Qualifications = preferred? But we don't have clear separation. Could treat Requirements as the bullet list of mandatory items, and Qualifications as optional (Java/JVM/Python plus). But we need to avoid filler. Better: Use Requirements for the list of mandatory qualifications (education, 5+ years, experience with LLM tooling, integrating AI tools, system design skills, comfort with ambiguity, APIs, developer tooling, etc). Use Qualifications for the "Experience with Java/JVM and/or Python is a plus, though not required." and maybe "pragmatic approach..." but that's also mandatory. Hmm. Alternatively, we could have only Requirements and Qualifications combined? But we need to follow instruction: use those headings when posting has real specific content. If we cannot differentiate, we could omit Qualifications if no distinct content. But we have some plus items. Let's see: The posting includes: "What You Bring To The Table" bullet list: - Bachelor's or Master's degree in Computer Science or a related field, or equivalent practical experience - 5+ years of professional software engineering experience, including recent, hands-on work building with or on top of LLM-based tooling (agents, MCP servers, coding assistants, or similar). - Direct experience integrating AI tools into real development workflows — code review, testing, code generation, or documentation — beyond individual use as an end user. - Strong system design skills and a track record of owning tools or platforms end-to-end, from design through adoption. - Comfort operating with ambiguity: this is a new team without established playbooks, and you'll be shaping them. - Experience designing and consuming APIs, webhooks, or other integration/message-based systems. - Experience building developer tooling, internal platforms, CI/CD systems, or other software used by engineers as its primary users. - Experience with Java/JVM and/or Python is a plus, though not required. - A pragmatic approach to problem solving and the ability to troubleshoot complex technical obstacles. - Excellent communication and interpersonal skills, including the ability to drive technical discussions with engineers and leaders across multiple teams. Thus we can treat Requirements as the first 8 items (mandatory) and Qualifications as the last 2 (Java/Python plus, pragmatic approach, communication). But pragmatic approach and communication are also mandatory? They are listed as part of what you bring. Could treat them as Qualifications. Alternatively, we could have Requirements = the list, Qualifications = empty (omit). But we need to avoid empty headings. Better: Use Requirements for the list (all items) and Qualifications for the Java/Python plus note (since it's a plus). Also maybe note "pragmatic approach" and "excellent communication" could be considered Skills. Actually Skills heading could capture communication, pragmatic approach, troubleshooting. Thus: - Skills: pragmatic approach, troubleshooting, excellent communication, ability to drive technical discussions. - Requirements: education, 5+ years, LLM experience, AI tool integration, system design, comfort with ambiguity, APIs, developer tooling experience. - Qualifications: Java/JVM/Python experience (plus). But we also have "Experience building developer tooling, internal platforms, CI/CD systems, or other software used by engineers as its primary users." That's a requirement. Ok. Now Responsibilities: from About The Opportunity and Impact. Let's draft Responsibilities paragraph(s) maybe as a list. Responsibilities: - Design and build solutions to solve context fragmentation, MCPs/CLIs, skills, sub-agents, and integrations that connect AI tooling to Wonder's codebases and systems. - Develop AI-assisted workflows (code generation, review, testing, documentation, refactoring, on-call/incident management). - Build AI-native developer tooling: context aggregation solutions, MCPs/CLIs, skills, sub-agents. - Help define and stand up Wonder's autonomous development agents and cloud agent solutions. - Bring outside AI-assisted development patterns into Wonder's stack, defining standards for review, testing, code generation, documentation. - Contribute to pre-review and triage tooling that clears and automates mechanical and policy issues before human review; help define standards for reviewing AI-generated code. - Design and implement systems that optimize AI costs across the org, abstract model selection, route tasks to right model at right cost. - Help define and measure developer velocity. - Scope, design, and ship developer tooling with minimal oversight, weighing tradeoffs and partnering with platform, infrastructure, application teams. - Write clear specs and documentation; provide, seek, incorporate feedback from team and organization. That seems good. About the role: Could be a brief paragraph summarizing the role and team: "Join the Developer Experience & AI Velocity team, a new team chartered to own developer experience for Wonder Engineering (400+ engineers) with AI as the primary lever. You will help stand up this team from its earliest days and bring AI-enabled development practices to Wonder Engineering." We can combine About The Team and About The Opportunity. Now Schedule: from hybrid model description. Pay: salary range and note. Benefits: paragraph. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include any boilerplate like EEO etc. So we drop final note. Let's craft. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Qualifications

  • Experience with Java/JVM and/or Python is a plus, though not required.

  Benefits

  ...

  Pay

  New York: $176,000 - $191,000 per year. Wonder uses geographic-specific salary structures, which means the salary offered may vary depending on where the job is located. The final salary offer will take into account various factors, such as the candidate's skills, education, training, credentials, and experience.

  Schedule

  Our hybrid model requires 3 days a week in the office. That said, many team members choose to come in more often to take advantage of in-person collaboration and connection. You're welcome—and encouraged—to be in the office up to 5 days a week if it works for you.

  Check for any duplicated lines: ensure we didn't repeat. Now verify we haven't included any boilerplate: we omitted EEO, E-Verify, accommodation, final note, etc. Check that we preserved all substantive information: Did we miss any? Let's review original content: - About Wonder description: "Everything’s on the menu at Wonder. Except compromise. Wonder is the mealtime platform built to feed every craving in one order...". That's company description; we might have omitted it. Should we include it? It's about the company, not the role. The instruction says we should preserve ALL substantive information. But we are only allowed to output sections with headings from list. Could we include About the role section to incorporate company description? Possibly we can include a brief summary of Wonder in About the role. The About the role section could include both role and company context. That would preserve that info. We omitted the Wonder description. Let's incorporate it into About the role paragraph. Thus About the role paragraph: combine Wonder description and team description. Let's write: "Wonder is the mealtime platform built to feed every craving in one order, offering mix-and-match dishes from 20+ exclusive restaurants with $0 delivery fees, dine-in or pickup, made-to-order on-site.