Principal Engineer (US)

We need to output HTML fragment with sections only when there is 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, no invention, no filler. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to parse the posting. Key details: - Work Location: Charlotte, North Carolina, United States of America - Hours: 40 - Pay Details: description about compensation policies, but no specific numbers. It says "The base pay actually offered may vary based upon the candidate's skills and experience, job-related knowledge, geographic location, and other specific business and organizational needs." Also "TD is committed to providing fair and equitable compensation opportunities...". No specific pay figure. According to rules: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Hours 40 (so schedule maybe). It does not give specific pay amount. The Pay Details section is more about policy, not a specific number. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states "Hours 40" and "Pay Details" but the content is vague. However, we might still include a Pay section if there is substantive info beyond filler? The content includes statements about compensation policies, growth opportunities, etc. That might be considered substantive? But the rule says avoid filler like "commensurate with experience". The text includes "The base pay actually offered may vary based upon the candidate's skills and experience...". That's somewhat vague but still substantive? It's not a specific number, but it's describing compensation philosophy. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Details heading in the raw text. So we could include a Pay section with that content, but we must avoid filler like "varies". However the content includes "may vary". That's arguably filler. Might be better to omit Pay section because it's not specific. But we have Hours 40, which is schedule info. So we could include a Schedule section with "Hours 40". That's specific. Benefits: The posting mentions "Our Total Rewards Package" describing benefits: base salary, variable compensation, health and well-being benefits, savings and retirement programs, paid time off, banking benefits and discounts, career development, reward and recognition. That's substantive. So we can include Benefits section with that list. About the role: The job description paragraph about Principal Engineer providing deep technical leadership etc. That's substantive. Responsibilities: The "Depth & Scope" bullet points (though not bullet list originally) describe responsibilities: recognized as internal/external expert, spends majority time on technical issues, sets direction and oversees work of other IT professionals on complex projects, recognized as internal expert, provides consultative and strategic guidance to executive leadership. Those are responsibilities. Requirements: Education & Experience: Bachelor's or Graduate degree, Strong academic background (e.g., computer science, engineering) or 15+ years relevant experience. Preferred Qualifications: list of many items: 3+ years AI experience, advanced proficiency in cloud data platforms, strong experience with data architecture patterns, expertise in data modeling, deep knowledge of SQL, Python, distributed data processing frameworks, understanding of data governance frameworks, experience implementing data quality controls, knowledge of regulatory requirements, expertise in CI/CD pipelines and DevOps for data engineering, ability to enforce coding standards, executive-level communication, drives architecture etc. Skills: Could be derived from Preferred Qualifications? But we already have a Qualifications section maybe. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: job description paragraph. - Responsibilities: Depth & Scope bullet points. - Requirements: Education & Experience (minimum). - Qualifications: Preferred Qualifications (maybe also include "Preferred Qualifications" as Qualifications). - Skills: Could be extracted from Preferred Qualifications (like AI experience, cloud platforms, data architecture, data modeling, SQL, Python, distributed processing, data governance, data quality controls, regulatory knowledge, CI/CD DevOps, coding standards, executive communication). But we might combine Qualifications and Skills? The instruction says we can have multiple sections; we should not create thin sections. Perhaps combine Qualifications and Skills into one "Qualifications" section that includes both required and preferred? But we already have Requirements for mandatory. Could have Qualifications for preferred qualifications. Skills maybe not needed if covered. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Let's think: we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. That's six sections. Could be okay. We must not include Pay section because no specific pay. Hours 40 is schedule. We must not include boilerplate like "Who We Are", "Our Total Rewards Package" (but we can use that for Benefits). Actually "Our Total Rewards Package" is substantive benefits description; we can include that under Benefits. We must not include "Physical Requirements" etc? That's substantive but maybe not needed as a separate heading; could be part of Responsibilities or Requirements? But it's about physical demands; could be included under Responsibilities? However the instruction says use headings only for those specific categories. There's no heading for Physical Requirements. We could incorporate that info into Responsibilities or Requirements? But it's not exactly responsibilities. Might be better to omit because not fitting headings. However we must preserve ALL substantive information; we cannot invent or summarize away detail. If we omit physical requirements, we lose info. But we could include them under Responsibilities as part of job duties? Might be a stretch. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It implies we should use those headings for sections; we could still add 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 allowed headings. It doesn't say we cannot use other headings, but likely they want only those. To be safe, we should try to fit all substantive info into those categories. Physical Requirements could be considered part of Responsibilities (what the job entails). Or we could add a "Requirements" section that includes both education/experience and physical requirements. But Requirements heading is for qualifications; but we could still include physical demands there. Might be okay. Similarly, "Who We Are" is company description; could be part of About the role? Might be okay. But we need to preserve all substantive info; we can embed company description in About the role paragraph. Let's extract all substantive info: - Work Location: Charlotte, North Carolina, United States of America - Hours: 40 - Pay Details: description (compensation philosophy) - Line Of Business: Technology Solutions - Job Description paragraph (About the role) - Depth & Scope (Responsibilities) - Education & Experience (Requirements) - Preferred Qualifications (Qualifications) - Physical Requirements (maybe part of Responsibilities or Requirements) - Who We Are (company overview) maybe part of About the role. - Our Total Rewards Package (Benefits) - Additional Information (Colleague Development, Training & Onboarding, Interview Process, Accommodation) - some of that is boilerplate? Accommodation includes EEO statement and accommodation process; that's legal/EEO boilerplate, should be removed. Interview Process maybe generic; could be considered boilerplate? Might be removed. Colleague Development and Training & Onboarding could be part of Benefits? Actually they are about development opportunities; could be part of Benefits (career development). But we already have benefits list includes career development. So we can incorporate. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out: - EEO statement (Accommodation section includes EEO and accommodation request). Remove. - Interview Process maybe generic but could be kept? It's not boilerplate per se but it's about process; might be considered application instructions? The instruction says remove application instructions. Interview Process is about how they'll reach out; that's application instructions. So remove. - Colleague Development, Training & Onboarding maybe not application instructions; they are about employee development; could be kept as part of Benefits or maybe as a separate section? But we have Benefits already; we could add "Career development" under Benefits. - "Who We Are" is company overview; could be part of About the role. - "Our Total Rewards Package" is benefits. - "Additional Information" includes several subsections; we need to extract substantive parts: Colleague Development, Training & Onboarding, Interview Process (remove), Accommodation (remove). So we keep Colleague Development and Training & Onboarding. Now we need to format into HTML with

headings and

• for lists,

  for prose. We must not repeat job title as heading. We need to decide which sections to include: - About the role: combine job description paragraph + company overview (Who We Are) maybe. - Responsibilities: Depth & Scope bullet points (converted to

  • ). - Requirements: Education & Experience (Bachelor's or Graduate degree, Strong academic background ... or 15+ years relevant experience). Could also include physical requirements? Might be separate but we can add physical requirements under Responsibilities? Let's think: Physical requirements are not responsibilities but job demands. Could be under Requirements as well (job requirements). We'll include them under Requirements as a list. - Qualifications: Preferred Qualifications list. - Skills: Could be omitted if we think Qualifications covers skills. But we have a separate Skills heading allowed; we could split Preferred Qualifications into Skills and Qualifications? However Preferred Qualifications includes both skills and experience. Might be better to have Qualifications for experience/education and Skills for technical skills. But we already have Requirements for education/experience (minimum). Preferred Qualifications includes both experience (3+ years AI) and skills (cloud platforms, data architecture, etc.). We could split: Qualifications: 3+ years AI experience, maybe also advanced proficiency in cloud data platforms (skill). But it's messy. Given instruction to prefer few substantive sections, we could combine Qualifications and Skills into one "Qualifications" section that includes both preferred qualifications and skills. That would be okay. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We need to include Work Location and Hours somewhere. Work Location could be in About the role paragraph or maybe as a separate line? Could be included in About the role as a sentence: "Located in Charlotte, North Carolina." Hours 40 could be in Schedule section. Pay: we have Pay Details description but it's vague; we might omit Pay section because no specific number. However we could include a Pay section with the description about compensation philosophy, but that includes filler like "may vary". Might be considered filler. Safer to omit. Thus final sections:

    About the role

    Located in Charlotte, North Carolina. The Principal Engineer provides deep technical leadership, domain specialization and expertise, and sets direction in developing and implementing solutions to address emerging business needs and strategies and also advances the overall design architecture and technology capabilities in accordance with industry developments. This role is also influential to Senior Leaders and provides guidance and governance to other technology groups and business areas. TD is one of the world's