Senior AI Software Engineer — T. Rowe Price Labs (NY or MD)

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Company description (T. Rowe Price) - Role Summary (positions available in NYC or Baltimore) - Responsibilities (list of bullet points) - Business Knowledge (list of bullet points) - Qualifications (Required and Preferred) - FINRA Requirements (not required) - Work Flexibility (hybrid, up to 3 days from home) - What To Expect After Applying (application process details - this is application instructions, should be removed) - Base Salary Ranges (specific ranges by location) - Commitment to Diversity, Equity, and Inclusion (EEO boilerplate - should be removed) - Benefits (list of benefits) I need to structure this into appropriate sections. Let me map: - About the role: Role Summary + maybe company description? The company description is generic marketing. The Role Summary is specific to the role. I'll include Role Summary as "About the role" section. - Responsibilities: The Responsibilities list - Business Knowledge: Could be part of Responsibilities or separate. It's a separate section in the posting. I'll include as "Business Knowledge" or maybe "Requirements"? The instructions say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Business Knowledge is not in that list but it's a substantive section. I'll include it as a section with h3. - Qualifications: Required and Preferred - FINRA Requirements: minor metadata, fold into a short p or drop. It says FINRA licenses not required. Could be a small note. - Work Flexibility: Schedule section - Base Salary Ranges: Pay section - Benefits: Benefits section - What To Expect After Applying: application instructions - remove - Commitment to Diversity...: EEO boilerplate - remove I need to preserve all substantive information. So I'll keep the company description? The instructions say "Preserve ALL substantive information". The company description is generic but it's part of the posting. However, it's not specific to the role. The Role Summary is specific. I'll include the Role Summary as "About the role" and maybe include a brief company description as a paragraph before sections? But the instructions say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Senior Software Engineer" presumably. The posting doesn't explicitly state the title at the top, but the Role Summary says "As a Senior Software Engineer on T. Rowe Price Labs' AI Engineering team". I'll not repeat that as a heading. I'll structure:

  About the role

  Positions are available in our New York City office or with our AI Engineering squad in Harbor Point, Baltimore, MD. In either location, you will join a collaborative team of engineers, product owners, and business partners building high-impact AI products with leverage across the firm. As a Senior Software Engineer on T. Rowe Price Labs' AI Engineering team, you will independently design, build, and scale production-grade AI agents and intelligent systems that solve complex business problems. You will lead technical workstreams, incubate new AI products, experiment with emerging technologies and innovative ideas, and partner with business-aligned technology teams to enable broader adoption at scale. This is a hands-on role for an experienced engineer with strong software fundamentals, practical AI engineering experience, and a product mindset. You will take ownership of complex and ambiguous problems, mentor other engineers, and contribute to the patterns and practices that shape AI engineering at T. Rowe Price.

  Responsibilities

  • Own the end-to-end design and delivery of production-grade AI agents and intelligent systems, including architecture, implementation, testing, evaluation, deployment, observability, and production support.
  • Design agentic workflows using orchestration, tool integration, retrieval-based systems, structured outputs, context management, and appropriate human-in-the-loop patterns.
  • Partner with product owners and business stakeholders to take control of complex or ambiguous problems, evaluate alternative approaches, and translate needs into scalable AI solutions.
  • Lead technical workstreams from rapid experimentation and validation through production adoption.
  • Establish evaluation and testing approaches for non-deterministic AI systems, including quality metrics, regression testing, failure analysis, and production monitoring.
  • Make informed engineering trade-offs across models, prompts, context, tools, latency, cost, reliability, security, and maintainability.
  • Contribute to reusable AI capabilities and shared engineering patterns that improve speed, quality, and consistency across teams.
  • Lead code and design reviews, mentor less-experienced engineers, and help others solve complex technical problems.
  • Own technical debt and continuously improve the quality, reliability, and maintainability of the systems you build.
  • Rapidly evaluate emerging AI technologies and determine when and how they can be applied to deliver meaningful business value.
  • Support the Build-Operate-Transfer model by preparing successful AI solutions for long-term ownership and scale by business-aligned technology teams.

  Business Knowledge

  • Work directly with business stakeholders and product owners to understand priorities, shape solution direction, and deliver measurable outcomes.
  • Translate complex business needs into effective technology solutions and clearly communicate technical trade-offs.
  • Balance innovation, business value, scalability, risk, fiscal responsibility, and long-term maintainability when making technical decisions.

  Qualifications

  Required

  • BS or MS in Computer Science or a related technical field, or equivalent practical experience, with 5+ years of professional software engineering experience.
  • Strong hands-on development experience in object-oriented languages such as Python, Java, or JavaScript/TypeScript.
  • Hands-on experience building AI-enabled applications, intelligent workflows, or agentic systems using modern LLMs and AI development frameworks.
  • Practical experience with modern AI engineering patterns such as agent orchestration, tool/function calling, retrieval-based systems, prompt and context engineering, structured outputs, evaluation, observability, or guardrails.
  • Experience taking AI-enabled systems beyond prototypes toward production, including testing, monitoring, reliability, security, and operational considerations.
  • Strong experience with cloud-native architectures, containerized microservices, APIs, and modern software delivery practices.
  • Strong analytical, problem-solving, software design, and debugging skills.
  • Demonstrated commitment to engineering quality through automated testing, code reviews, observability, and continuous delivery.
  • Ability to independently own complex technical problems and clearly communicate designs, decisions, and trade-offs.
  • A product mindset, strong learning agility, and passion for staying current with the rapidly evolving AI engineering landscape.

  Preferred

  • Experience mentoring engineers or leading technical workstreams.
  • Understanding of financial markets, asset management, or financial instruments.

  FINRA Requirements

  FINRA licenses are not required and will not be supported for this role.

  Schedule

  This role is eligible for hybrid work, with up to three days per week from home.

  Pay

  Base salary ranges by location:

  • $121,000.00 - $206,000.00 for the location of: Maryland, Colorado, Washington and remote workers
  • $133,000.00 - $227,000.00 for the location of: Washington, D.C.
  • $151,000.00 - $258,000.00 for the location of: New York, California

  Placement within the range provided above is based on the individual’s relevant experience and skills for the role. Base salary is only one component of our total compensation package. Employees may be eligible for a discretionary bonus, which is determined upon company and individual performance.

  Benefits

  • Competitive compensation
  • Annual bonus eligibility
  • A generous retirement plan
  • Hybrid work schedule
  • Health and wellness benefits, including online therapy
  • Paid time off for vacation, illness, medical appointments, and volunteering days
  • Family care resources, including fertility and adoption benefits
  I should not include the "What To Expect After Applying" section (application instructions). Also not include the EEO boilerplate. The company description at the very top is generic marketing; I could include it as a paragraph before sections? The instructions say "Preserve ALL substantive information". The company description is not specific to the role but it's part of the posting. However, the Role Summary already includes the key info. I'll include a brief company description as a paragraph before the sections? But the instructions say "Output ONLY the HTML fragment". I think it's okay to include a short intro paragraph about the company. But the instructions say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is not in the provided text? Actually the user provided the entire posting text. The title might be "Senior Software Engineer" but not explicitly at top. The Role Summary mentions it. I'll not add a heading for the job title. I'll include a short paragraph about the company from the first paragraph? It's generic but it's part of the posting. I'll include it as a

  before the sections. Let me craft the final HTML fragment. I'll not use

  because the instructions only mention

  for section headings. But they didn't forbid

  . However, they said "use

  for section headings". For sub-sections like Required/Preferred, I could use

  or just use or

  . I'll use

  for sub-headings within Qualifications. That's acceptable. But to be safe, I'll use

  for main sections and maybe for Required/Preferred. However, the instructions say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot use other heading levels. I'll use

  for main sections and

  for sub-sections. Now, I need to ensure I don't include any boilerplate. The "Commitment to Diversity, Equity, and Inclusion" is EEO boilerplate - remove. The "What To Expect After Applying" is application instructions - remove. The "Learn More About Our Benefits." is a link - remove. The "T. Rowe