Jobs · Engineering · Minnesota

Lead Data Engineer - Data Scientist

Wells Fargo · Minneapolis, MN · 1 mo ago
Engineering$119k–$206k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. We have content: About the role (first paragraph). Responsibilities: list of duties (the bullet-like sentences). Requirements: required qualifications (5+ years DB engineering, 5+ years Python etc). Qualifications: desired qualifications (list). Skills: maybe combine? Could treat required and desired as Qualifications? But we need separate sections if content exists. We have "Required Qualifications:" and "Desired Qualifications:" plus many skill-like items. Could map: Responsibilities: the bullet list after "In This Role, You Will". Requirements: maybe the required qualifications. Qualifications: desired qualifications. Skills: maybe the list of skills like "Strong SQL skills..." etc. Benefits: we have benefits list. Pay: we have salary range. Schedule: not mentioned (no schedule info). So omit Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Also remove "Posting End Date", "Posting Statements", etc. Keep location? Might be considered metadata; we could fold into short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is minor metadata; we can include in a p after About the role maybe. But we need to preserve ALL substantive information; location is substantive? It's location of job; maybe we keep as a p. However they said "fold minor metadata into a short

or drop it." Location could be considered minor metadata; we can include in a p. We must not include sections with filler like "commensurate with experience". Not present. We need to use

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

    for prose. We need to preserve all substantive information: responsibilities list, required qualifications, desired qualifications, skills list, benefits list, pay range, location. We need to avoid repeating content. Let's extract: About the role: "Wells Fargo is seeking a Lead Data Engineer in Cybersecurity as part of Identity Access Management. Learn more about career areas and business divisions at wellsfargojobs.com This role sits at the intersection of cybersecurity, data science, machine learning, and AI. The successful candidate will develop intelligent solutions that improve access governance, identify anomalous behavior, automate entitlement decisions, and generate actionable insights across Wells Fargo's Identity and Access Management ecosystem." We could keep that as a p. Responsibilities: The bullet list after "In This Role, You Will". Let's list each sentence as li. - Lead complex initiatives with broad impact and act as key participant in large scale software planning for the Identity and Access management. - Design, develop, and run tooling to discover problems in data and applications and report the issues to engineering and product leadership - Apply knowledge of statistical and data science methods and techniques to business problems relating to Identity and Access Management. - Serve as a subject matter expert on ML, AI and the application of mathematical and statistical techniques to large datasets. - Design, support and operate data pipelines, data models, dashboards, and API integrations to deliver real-time and batch analytics use cases. - Design and conduct experiments, statistical analyses, and hypothesis testing to evaluate proposals in support of controls, policies, and operational processes. - Build AI-powered capabilities that identify inappropriate access, recommend entitlements before users request them, and detect anomalous behavior across millions of identity events. - Lead other IAM team members including operations, onboarding, initiatives and engineering teams as well as line of business and lines of defense teams to understand analytical needs and translate them into technical solutions. - Establish and implement engineering and analytical best practices when developing solutions. - Develop solutions in accordance with established security, privacy, model risk, and regulatory guidelines. - Develop, test, deploy and support of ML-enabled analytical solutions and guide other members of the team in ML, AI and statistical techniques in driving adoption of AI/ML across IAM. - Assist in monitoring model health, reliability, and drift to ensure continuous improvement and required remediation. - Demonstrate proficiency in using AI-assisted development and analysis tools (e.g., GitHub Copilot and approved code-centric agents) - Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting - Apply strong technical judgment when validating and integrating AI-assisted outputs into solutions - Understand and account for model limitations, security risks, and operational considerations - Apply AI responsibly in development and production environments - Ensure AI usage aligns with security, compliance, privacy, and ethical standards That's many. Required Qualifications: "5+ years of Database Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education" and "5+ years of experience with Python data science libraries such as Pandas, NumPy, and Scikit-Learn, together with exposure to a deep learning framework such as TensorFlow or PyTorch". Could be two li. Desired Qualifications: list many items. Let's extract each bullet after "Desired Qualifications:": - Knowledge of Vertex AI, GCP environments, BigQuery and getting models into production on these platforms - Knowledge of graph networks for anomaly detection (Neo4j) - A learning mindset that keeps up-to-date with the latest developments in the field - Knowledge of Github for code management, Power BI, Tableau, Alteryx - Understanding of software engineering fundamentals including testing, debugging, code reviews etc is highly desirable - Knowledge of the mathematical foundations of statistics, machine learning, and modern AI techniques. - Strong understanding of model evaluation techniques, particularly for classification and clustering models including metrics such as precision, accuracy, F1-scores, confusion matrices, ROC curves etc. - High level of comfort with the use of AI coding agents such as Github Copilot, Claude Code, Cursor, Devin or others with the ability to critically examine AI code for fitness for use. - Familiarity with LLMs, RAG, and AI agents - Strong SQL skills and ability to work with relational and analytical databases. - Strong book-of-work management and organizational skills. - Hands-on ability to manipulate data and tools to prototype and present solutions. - Confident and self-motivated producer of original ideas and solutions, with sound judgment for when to escalate issues - Strong written and verbal communicator with excellent presentation skills - Ability to communicate complex technical concepts to colleagues and team members. - Bachelor's or Master's degree in Computer Science, Data Science, AI, Engineering, or related field. We could treat these as Skills or Qualifications. Since we already have Required Qualifications and Desired Qualifications sections, we could put Desired Qualifications under Qualifications heading. Then Skills maybe not needed. But we have many skill-like items; maybe we combine Desired Qualifications as Skills. However instruction: Use headings for sections like Skills, Benefits, Pay, Schedule. We can decide to have sections: About the role (p), Responsibilities (ul), Requirements (ul) for required qualifications, Qualifications (ul) for desired qualifications, Benefits (ul), Pay (p). That seems reasonable. We must not create sections with filler. All have content. Location: we can include a p after About the role maybe: "Locations: 300 S Brevard, Charlotte, North Carolina 28202; 401 Las Colinas Blvd W Bldg. A - Irving, TX 75039; 550 S 4th St. Minneapolis, MN 55415; 3075 Loyalty Cir. - Columbus, Ohio 43219". That's substantive. Pay: "$119,000.00 - $206,000.00". Also mention "Salary range is determined by location of the job. May be considered for a discretionary bonus, Restricted Share Rights, or other long - term incentive awards." Also "Pay Range Reflected is the base pay range offered for this position. Pay may vary depending on factors including but not limited to demonstrated examples of prior performance, skills, experience, or work location. Employees may also be eligible for incentive opportunities." We can include that as p. Benefits list: many items. We'll put as ul. Now ensure we don't include boilerplate like EEO, etc. Remove. Now produce HTML fragment. Let's craft:

    About the role

    Wells Fargo is seeking a Lead Data Engineer in Cybersecurity as part of Identity Access Management. Learn more about career areas and business divisions at wellsfargojobs.com This role sits at the intersection of cybersecurity, data science, machine learning, and AI. The successful candidate will develop intelligent solutions that improve access governance, identify anomalous behavior, automate entitlement decisions, and generate actionable insights across Wells Fargo's Identity and Access Management ecosystem.

    Locations: 300 S Brevard, Charlotte, North Carolina 28202; 401 Las Colinas Blvd W Bldg. A - Irving, TX 75039; 550 S 4th St. Minneapolis, MN 55415; 3075 Loyalty Cir. - Columbus, Ohio 43219

    Responsibilities

    • Lead complex initiatives with broad impact and act as key participant in large scale software planning for the Identity and Access management.
    • Design, develop, and run tooling to discover problems in data and applications and report the issues to engineering and product leadership
    • Apply knowledge of statistical and data science methods and techniques to business problems relating to Identity and Access Management.
    • Serve as a subject matter expert on ML, AI and the application of mathematical and statistical techniques to large datasets.
    • Design, support and operate data pipelines, data models, dashboards, and API integrations to deliver real-time and batch analytics use cases.
    • Design and conduct experiments, statistical analyses, and hypothesis testing to evaluate proposals in support of controls, policies, and operational processes.
    • Build AI-powered capabilities that identify inappropriate access, recommend entitlements before users request them, and detect anomalous behavior across millions of identity events.
    • Lead other IAM team members including operations, onboarding, initiatives and engineering teams as well as line of business and lines of defense teams to understand analytical needs and translate them into technical solutions.
    • Establish and implement engineering and analytical best practices when developing solutions.
    • Develop solutions in accordance with established security, privacy, model risk, and regulatory guidelines.
    • Develop, test, deploy and support of ML-enabled analytical solutions and guide other members of the team in ML, AI and statistical techniques in driving adoption of AI/ML across IAM.
    • Assist in monitoring model health, reliability, and drift to ensure continuous improvement and required remediation.
    • Demonstrate proficiency in using AI-assisted development and analysis tools (e.g., GitHub Copilot and approved code-centric agents)
    • Leverage AI to accelerate system design, coding, testing, analysis, and troubleshooting
    • Apply strong technical judgment when validating and integrating AI-assisted outputs into solutions
    • Understand and account for model limitations, security risks, and operational considerations
    • Apply AI responsibly in development and production environments
    • Ensure AI usage aligns with security, compliance, privacy, and ethical standards

    Requirements

    • 5+ years of Database Engineering experience, or equivalent demonstrated through one or a combination of the following: work experience, training, military experience, education
    • 5+ years of experience with Python data science libraries such as Pandas, NumPy, and Scikit-Learn, together with exposure to a deep learning framework such as TensorFlow or PyTorch

Similar jobs

Lead Data Science Engineer

Medidata SolutionsNew York, United States· 3 mo ago
Information Technology$135k–$180k/yrapply on medidata.com

Lead Data Science Engineer

Dassault SystèmesNew York, United States· 3 mo ago
Information Technology$135k–$180k/yrapply on 3ds.com

Lead Data Science Engineer

Health Care Service CorporationChicago, IL· 3 mo ago
Information Technology$121k–$225k/yrapply on careers.hcsc.com