Lead Software Development Engineer
for each heading. Only include sections when posting has real specific content. We need to parse the posting.
We have description: "The application deadline is being extended to September 18, 2026" - that's metadata, not a section.
Job Location: remote work model.
About Envestnet: description of company.
The Team You’ll Join: description.
How You’ll Contribute: responsibilities.
What You’ll Need to Bring: requirements/qualifications/skills.
Why You’ll Enjoy Working at Envestnet: benefits? Actually it's about culture.
Sponsorship: visa sponsorship.
Our Investment in You: salary range, benefits.
Our Commitment to Inclusion & Belonging: EEO boilerplate (remove).
Recruitment Fraud: remove.
We need to map to headings: About the role (maybe combine About Envestnet and The Team You’ll Join?), Responsibilities (How You’ll Contribute), Requirements (What You’ll Need to Bring includes degree, experience), Qualifications (maybe same as Requirements?), Skills (technologies), Benefits (Our Investment in You benefits), Pay (salary range), Schedule (maybe remote work model? Not explicit schedule; remote work model is location, not schedule. No schedule info, so omit Schedule section.)
We must not repeat job title as heading. No Job ID.
We must not include boilerplate like EEO, fraud, etc.
We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for headings, - for lists,
for prose.
We need to decide sections:
- About the role: could include About Envestnet and The Team You’ll Join? Might be better to have About the role as a short paragraph summarizing role? But we must not invent content. We could put About Envestnet and The Team You’ll Join under About the role heading, as they describe role context. That's acceptable.
- Responsibilities: from How You’ll Contribute.
- Requirements: maybe degree requirement? Could be under Requirements.
- Qualifications: maybe similar to Requirements? Might be redundant. Better to have Requirements for degree and experience, Qualifications for specific technical background? But we need to avoid thin sections. Let's think: The posting has "What You’ll Need to Bring" which includes degree, technical background, experience with .NET, etc., experience with AWS, Kubernetes, AI/ML, etc., agentic coding tools, fintech experience. That's a lot of detail. Could split into Requirements (degree, years experience) and Skills (technologies). Qualifications maybe not needed.
But we need to follow instruction: Use headings only when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications if we have distinct content (like Bachelor's degree required, master's preferred). That could be under Requirements. Qualifications could be about experience leading architectural decisions, etc. But that's also in What You’ll Need to Bring. Might be better to have Requirements (education + years experience) and Qualifications (leadership, architectural decision making, etc.) and Skills (specific tech stack). However we need to avoid filler.
Let's extract content:
About Envestnet: paragraph about company.
The Team You’ll Join: paragraph about team.
How You’ll Contribute: list of responsibilities (many bullet-like sentences). We can turn into
- .
What You’ll Need to Bring: list of requirements: degree, technical background (.NET, xUnit, Reqnroll, RESTful APIs, Apigee), experience with PostgreSQL, SQL Server, Redis, ElastiCache, AWS services, Kubernetes, Docker, Kafka, CloudFormation, CDK, Terraform, DevOps practices, automation, agile delivery, Scrum, TDD, 2+ years designing AI/ML systems, LLM-based applications, AI platform capabilities, agentic workflows, Python-based AI/ML support, AI cost control, evaluation, governance, LLM integration patterns, stateful agents, memory patterns, practical AI use case delivery, event-driven architectures, Kafka or async messaging, cloud infrastructure (AWS, GCP, Azure), observability practices, ability to lead architectural decisions, define technical standards, conduct code reviews, communicate trade-offs, experience in fintech, reporting, real-time financial platforms, regulated production environments, data consistency, idempotency, fault tolerance, scalability, hands-on experience using agentic coding tools (Claude Code or GitHub Copilot) to accelerate feature delivery, code review, testing, SDLC execution.
Why You’ll Enjoy Working at Envestnet: paragraph about impact, flexibility, rewards, development.
Our Investment in You: salary range $152,300 to $190,400 base, incentive component, benefits list: medical insurance, PTO, 401k company match, paid parental leave, education reimbursement, disability coverage, mental health & wellness support.
Sponsorship: visa sponsorship statement.
We need to include Benefits section: list of benefits.
Pay section: salary range.
Schedule: not present, omit.
We also might include a short paragraph about remote work model under About the role or maybe as its own section? There's no heading for location; we could incorporate into About the role as a sentence.
We must not include boilerplate like EEO, fraud, etc.
Now produce HTML.
Structure:
About the role
... combine About Envestnet, The Team You’ll Join, and remote work model.
Responsibilities
- ...
...
Requirements
Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field required; master’s degree preferred.
2+ years designing, delivering, or integrating production-grade AI/ML systems, LLM-based applications, AI platform capabilities, and agentic workflows.
But maybe we should also include experience with .NET etc under Skills.
Skills
- Strong technical background with .NET, xUnit, Reqnroll, RESTful APIs, and API management solutions such as Apigee.
- Experience with PostgreSQL, SQL Server, Redis, and ElastiCache.
- Experience with AWS services including EC2, S3, ELB, ASG, API Gateway, Lambda, RDS, EKS, CloudWatch, SQS.
- Experience with Kubernetes, Docker, Kafka, CloudFormation, CDK, Terraform, DevOps practices, automation, agile delivery, Scrum, and test-driven development.
- Experience with Python-based AI/ML application support, enhancement, maintenance, reliability, scalability, and production readiness.
- Strong knowledge of AI cost control, evaluation, governance, LLM integration patterns, stateful agents, memory patterns, and practical AI use case delivery.
- Experience with event-driven architectures, Kafka or asynchronous messaging, cloud infrastructure such as AWS, GCP, or Azure, and observability practices.
- Demonstrated ability to lead architectural decisions, define technical standards, conduct code reviews, and communicate trade-offs to technical and non-technical stakeholders.
- Experience in fintech, reporting, real-time financial platforms, regulated production environments, or other domains requiring strong data consistency, idempotency, fault tolerance, and scalability.
- Hands-on experience using agentic coding tools such as Claude Code or GitHub Copilot to accelerate feature delivery, code review, testing, and SDLC execution.
But some of those overlap with responsibilities; but okay.
We need to ensure we don't duplicate content. The responsibilities list includes many items that also appear in skills; but we can keep responsibilities as the list of duties from How You’ll Contribute. Skills list can be the technical stack.
Let's extract responsibilities from How You’ll Contribute:
- Building scalable, secure platforms in support of Envestnet business operations, including wealth management, financial data aggregation and advisor-driven technology solutions.
- Works across cloud-based architectures, integrating complex data sources and APIs to deliver reliable, high-performance systems.
- Collaborates with product managers, data scientists and compliance stakeholders to meet both business and regulatory requirements.
- Architects and designs systems, services, or platforms with broad impact.
- Leads technical decision-making for major features or initiatives.
- Breaks down complex problems into scalable and maintainable solutions.
- Drives cross-team collaboration and align technical solutions with business goals.
- Establishes and enforces best practices in architecture, coding, and deployment.
- Mentors engineers across multiple levels and contribute to talent development.
- Anticipates technical risks and proactively implement mitigation strategies.
- Leads incident response and root cause analysis for critical issues.
- Influences roadmap planning through technical insight and feasibility analysis.
- Partners with DevOps/SRE to improve system reliability, deployment automation, and observability.
- Designs and maintains CI/CD pipelines for owned services, improving deployment speed and safety.
- Implements infrastructure-aware design decisions (scalability, failover, resiliency, cost).
- Leads the design and delivery of scalable reporting solutions, leveraging Java and/or Python, cloud infrastructure, RESTful APIs, event-driven architectures, and SQL/NoSQL technologies.
- Specializes in AI/ML integration, LLM-based capabilities, and AI platform engineering, including the support and enhancement of production AI/ML applications.
- Utilizes agentic coding tools and AI-enabled development practices to accelerate feature delivery, improve code quality, and enhance software development lifecycle efficiency.
- Partners with business, product, and quality engineering stakeholders to translate complex requirements into robust, maintainable solutions and ensure successful end-to-end delivery.
We'll put each as - .
Now Requirements: maybe just degree and years experience? Could also include visa sponsorship? That's separate.
We could have Requirements: Bachelor’s degree required; master’s preferred. 2+ years AI/ML experience.
Qualifications: maybe leadership, architectural decision making, mentoring, etc. But we already have some in responsibilities. Might be redundant.
Better to have Requirements (education + experience) and Skills (technical stack). Qualifications maybe not needed.
Benefits: list from Our Investment in You.
Pay: salary range.
We also have sponsorship statement: "This position is open to candidates requiring visa sponsorship". Could be placed under About the role or a short paragraph. Not a heading.
Let's craft About the role paragraph:
Combine About Envestnet, The Team You’ll Join, and remote work model.
About Envestnet paragraph: "Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights, and industry leading support. Backed by over 25 years of experience and approximately $7.0 trillion in platform assets, Envestnet is trusted by over one third of financial advisors across leading banks, wealth managers, brokerages, and RIAs."
The Team You’ll Join: "You will join a collaborative engineering team focused on building scalable, data-driven reporting solutions and advancing AI-enabled capabilities for financial services. As a Lead Engineer, you’ll work closely with engineers, product partners, and stakeholders to drive technical decisions, deliver high-impact features, and align solutions to business goals. The team emphasizes modern architectures, AI/ML and LLM-based innovation, and strong engineering practices—leveraging cloud technologies and agentic coding tools to improve reliability, accelerate delivery, and continuously enhance reporting capabilities."
Remote work model: "The primary work location for this role is a remote work model."
We can combine into a paragraph or multiple paragraphs. Use
for prose; we can have multiple
under the heading.
Now Benefits: list: medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage and mental health & wellness support.
We'll put as
- .
Pay:
The
- for lists,
for prose. We need to decide sections: - About the role: could include About Envestnet and The Team You’ll Join? Might be better to have About the role as a short paragraph summarizing role? But we must not invent content. We could put About Envestnet and The Team You’ll Join under About the role heading, as they describe role context. That's acceptable. - Responsibilities: from How You’ll Contribute. - Requirements: maybe degree requirement? Could be under Requirements. - Qualifications: maybe similar to Requirements? Might be redundant. Better to have Requirements for degree and experience, Qualifications for specific technical background? But we need to avoid thin sections. Let's think: The posting has "What You’ll Need to Bring" which includes degree, technical background, experience with .NET, etc., experience with AWS, Kubernetes, AI/ML, etc., agentic coding tools, fintech experience. That's a lot of detail. Could split into Requirements (degree, years experience) and Skills (technologies). Qualifications maybe not needed. But we need to follow instruction: Use headings only when posting has real specific content for it. So we can include About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications if we have distinct content (like Bachelor's degree required, master's preferred). That could be under Requirements. Qualifications could be about experience leading architectural decisions, etc. But that's also in What You’ll Need to Bring. Might be better to have Requirements (education + years experience) and Qualifications (leadership, architectural decision making, etc.) and Skills (specific tech stack). However we need to avoid filler. Let's extract content: About Envestnet: paragraph about company. The Team You’ll Join: paragraph about team. How You’ll Contribute: list of responsibilities (many bullet-like sentences). We can turn into
- .
What You’ll Need to Bring: list of requirements: degree, technical background (.NET, xUnit, Reqnroll, RESTful APIs, Apigee), experience with PostgreSQL, SQL Server, Redis, ElastiCache, AWS services, Kubernetes, Docker, Kafka, CloudFormation, CDK, Terraform, DevOps practices, automation, agile delivery, Scrum, TDD, 2+ years designing AI/ML systems, LLM-based applications, AI platform capabilities, agentic workflows, Python-based AI/ML support, AI cost control, evaluation, governance, LLM integration patterns, stateful agents, memory patterns, practical AI use case delivery, event-driven architectures, Kafka or async messaging, cloud infrastructure (AWS, GCP, Azure), observability practices, ability to lead architectural decisions, define technical standards, conduct code reviews, communicate trade-offs, experience in fintech, reporting, real-time financial platforms, regulated production environments, data consistency, idempotency, fault tolerance, scalability, hands-on experience using agentic coding tools (Claude Code or GitHub Copilot) to accelerate feature delivery, code review, testing, SDLC execution.
Why You’ll Enjoy Working at Envestnet: paragraph about impact, flexibility, rewards, development.
Our Investment in You: salary range $152,300 to $190,400 base, incentive component, benefits list: medical insurance, PTO, 401k company match, paid parental leave, education reimbursement, disability coverage, mental health & wellness support.
Sponsorship: visa sponsorship statement.
We need to include Benefits section: list of benefits.
Pay section: salary range.
Schedule: not present, omit.
We also might include a short paragraph about remote work model under About the role or maybe as its own section? There's no heading for location; we could incorporate into About the role as a sentence.
We must not include boilerplate like EEO, fraud, etc.
Now produce HTML.
Structure:
About the role
... combine About Envestnet, The Team You’ll Join, and remote work model.
Responsibilities
- ... ...
Requirements
Bachelor’s degree in Computer Science, Engineering, Information Systems, or related field required; master’s degree preferred.
2+ years designing, delivering, or integrating production-grade AI/ML systems, LLM-based applications, AI platform capabilities, and agentic workflows.
But maybe we should also include experience with .NET etc under Skills.Skills
- Strong technical background with .NET, xUnit, Reqnroll, RESTful APIs, and API management solutions such as Apigee.
- Experience with PostgreSQL, SQL Server, Redis, and ElastiCache.
- Experience with AWS services including EC2, S3, ELB, ASG, API Gateway, Lambda, RDS, EKS, CloudWatch, SQS.
- Experience with Kubernetes, Docker, Kafka, CloudFormation, CDK, Terraform, DevOps practices, automation, agile delivery, Scrum, and test-driven development.
- Experience with Python-based AI/ML application support, enhancement, maintenance, reliability, scalability, and production readiness.
- Strong knowledge of AI cost control, evaluation, governance, LLM integration patterns, stateful agents, memory patterns, and practical AI use case delivery.
- Experience with event-driven architectures, Kafka or asynchronous messaging, cloud infrastructure such as AWS, GCP, or Azure, and observability practices.
- Demonstrated ability to lead architectural decisions, define technical standards, conduct code reviews, and communicate trade-offs to technical and non-technical stakeholders.
- Experience in fintech, reporting, real-time financial platforms, regulated production environments, or other domains requiring strong data consistency, idempotency, fault tolerance, and scalability.
- Hands-on experience using agentic coding tools such as Claude Code or GitHub Copilot to accelerate feature delivery, code review, testing, and SDLC execution.
- .
Now Requirements: maybe just degree and years experience? Could also include visa sponsorship? That's separate.
We could have Requirements: Bachelor’s degree required; master’s preferred. 2+ years AI/ML experience.
Qualifications: maybe leadership, architectural decision making, mentoring, etc. But we already have some in responsibilities. Might be redundant.
Better to have Requirements (education + experience) and Skills (technical stack). Qualifications maybe not needed.
Benefits: list from Our Investment in You.
Pay: salary range.
We also have sponsorship statement: "This position is open to candidates requiring visa sponsorship". Could be placed under About the role or a short paragraph. Not a heading.
Let's craft About the role paragraph:
Combine About Envestnet, The Team You’ll Join, and remote work model.
About Envestnet paragraph: "Envestnet is an adaptive WealthTech company that is redefining the future of wealth management by helping advisors meet the moment with its comprehensive technology, actionable insights, and industry leading support. Backed by over 25 years of experience and approximately $7.0 trillion in platform assets, Envestnet is trusted by over one third of financial advisors across leading banks, wealth managers, brokerages, and RIAs."
The Team You’ll Join: "You will join a collaborative engineering team focused on building scalable, data-driven reporting solutions and advancing AI-enabled capabilities for financial services. As a Lead Engineer, you’ll work closely with engineers, product partners, and stakeholders to drive technical decisions, deliver high-impact features, and align solutions to business goals. The team emphasizes modern architectures, AI/ML and LLM-based innovation, and strong engineering practices—leveraging cloud technologies and agentic coding tools to improve reliability, accelerate delivery, and continuously enhance reporting capabilities."
Remote work model: "The primary work location for this role is a remote work model."
We can combine into a paragraph or multiple paragraphs. Use
for prose; we can have multiple
under the heading. Now Benefits: list: medical insurance, paid time off (PTO), 401k company match, paid parental leave, education reimbursement, disability coverage and mental health & wellness support. We'll put as
- .
Pay:
The
- .
Pay:
- .
What You’ll Need to Bring: list of requirements: degree, technical background (.NET, xUnit, Reqnroll, RESTful APIs, Apigee), experience with PostgreSQL, SQL Server, Redis, ElastiCache, AWS services, Kubernetes, Docker, Kafka, CloudFormation, CDK, Terraform, DevOps practices, automation, agile delivery, Scrum, TDD, 2+ years designing AI/ML systems, LLM-based applications, AI platform capabilities, agentic workflows, Python-based AI/ML support, AI cost control, evaluation, governance, LLM integration patterns, stateful agents, memory patterns, practical AI use case delivery, event-driven architectures, Kafka or async messaging, cloud infrastructure (AWS, GCP, Azure), observability practices, ability to lead architectural decisions, define technical standards, conduct code reviews, communicate trade-offs, experience in fintech, reporting, real-time financial platforms, regulated production environments, data consistency, idempotency, fault tolerance, scalability, hands-on experience using agentic coding tools (Claude Code or GitHub Copilot) to accelerate feature delivery, code review, testing, SDLC execution.
Why You’ll Enjoy Working at Envestnet: paragraph about impact, flexibility, rewards, development.
Our Investment in You: salary range $152,300 to $190,400 base, incentive component, benefits list: medical insurance, PTO, 401k company match, paid parental leave, education reimbursement, disability coverage, mental health & wellness support.
Sponsorship: visa sponsorship statement.
We need to include Benefits section: list of benefits.
Pay section: salary range.
Schedule: not present, omit.
We also might include a short paragraph about remote work model under About the role or maybe as its own section? There's no heading for location; we could incorporate into About the role as a sentence.
We must not include boilerplate like EEO, fraud, etc.
Now produce HTML.
Structure: