Senior Data Engineer, AI Data Products
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to extract relevant content: Alternate Locations, Work Arrangement, Relocation assistance, Requisition # (fold into short p or drop). The Role at a Glance (maybe About the role). Then "What You'll Be Doing" (Responsibilities). Then "What We’re Looking For" with Must Haves and Nice to Haves (Requirements/Qualifications/Skills). Then "What’s it like to work here?" maybe not needed? It's generic fluff; maybe we can include as About the role? But we should avoid filler. It's somewhat generic but still substantive? It's about culture; could be included under About the role or maybe omitted as not essential? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep culture description if it's substantive. However we need to avoid boilerplate like EEO etc. The culture paragraph is not boilerplate; it's specific to Lincoln Financial. So we can include maybe under About the role or a separate section like "About the Company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We have "What’s it like to work here?" could be considered About the role or maybe we can put under About the role. Also "What’s in it for you:" includes benefits: career tracks, leadership development, PTO/parental leave, competitive 401K and employee benefits, free financial counseling, health coaching, employee assistance program, tuition assistance program, work arrangements that work for you, effective productivity/technology tools and training. That's benefits. So we need a Benefits section.
Pay: The posting includes "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range and could vary above and below the listed range as permitted by applicable law." It does not give actual numbers. It says pay range is ??? Not specified. It says "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range". This is vague; no actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state there is a pay range but doesn't give numbers; still it's stating something about pay. However it's essentially filler: "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range and could vary above and below the listed range as permitted by applicable law." This is not a concrete range; it's generic. Might be considered placeholder? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "varies". So we should NOT create a Pay section because it's not specific. So we omit Pay.
Schedule: Work Arrangement: Hybrid : Employee will work 3 days a week in a Lincoln office. That's schedule info. So we can include a Schedule section.
Benefits: we have "What’s in it for you:" list. So Benefits section.
Now we need to decide sections: About the role (maybe from "The Role at a Glance" and maybe also "What’s it like to work here?"), Responsibilities (What You'll Be Doing), Requirements (Must Haves), Qualifications (maybe Nice to Haves?), Skills (maybe combine). But we should prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But headings are predefined; we can use them if we have content. We have Must Haves and Nice to Haves; we could put Must Haves under Requirements, Nice to Haves under Qualifications or Skills. Or we could put all under Requirements and leave Qualifications empty (but we shouldn't emit empty headings). So we need to allocate.
We have "Must Haves:" list of items. That's requirements. "Nice to Haves:" list. Could be Qualifications or Skills. The distinction: Qualifications often refer to education/experience; Skills refer to technical abilities. Must Haves includes degree/experience, graph solutions, GraphRAG, Python/SQL/AWS, ability to translate business capability, ownership of quality etc. Nice to Haves includes specific AI services, Model Context Protocol, insurance experience, leadership across teams. So we could put Must Haves under Requirements, Nice to Haves under Skills (or Qualifications). Let's put Nice to Haves under Skills.
Now About the role: combine "The Role at a Glance" paragraph and maybe "What’s it like to work here?" paragraph. Also maybe include Alternate Locations and Work Arrangement? Work Arrangement goes to Schedule. Alternate Locations maybe could be part of About the role? Could be a short p under About the role. Or we could drop it? It's substantive; we should preserve. So include in About the role as a paragraph.
Relocation assistance: "is not available for this opportunity." That's also substantive; could be part of About the role or maybe a note. We'll include in About the role.
Requisition #: fold into short p or drop. We'll include a short p maybe under About the role as metadata.
Now Responsibilities: "What You'll Be Doing" bullet points (actually each line starts with a verb). We'll make
- for each.
Benefits: "What’s in it for you:" list items. We'll make
- .
Schedule: Work Arrangement: Hybrid: Employee will work 3 days a week in a Lincoln office. We'll put in
.
Now we need to ensure we don't include boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the large sections about EEO, fraud warnings, political contribution policy, E-Verify, etc. Also remove "Application Deadline" maybe? That's application instruction; we should remove. Also remove "What’s it like to work here?" we kept but maybe it's not boilerplate; it's culture description. Keep.
Also remove "About The Company" maybe? That's generic but still substantive about Lincoln Financial. Could be considered boilerplate? It's describing the company; might be okay to keep but we have limited headings. Could include under About the role as extra paragraph. But we already have culture. Might be okay to include a short paragraph about company. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine company description into About the role.
Let's extract the company description paragraph: "Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, life insurance, group protection, and retirement plan services. With our 120-year track record of expertise and integrity, millions of customers trust our solutions and service to help put their goals in reach. Lincoln Financial Distributors, a broker-dealer, is the wholesale distribution organization of Lincoln Financial. Lincoln Financial is the marketing name for Lincoln Financial Corporation and its affiliates including The Lincoln National Life Insurance Company, Fort Wayne, IN, and Lincoln Life & Annuity Company of New York, Syracuse, NY. Lincoln Financial affiliates, their distributors, and their respective employees, representatives and/or insurance agents do not provide tax, accounting or legal advice." This is substantive; we can include.
Now we need to ensure we don't duplicate content. We'll produce HTML:
About the role
Alternate Locations: Radnor, PA (Pennsylvania); Charlotte, NC (North Carolina); Fort Wayne, IN (Indiana); Greensboro, NC (North Carolina). Work Arrangement: Hybrid – Employee will work 3 days a week in a Lincoln office. Relocation assistance: is not available for this opportunity. Requisition #: 76678.
The Role at a Glance: Lincoln Financial's AI, Data and Analytics (AIDA) organization is building the capabilities required for an AI-enabled business. Within AIDA, Data Strategy & Governance turns priority insurance and retirement use cases into governed, reusable data products and services. We work backward from the decisions and actions AI agents and applications must support, then build the common meaning, quality, metadata, lineage, and secure access needed to trust the result. We deliver with AIDA's infrastructure, platform, engineering, MLOps, and AI-native platform teams, with governance built into the product. As a Senior Data Engineer, you will lead the end-to-end technical direction and delivery of complex AI-ready data products. You will connect priority business and AI use cases to the data capabilities beneath them, including shared meaning, rules, quality, lineage, secure access, and reusable services. You will also lead hands-on graph and GraphRAG delivery where relationships and unstructured knowledge matter, while choosing simpler relational, search, or rules-based patterns when they fit better.
What’s it like to work here? At Lincoln Financial, we love what we do. We make meaningful contributions each and every day to empower our customers to take charge of their lives. Working alongside dedicated and talented colleagues, we build fulfilling careers and stronger communities through a company that values our unique perspectives, insights and contributions and invests in programs that empower each of us to take charge of our own future.
About The Company: Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, life insurance, group protection, and retirement plan services. With our 120-year track record of expertise and integrity, millions of customers trust our solutions and service to help put their goals in reach. Lincoln Financial Distributors, a broker-dealer, is the wholesale distribution organization of Lincoln Financial. Lincoln Financial is the marketing name for Lincoln Financial Corporation and its affiliates including The Lincoln National Life Insurance Company, Fort Wayne, IN, and Lincoln Life & Annuity Company of New York, Syracuse, NY. Lincoln Financial affiliates, their distributors, and their respective employees, representatives and/or insurance agents do not provide tax, accounting or legal advice.
Then Responsibilities:
Responsibilities
- Lead discovery with business and product owners, domain experts, stewards, source owners, and partner AIDA pillars to define the questions, actions, outcomes, product boundaries, and accountable owners.
- Design the product's canonical and consumer models, ontology and semantic layer, business rules, contracts, interfaces, quality controls, metadata, lineage, provenance, and secure access.
- Design and build graph models in Amazon Neptune or comparable technology, including entities, relationships, effective dates, rules, provenance, SPARQL queries, and performance tuning.
- Implement GraphRAG and hybrid graph-vector retrieval, including ingestion, entity and relationship extraction, embeddings, graph enrichment, filtering, retrieval, reranking, grounding, and citations.
- Design and build AWS source-to
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to extract relevant content: Alternate Locations, Work Arrangement, Relocation assistance, Requisition # (fold into short p or drop). The Role at a Glance (maybe About the role). Then "What You'll Be Doing" (Responsibilities). Then "What We’re Looking For" with Must Haves and Nice to Haves (Requirements/Qualifications/Skills). Then "What’s it like to work here?" maybe not needed? It's generic fluff; maybe we can include as About the role? But we should avoid filler. It's somewhat generic but still substantive? It's about culture; could be included under About the role or maybe omitted as not essential? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep culture description if it's substantive. However we need to avoid boilerplate like EEO etc. The culture paragraph is not boilerplate; it's specific to Lincoln Financial. So we can include maybe under About the role or a separate section like "About the Company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have "What’s it like to work here?" could be considered About the role or maybe we can put under About the role. Also "What’s in it for you:" includes benefits: career tracks, leadership development, PTO/parental leave, competitive 401K and employee benefits, free financial counseling, health coaching, employee assistance program, tuition assistance program, work arrangements that work for you, effective productivity/technology tools and training. That's benefits. So we need a Benefits section. Pay: The posting includes "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range and could vary above and below the listed range as permitted by applicable law." It does not give actual numbers. It says pay range is ??? Not specified. It says "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range". This is vague; no actual numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state there is a pay range but doesn't give numbers; still it's stating something about pay. However it's essentially filler: "The pay range for this position is with anticipated pay for new hires between the minimum and midpoint of the range and could vary above and below the listed range as permitted by applicable law." This is not a concrete range; it's generic. Might be considered placeholder? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "varies". So we should NOT create a Pay section because it's not specific. So we omit Pay. Schedule: Work Arrangement: Hybrid : Employee will work 3 days a week in a Lincoln office. That's schedule info. So we can include a Schedule section. Benefits: we have "What’s in it for you:" list. So Benefits section. Now we need to decide sections: About the role (maybe from "The Role at a Glance" and maybe also "What’s it like to work here?"), Responsibilities (What You'll Be Doing), Requirements (Must Haves), Qualifications (maybe Nice to Haves?), Skills (maybe combine). But we should prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But headings are predefined; we can use them if we have content. We have Must Haves and Nice to Haves; we could put Must Haves under Requirements, Nice to Haves under Qualifications or Skills. Or we could put all under Requirements and leave Qualifications empty (but we shouldn't emit empty headings). So we need to allocate. We have "Must Haves:" list of items. That's requirements. "Nice to Haves:" list. Could be Qualifications or Skills. The distinction: Qualifications often refer to education/experience; Skills refer to technical abilities. Must Haves includes degree/experience, graph solutions, GraphRAG, Python/SQL/AWS, ability to translate business capability, ownership of quality etc. Nice to Haves includes specific AI services, Model Context Protocol, insurance experience, leadership across teams. So we could put Must Haves under Requirements, Nice to Haves under Skills (or Qualifications). Let's put Nice to Haves under Skills. Now About the role: combine "The Role at a Glance" paragraph and maybe "What’s it like to work here?" paragraph. Also maybe include Alternate Locations and Work Arrangement? Work Arrangement goes to Schedule. Alternate Locations maybe could be part of About the role? Could be a short p under About the role. Or we could drop it? It's substantive; we should preserve. So include in About the role as a paragraph. Relocation assistance: "is not available for this opportunity." That's also substantive; could be part of About the role or maybe a note. We'll include in About the role. Requisition #: fold into short p or drop. We'll include a short p maybe under About the role as metadata. Now Responsibilities: "What You'll Be Doing" bullet points (actually each line starts with a verb). We'll make
- for each.
Benefits: "What’s in it for you:" list items. We'll make
- .
Schedule: Work Arrangement: Hybrid: Employee will work 3 days a week in a Lincoln office. We'll put in
. Now we need to ensure we don't include boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the large sections about EEO, fraud warnings, political contribution policy, E-Verify, etc. Also remove "Application Deadline" maybe? That's application instruction; we should remove. Also remove "What’s it like to work here?" we kept but maybe it's not boilerplate; it's culture description. Keep. Also remove "About The Company" maybe? That's generic but still substantive about Lincoln Financial. Could be considered boilerplate? It's describing the company; might be okay to keep but we have limited headings. Could include under About the role as extra paragraph. But we already have culture. Might be okay to include a short paragraph about company. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine company description into About the role. Let's extract the company description paragraph: "Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, life insurance, group protection, and retirement plan services. With our 120-year track record of expertise and integrity, millions of customers trust our solutions and service to help put their goals in reach. Lincoln Financial Distributors, a broker-dealer, is the wholesale distribution organization of Lincoln Financial. Lincoln Financial is the marketing name for Lincoln Financial Corporation and its affiliates including The Lincoln National Life Insurance Company, Fort Wayne, IN, and Lincoln Life & Annuity Company of New York, Syracuse, NY. Lincoln Financial affiliates, their distributors, and their respective employees, representatives and/or insurance agents do not provide tax, accounting or legal advice." This is substantive; we can include. Now we need to ensure we don't duplicate content. We'll produce HTML:
About the role
Alternate Locations: Radnor, PA (Pennsylvania); Charlotte, NC (North Carolina); Fort Wayne, IN (Indiana); Greensboro, NC (North Carolina). Work Arrangement: Hybrid – Employee will work 3 days a week in a Lincoln office. Relocation assistance: is not available for this opportunity. Requisition #: 76678.
The Role at a Glance: Lincoln Financial's AI, Data and Analytics (AIDA) organization is building the capabilities required for an AI-enabled business. Within AIDA, Data Strategy & Governance turns priority insurance and retirement use cases into governed, reusable data products and services. We work backward from the decisions and actions AI agents and applications must support, then build the common meaning, quality, metadata, lineage, and secure access needed to trust the result. We deliver with AIDA's infrastructure, platform, engineering, MLOps, and AI-native platform teams, with governance built into the product. As a Senior Data Engineer, you will lead the end-to-end technical direction and delivery of complex AI-ready data products. You will connect priority business and AI use cases to the data capabilities beneath them, including shared meaning, rules, quality, lineage, secure access, and reusable services. You will also lead hands-on graph and GraphRAG delivery where relationships and unstructured knowledge matter, while choosing simpler relational, search, or rules-based patterns when they fit better.
What’s it like to work here? At Lincoln Financial, we love what we do. We make meaningful contributions each and every day to empower our customers to take charge of their lives. Working alongside dedicated and talented colleagues, we build fulfilling careers and stronger communities through a company that values our unique perspectives, insights and contributions and invests in programs that empower each of us to take charge of our own future.
About The Company: Lincoln Financial (NYSE: LNC) helps people to confidently plan for their version of a successful future. We focus on identifying a clear path to financial security, with products including annuities, life insurance, group protection, and retirement plan services. With our 120-year track record of expertise and integrity, millions of customers trust our solutions and service to help put their goals in reach. Lincoln Financial Distributors, a broker-dealer, is the wholesale distribution organization of Lincoln Financial. Lincoln Financial is the marketing name for Lincoln Financial Corporation and its affiliates including The Lincoln National Life Insurance Company, Fort Wayne, IN, and Lincoln Life & Annuity Company of New York, Syracuse, NY. Lincoln Financial affiliates, their distributors, and their respective employees, representatives and/or insurance agents do not provide tax, accounting or legal advice.
Then Responsibilities:Responsibilities
- Lead discovery with business and product owners, domain experts, stewards, source owners, and partner AIDA pillars to define the questions, actions, outcomes, product boundaries, and accountable owners.
- Design the product's canonical and consumer models, ontology and semantic layer, business rules, contracts, interfaces, quality controls, metadata, lineage, provenance, and secure access.
- Design and build graph models in Amazon Neptune or comparable technology, including entities, relationships, effective dates, rules, provenance, SPARQL queries, and performance tuning.
- Implement GraphRAG and hybrid graph-vector retrieval, including ingestion, entity and relationship extraction, embeddings, graph enrichment, filtering, retrieval, reranking, grounding, and citations.
- Design and build AWS source-to
- .
Schedule: Work Arrangement: Hybrid: Employee will work 3 days a week in a Lincoln office. We'll put in