Forward Deployed Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: About Praxent (company description), The mission, What you will own, How we work, What you bring, How you work: our CAN/DO values in practice, What you’ll love about us, Pay info. We must use

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

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings. 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 decide which sections to include based on content. We have: - About Praxent (company description) – could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "About Praxent" which is company overview. Could map to "About the role"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We have content that maps to: - About the role: maybe combine mission, what you will own, how we work? But we need to preserve all substantive info. Could create sections: About the role (mission + what you will own + how we work?), Responsibilities (what you will own?), Requirements (what you bring?), Qualifications (maybe same as requirements?), Skills (maybe fluency in Python/TS etc.), Benefits (what you’ll love about us includes PTO, medical etc.), Pay (salary range). Schedule not mentioned. We must not create sections with filler. So we need to ensure each heading has substantive content. Let's extract substantive content: Company description: About Praxent (first paragraph). This is about the company, not role. Could be placed under "About the role"? Might be okay but it's about company. However we could also create a section "About Praxent" but not in allowed list. 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? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. So we should map content to those headings. Thus: - About the role: could include mission, what you will own, how we work (description of role). Might be long but okay. - Responsibilities: maybe "What you will own" details responsibilities. - Requirements/Qualifications/Skills: "What you bring" includes experience, fluency, track record, ability, experience in banking etc. Could split into Requirements (years experience, shipping production software), Qualifications (LLM/agentic experience), Skills (Python/TS, cloud, containers, CI/CD). But we need to avoid thin sections. Perhaps combine into one "Requirements" section with bullet list. - Benefits: "What you’ll love about us" includes PTO, holidays, wellness days, parental leave, medical/dental/vision/disability/accident, wellness program, IRA match, recognition, culture. Also mention being Anthropic partner, Microsoft partner, 26 years of runway. Those are benefits/perks. - Pay: salary range $156,000-$186,000 + benefits. - Schedule: not mentioned, so omit. We must not repeat job title as heading. Not needed. We must remove boilerplate like remote work locations list? That is substantive: location eligibility. Should we include? It's about remote work eligibility. Could be part of "About the role" or maybe a separate section? Not in list. Could include under About the role as a paragraph. Also must include work authorization requirement. We must preserve all substantive information. So we need to include location list, work authorization, remote definition, etc. We need to decide where to put them. Perhaps under About the role as a paragraph after mission. Let's craft HTML:

  About the role

  ... includes mission, what you will own, how we work, remote eligibility, work authorization.

  Then maybe

  Responsibilities

  with
  • items from "What you will own". Then

    Requirements

    with
    • items from "What you bring". Then

      Benefits

      with
      • items from "What you’ll love about us". Then

        Pay

        with

        salary range. We must not create Schedule. Check for filler: ensure each section has real content. Now extract specifics: Mission paragraph: "As a Forward Deployed Engineer, you embed directly with a Praxent client (a bank, lender, or payments company) and build the AI systems that run inside their business. An Architect or Senior FDE sets the shape of the system. You own a workstream inside it and take it to production writing most of the code, making day-to-day calls, and getting your piece across the compliance line.. Not a prototype that impresses in a room, but a system that holds up after we hand it over." What you will own bullet points (actually paragraphs): - Shipped, dependable AI in the client's environment. Agentic and LLM-backed features that meet the client's functional and compliance requirements and keep working after handoff, not just in our staging. - A work stream, end to end. You take a piece of the engagement from understanding the client's problem through to a delivered, documented solution. - AI that fits their world. Clean integration with the systems you are actually given, including legacy cores, governed data, and their identity and infrastructure, rather than a greenfield ideal. - Systems the client can run without you. The evals, guardrails, runbooks, and handoffs that let their team operate and trust what you built. - Earned trust on the ground. Client engineers who want you in the room because your communication is clear and your follow-through is reliable. How we work paragraph: "Praxent runs on a spirit of service that our clients feel from the first week. We lead with 'yes, and': we start from the client's goals and shape ourselves around how they actually work, instead of arriving with a fixed playbook. In financial services, that means treating constraints like compliance, risk reviews, legacy systems, and audit and explainability requirements not as obstacles to route around, but as the design problem itself. The strongest forward-deployed work embraces those constraints and is better for them. You will not do this alone. You work shoulder to shoulder with Praxent Senior Forward Deployed Engineers and Product Managers and the client's own people, and you own your part of the result from first commit to confident handoff." Remote eligibility: "These roles have been categorized as a Remote position. “Remote” employees do not have a permanent corporate office workplace and, instead, work from a physical location of their choice which must be identified to the Company. Employees may live in the following locations: Texas, Colorado, Florida, Georgia, Massachusetts, Maryland, Minnesota, Nebraska, New York, New Jersey, North Carolina, Oregon, Pennsylvania, Tennessee, South Carolina, Washington. Applicants for this position must be currently and legally authorized to work in the United States without the need for current or future sponsorship (e.g., H-1B, J-1, F-1, CPT, OPT, etc.). Praxent will not offer immigration sponsorship or assume sponsorship of an employment visa for this position. International relocation or remote work arrangements outside of the U.S. will not be considered." What you bring bullet points (actually paragraphs): - 3+ years shipping production software that other people depended on. - Direct experience with LLM and agentic systems (RAG, agent frameworks, vector stores, evals) is ideal, though strong product engineers who have recently gone deep on AI are very much in scope. - Fluency in Python and/or TypeScript, and comfort across the stack and a major cloud (AWS, Azure, or GCP), containers, and CI/CD. - A track record of integrating with messy, real-world systems and data, not just building from scratch. - You are working within decisions someone else has made. - The ability to hold a technical conversation with a client’s engineers and work directly with them. - Experience in banking, lending, or payments is strongly preferred, including working directly with risk and compliance partners and getting AI through model-risk or security review in a regulated organization. How you work: CAN/DO values paragraph: "Care deeply. You treat the client's users, data, and constraints as if they were your own.Always deliver. You do what you said you would, and people can count on your follow-through.Never settle. You keep raising the quality bar even when 'good enough' would pass review.Do it together. You build trust with the client's team and your Praxent peers, and you look for win-win.Own the outcome. You take responsibility for results, not just tasks, and you are the first to step toward what is broken." What you’ll love about us paragraph: includes many items: - A seat at the frontier, inside an industry that matters. Praxent is an Anthropic partner and a Microsoft partner. That means partner-level enablement and direct lines into both ecosystems — applied to banks, lenders, and insurers where the work is hard and the stakes are real. - Twenty-six years of runway. A reputation in financial services that took decades to earn. Do frontier work on solid ground. - Real time off. 15 days PTO to start and growing every year, 9 US holidays, 5 wellness days, paid parental leave. - The standard stuff, done right. Medical, dental, vision, disability, accident, a wellness program, and an IRA with up to 3% match. - A culture people vouch for. Recognized by Texas Monthly, Clutch, and Comparably. Doors are open, ideas travel upward, and nobody here says "it's just business." Pay: "The US base salary for this full-time position is targeted to be $156,000-$186,000 + benefits. Our ranges are determined by role, level, and location. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training." We need to preserve all substantive info. So include that paragraph. Now format. We'll produce:

        About the role

        Mission paragraph + How we work paragraph + Remote eligibility paragraph + Work authorization paragraph.

        But we need to ensure we don't duplicate content. We'll combine. Let's craft About the role paragraph: Combine mission, how we work, remote eligibility, work authorization. Mission: "As a Forward Deployed Engineer, you embed directly with a Praxent client (a bank, lender, or payments company) and build the AI systems that run inside their business. An Architect or Senior FDE sets the shape of the system. You own a workstream inside it and take it to production writing most of the code, making day-to-day calls, and