Tech Correspondent

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes job description (role description), responsibilities (what you will do), requirements/qualifications (what you need), maybe skills (some overlapping). Pay: salary range given. Benefits: not explicitly mentioned besides "We value our people. Click here for more on what we offer..." but no specifics; we should not create Benefits unless actual content. Schedule: not mentioned. So we include About the role (maybe a summary), Responsibilities, Requirements/Qualifications (could combine), Skills (maybe separate if distinct), Pay. We must not repeat job title as heading. No Job ID. Remove boilerplate like application instructions, EEO, etc. Also remove navigation, cookie, legal, duplicated lines. Preserve all substantive info. We need to parse the posting: It starts with "Job Description POLITICO is seeking an aggressive, enterprising reporter..." then description of beat, responsibilities. Then "What You’ll Need" list of requirements. Then "The anticipated salary range is $145,000–$160,000 per year." Then "We value our people. Click here for more on what we offer..." that's benefits but not specific; we should not include Benefits section because no concrete benefits listed. Then "About Us." etc. That's company description; could be considered "About the role"? Actually "About Us" is company overview, not role. The instruction: use headings for section headings like About the role, Responsibilities, etc. We could include an "About the role" section summarizing the job description (the first paragraph). Then Responsibilities: detailed duties. Then Requirements/Qualifications: the "What You’ll Need" list. Then Skills: maybe we can extract skills from requirements (e.g., ability to break news, cultivate sources, write clearly, etc.) but those are already in requirements; we could still make a Skills section if we have distinct skill items. However we should avoid thin sections; maybe combine Requirements and Skills into one section called "Requirements and Skills". But the instruction says use those headings only if we have real specific content. We could have separate sections: Responsibilities, Requirements, Pay. Possibly also "About the role". Let's decide. We need to preserve all substantive information. So we need to include the description of beat, responsibilities, what you'll need, salary range, and maybe company overview (About Us) could be placed under "About the role" or maybe not needed. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include About the role (a brief summary), Responsibilities (duties), Requirements (what you need), Skills (maybe separate if we have skill list), Pay (salary). We'll avoid Benefits and Schedule. We must not invent or summarize away detail. So we need to keep the details verbatim or close. Let's extract: About the role: Could be the first paragraph: "POLITICO is seeking an aggressive, enterprising reporter to cover how the tech industry is shaping the new political landscape. You will focus on how leading companies and executives are positioning themselves with the White House, Congress and regulators across America; which policies they’re advancing or fighting; who they’re lobbying and how Silicon Valley is preparing for the 2028 presidential campaign. The beat will cover the companies at the center of the tech and AI industries — including OpenAI, Anthropic, Google, Meta, Nvidia and xAI — as well as the executives, founders, investors, lobbyists and political operatives driving the industry’s relationship with Washington and the states. A deep source network among the biggest tech players in Silicon Valley and Washington will be essential. Those sources will drive breaking news on the tech industry’s political strategy, lobbying campaigns, corporate relationships and policy priorities, along with distinctive reporting on the personalities behind the industry’s growing political clout. The beat will focus closely on who has the ear of President Trump, which executives are gaining access to the White House, who is building relationships on Capitol Hill, which tech leaders are becoming political players and how rivalries, alliances and personal relationships are influencing the industry’s political approach. The policy portfolio will include artificial intelligence, antitrust and competition, data privacy, copyright, content moderation, online platforms, cryptocurrency, semiconductors, export controls, data centers and the tech workforce. The job will involve explaining the policy fights that matter most to Silicon Valley and, crucially, how the industry is seeking to influence them — through lobbying, political organizing, coalition-building and direct engagement with policymakers. The beat will also explore the competing visions within Silicon Valley over AI policy, the growing influence of AI companies and investors, and the battles over regulation that could define the industry’s future. Following the money and political capital will be a key piece of the job: which companies are spending to influence policy, which lobbyists and advisers are gaining influence, what trade groups are prioritizing, which executives are becoming donors and advisers and how companies are positioning themselves on the biggest political and policy questions. The reporter will dive in on how presidential candidates are courting Silicon Valley, which tech executives and investors are choosing sides, what the industry wants from the next administration and how tech executives are working to influence the candidates who could ultimately set tech policy. The job will require someone who can move comfortably between Silicon Valley and Washington — someone who understands the tech industry on its own terms but can also recognize the political stakes behind its biggest decisions. Breaking news, cultivating high-level sources and producing ambitious enterprise will be central to the role, with a focus on explaining how Silicon Valley is positioning itself, building influence and trying to determine what comes next. The position will work closely with POLITICO’s teams to connect developments in Silicon Valley with policy and political battles in Washington, Brussels and other tech and political centers around the world." That's a lot; could be considered responsibilities. Actually that's the role description. We could split: About the role (short summary) and Responsibilities (list of duties). But the instruction says prefer a few substantive sections over many thin ones. So maybe we just have one section "Responsibilities" containing all that detail. And another section "Requirements" containing the "What You’ll Need" list. And a section "Pay" with salary range. Possibly also "About the role" could be omitted to avoid thin section. But we need to include all substantive info; if we put everything under Responsibilities, we still include the role description. That's fine. Thus sections: Responsibilities, Requirements, Pay. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to keep the details as they are, maybe break into paragraphs. We need to remove boilerplate: navigation, cookie, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove "We value our people. Click here for more on what we offer and what it’s like to work for POLITICO. Let’s keep in touch. You can view our list of open positions here. We hope to see your application soon!" That's application instructions/boilerplate; remove. Also remove "About Us." etc? That's company description; is that substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; does that include company description? Probably yes, as it's part of the posting. But we need to decide where to put it. Could be under a section "About POLITICO" but not in allowed headings. The allowed headings list does not include "About the company". However we could incorporate it into "About the role" maybe? But the instruction says use those headings for section headings (e.g. About the role, Responsibilities, etc). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; we could also use other headings if needed? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the expected headings; we should stick to them. So we should not add a heading like "About POLITICO". We could incorporate the company overview into the "About the role" section as prose, but we don't have an About the role section if we didn't create one. We could create an About the role section that includes both a brief summary of the role and the company overview. That would be substantive. Thus we can have sections: About the role, Responsibilities, Requirements, Pay. Let's see if we have enough content for each. About the role: Could include a brief summary: "POLITICO is seeking an aggressive, enterprising reporter to cover how the tech industry is shaping the new political landscape." plus maybe the company overview from About Us. That would be substantive. Responsibilities: The detailed beat description (the long paragraph). Could be broken into multiple

  paragraphs or a

  • list? The instruction: Use
    • for any list of duties/requirements/benefits. The responsibilities are not a simple list but prose; we can use

      for prose. However if we want to break into bullet points, we could but not required. We'll keep as

      paragraphs. Requirements: The "What You’ll Need" list. That's a list; we should use

      • . Pay: The salary range; we can put in

        . We must not include Benefits or Schedule. Now we need to strip out boilerplate: The "About Us." section after salary is company overview; we will incorporate that into About the role. Also remove lines like "Posting Date 2026-09-29 Title Tech Correspondent". That's metadata; we can drop or fold into short

        . The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we can either drop it or put in a short

        . Probably drop it to keep minimal. Also remove "Let’s keep in touch..." etc. Now craft HTML. We'll start with

        About the role

        then

        containing the summary and company overview. Summary: "POLITICO is seeking an aggressive, enterprising reporter to cover how the tech industry is shaping the new political landscape." Then maybe add more from the description? But we risk duplication with Responsibilities. We'll keep it short. Then company overview: The "About Us." paragraph(s). Let's extract that: "About Us. POLITICO illuminates the forces shaping global power. Since 2007, we have delivered intelligence that anticipates tomorrow's headlines, not reports on yesterday's news. As politics has increasingly become the defining force of our era, our work has never been more vital. Cabinet secretaries and Ministers start their mornings with our analysis. CEOs shape strategy around our reporting. Advocacy leaders rely on our insights to move policy. We deliver the straightforward facts and clear-eyed analysis they need to navigate the most complex political landscape of our lifetimes. Our 1,100+ publishing professionals across the world's key democratic capitals—Washington, Brussels, London, Paris, Berlin, Sacramento, and New York—form the world's premier politics and policy newsroom. We tell the story of how power really works by explaining who wields it and how they plan to exercise it, connecting dots others miss and delivering scoops from sources others don't even know exist. Innovation has always been a core tenet of our story. At launch, we bet that depth would trump scale, that talent would trump