Sr. Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. We need to parse the posting. Let's extract sections: - Intro: "Do work that matters..." description of company, values, mission. Could be "About the role"? Actually "About the role" maybe includes description of role and team. The posting says: "AlertMedia is looking for a Sr. Software Engineer with full-stack experience. This role is on our AI Agent and Orchestration team, building the AI Assistant and Orchestration products and the agents and platform capabilities that power them. As an AI-forward company, we actively use modern AI tools such as Claude, Codex, and other emerging technologies to help our engineers work smarter, move faster, and build better products." That could be "About the role". Also "Who you are:" is qualifications/requirements. "What you get to do every day:" is responsibilities. "What you bring to the role:" is qualifications/requirements/skills. "Why you’ll love working at AlertMedia:" is benefits. "About AlertMedia:" maybe company description but could be omitted as not required? Might be considered "About the company" but not in list; we can ignore or maybe include as part of About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Pay and Schedule only if present. Pay: they mention "Competitive base salary + Company-wide bonus program". That's pay info. So we should include Pay section. Schedule: they mention remote, U.S.-based position, location restrictions. That's schedule? Not exactly schedule; maybe work arrangement. Could be considered Schedule? Might be location. Not schedule. They didn't mention work hours. So we skip Schedule. Now we need to extract content for each section, preserving all substantive info, not inventing. Let's gather: About the role: Should include description of role, team, AI-forward, using Claude, Codex, etc. Also maybe mention remote? But location maybe separate. We'll keep role description. Responsibilities: From "What you get to do every day:" list bullet points. Requirements: Could be combined with Qualifications? The instruction says we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements are mandatory, Qualifications are preferred. But we can split based on wording. The posting has "Who you are:" (qualities) and "What you bring to the role:" (more specific qualifications). Also "Location:" and "Sponsorship:" are metadata; we should fold minor metadata into short p or drop. We'll not create separate sections for those. We need to avoid repeating content. Let's extract: Who you are: - You thrive in a collaborative engineering environment that plays to everyone's strengths with a willingness to work across the entire stack. - You’ve developed scalable production web applications in Python/Django/Next.js/React. - You understand how LLM applications work — context, tool calling, evaluation, and the ways they fail. - You care about the quality of your work, the impactful product you help build, and the team you help build it with. - You have AWS (or other cloud) experience and are willing to learn from people with both more and less experience than you. - You are a user of AI-assisted development tools that improve engineering workflows, code quality, and team productivity. What you get to do every day (Responsibilities): - Build and ship features for the AI Assistant and Orchestration products — agents, tools, and the approval steps that gate them - Add eval cases for the AI behavior you build, so prompt and model changes that degrade quality are caught before release - Learn the AlertMedia platform and tools, and its uses for our customers - Work with Python, Django, Next.js, React, Node and other web technologies - Use AI-enabled tools such as Claude, Codex, and other emerging platforms to support development, problem-solving, documentation, and productivity - Work in an Agile based environment using tools like Git, JIRA, Jenkins, and Slack - Contribute to the technology lead that AlertMedia has over other solutions through innovative development and by helping contribute new ideas related to leveraging technology in our product line - Use strong verbal and written communication skills in collaboration with other engineering and product teams - Contribute to AlertMedia’s culture, values and vision for the future What you bring to the role (Qualifications/Skills): - Bachelor’s degree in a technical field such as computer science, computer engineering or related field preferred - 6+ years of experience building scalable web applications, Python/Django/React/Node tech stack preferred - Hands-on experience shipping LLM-powered features — agents, tool/function calling, MCP or similar integrations, retrieval, prompt and model evaluation - Familiar with agentic design patterns and frameworks (Strands, AutoGen, LangChain, etc.) - Experience with Amazon Web Services (or other cloud services) is required - PostgreSQL, Redis, and other storage technologies experience required - You have an established practice of writing unit and integration tests - Proficiency using AI coding tools (Claude, Cursor, Codex, or similar) across the development lifecycle - Collaborative mindset to partner with principal engineers and leadership to drive architectural evolution for a critical application - Experience troubleshooting and remediating production issues when they arise - Strong organizational skills and ability to manage working on multiple projects in parallel - The ability and desire to work in a fast-paced challenging environment - Outstanding communication skills and ability to effectively work cross-functionally in a fast-paced challenging environment - Strong English proficiency (written and oral) is required Location and Sponsorship: remote, U.S.-based, list of states not hired, no visa sponsorship. We'll fold into a short p maybe under About the role or Benefits? Probably under About the role as metadata. Benefits: From "Why you’ll love working at AlertMedia:" list: - Competitive base salary + Company-wide bonus program - Generous and flexible time off and parental leave policies - Health benefits - Medical, Dental, Vision and Life Insurance are 100% paid for employees! - 401K with generous company match - Amazing rewards and incentives – we love celebrating each other! - Commitment to community service with opportunities to give back - A Best Places to Work company 10 years in a row and numerous other awards - Access to new downtown office with 360 views of Austin, high-tech building gym and nearby running trails - Ongoing career development opportunities through our Learning & Development team - You'll do meaningful work—while growing your career in a fast-moving, global company with an award-winning culture Pay: Already included in benefits? Actually "Competitive base salary + Company-wide bonus program" is pay. Could be separate Pay section. But we already have that in benefits list. The instruction: include Pay section only if posting actually states them. It does state competitive base salary + bonus. So we could make a Pay section with that line. However we must not duplicate content. If we put it in Benefits, we might duplicate. Better to separate: Pay section with that line; Benefits section with other benefits (time off, health, 401k, rewards, community service, awards, office access, career development, meaningful work). But the instruction says prefer a few substantive sections over many thin ones. Could combine Pay into Benefits? But they said include Pay section only if posting actually states them. It does state them, but we could still include Pay as a subsection within Benefits? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect separate headings. We'll create Pay and Benefits separate. Thus: - About the role: includes company mission, values, team description, remote location note maybe. - Responsibilities: list from "What you get to do every day:". - Requirements: maybe include mandatory items: Experience with AWS required, PostgreSQL, Redis required, 6+ years experience, Bachelor's degree preferred? Actually Bachelor's degree preferred, not required. Could put in Qualifications. Let's split: Requirements = mandatory: Experience with AWS (or other cloud) required; PostgreSQL, Redis required; 6+ years experience building scalable web applications; Hands-on experience shipping LLM-powered features; Proficiency using AI coding tools; Strong English proficiency required; Ability to work in fast-paced challenging environment; Outstanding communication skills; Collaborative mindset; Experience troubleshooting production issues; Strong organizational skills; Ability to manage multiple projects; Willingness to learn from others; etc. But many of those are also in "What you bring to the role". We'll just put all from "What you bring to the role" into Requirements and Qualifications? Might be messy. Simplify: Use Requirements for the bullet list under "What you bring to the role:" (since those are qualifications). Use Qualifications for maybe education and preferred experience? But the instruction says we can have both sections; we can decide to put education and preferred experience in Qualifications, and required experience/skills in Requirements. Let's define: Requirements (mandatory): - 6+ years of experience building scalable web applications, Python/Django/React/Node tech stack preferred (maybe preferred though). Actually "preferred". Hmm. - Experience with Amazon Web Services (or other cloud services) is required. - PostgreSQL, Redis, and other storage technologies experience required. - You have an established practice of writing unit and integration tests. - Proficiency using AI coding tools (Claude, Cursor, Codex, or similar) across the development lifecycle. - Strong English proficiency (written and oral) is required. - Experience troubleshooting and remediating production issues when they arise. - Strong organizational skills and ability to manage working on multiple projects in parallel. - The ability and desire to work in a fast-paced challenging environment. - Outstanding communication skills and ability to effectively work cross-functionally in a fast-paced challenging environment. - Collaborative mindset to partner with principal engineers and leadership to drive architectural evolution for a critical application. Qualifications (preferred/education): - Bachelor’s degree in a technical field such as computer science, computer engineering or related field preferred. - Hands-on experience shipping LLM-powered features — agents, tool/function calling, MCP or similar integrations, retrieval, prompt and model evaluation. - Familiar with agentic design patterns and frameworks (Strands, AutoGen, LangChain, etc.). - You are a user of AI-assisted development tools that improve engineering workflows, code quality, and team productivity. (maybe from Who you are) - You have AWS (or other cloud) experience and are willing to learn from people with both more and less experience than you. (some overlap) - You’ve developed scalable production web applications in Python/Django/Next.js/React. - You understand how LLM applications work — context, tool calling, evaluation, and the ways they fail. - You care about the quality of your work, the impactful product you help build, and the team you help build it with. - You thrive in a collaborative engineering environment that plays to everyone's strengths with a willingness to work across the entire stack. But there is overlap. Might be okay but could be repetitive. Perhaps better to combine Requirements and Qualifications into one section called Requirements (or Qualifications). But the instruction allows multiple sections; we can include both but ensure not repetitive. Could put "Requirements" for the hard requirements (AWS, PostgreSQL, Redis, 6+ years, English proficiency, etc.) and "Qualifications" for education and preferred experience (Bachelor's degree, LLM experience, agentic frameworks, etc.). Also "Skills" for technical stack: Python, Django, Next.js, React, Node, etc. Let's extract Skills: from "Who you are:" and "What you get to do every day:" we have Python, Django