Jobs · Engineering · New York

Senior Solutions Architect, Partner Business (Channel & Managed Services)

Everlaw · New York, NY · 1 mo ago
HybridEngineering$172k/yrFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate. We need to parse the posting. Content: "The Role" paragraph: "You'll build, grow, and scale partner practices across our channel and managed service provider (MSP) network, serving as the technical and product expert across the full partner lifecycle. Instead of focusing solely on individual deals, you will enable entire partner organizations, coaching their technical practitioners and delivery teams to independently deliver solutions on Everlaw's platform." Then "This is a full-time, exempt position based in our Oakland, CA, New York City, or Washington, D.C. office with a hybrid work schedule: in office M/W/Th with the option to work from home on Tu/Fr." Then "What you'll do" list: bullet points. Then "About You" list: bullet points. Then "The Team: Solutions Architect" paragraph. Then "Total Rewards & Benefits": salary info, then sections: Health & well-being, Financial rewards, Growth & everyday perks. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: likely the introductory paragraph about role (first paragraph). Could also include "This is a full-time, exempt position ..."? That's more schedule/location. Might go under Schedule? Actually schedule is hybrid work schedule. Location maybe part of About the role? But we have separate Schedule heading for schedule details. Location could be part of About the role or maybe omitted if not covered. The instruction: include a section only when posting has real specific content for it. So we need to decide. We have location: Oakland, CA, New York City, or Washington, D.C. office. That's location info. Not covered by any heading except maybe About the role. Could include in About the role. Responsibilities: the "What you'll do" bullet list. Requirements: maybe the "About You" bullet list? But that includes experience, skills, etc. Could split into Requirements (experience) and Qualifications (education? none) and Skills (technical acumen). However we have headings: Requirements, Qualifications, Skills. We need to use them if content exists. We have "About You" bullet list: - You have 3+ years of experience in a sales engineering, solutions architecture, or technical consulting role, with roughly 8+ years of total technology experience and deep hands-on expertise with legal technology platforms. - You bring a proven track record of working with managed service providers or legal industry delivery teams, with the ability to coach and enable other technical practitioners. - You have strong technical acumen and a solid command of litigation technology processes, data processing, analytics, and platform integrations. - You are an excellent communicator and presenter who can influence both delivery engineers and partner executives. - You are organized and process-oriented, comfortable managing long partnership cycles, concurrent enablement workstreams, and up to 25% travel. - You are authorized to work in the United States. Please note that at this time, Everlaw is not sponsoring U.S. employment visas for this role. - Think you're missing some of the skills and are hesitant to apply? We do not believe in the 'perfect' candidate and encourage you to apply if you feel you can bring value to our team. We often revisit candidates who may have applied for a different role if something comes up that's a better fit. We need to preserve all substantive info. So we need to include these bullet points under appropriate headings. We could treat "Requirements" as the experience and eligibility (3+ years, 8+ years, authorized to work, no visa sponsorship). "Qualifications" maybe the proven track record, ability to coach, etc. "Skills" could be technical acumen, communication, organized, etc. But we need to avoid duplication. Let's parse: - Experience: 3+ years in sales engineering/solutions architecture/technical consulting, 8+ years total tech experience, deep hands-on expertise with legal technology platforms. -> Requirements. - Proven track record working with MSPs or legal industry delivery teams, ability to coach/enable other technical practitioners. -> Could be Requirements or Qualifications. Might fit Qualifications. - Strong technical acumen and solid command of litigation technology processes, data processing, analytics, platform integrations. -> Skills. - Excellent communicator and presenter who can influence both delivery engineers and partner executives. -> Skills. - Organized and process-oriented, comfortable managing long partnership cycles, concurrent enablement workstreams, up to 25% travel. -> Skills (or maybe Requirements? but it's more skill/trait). - Authorized to work in US, no visa sponsorship. -> Requirements (eligibility). - Encouragement to apply even if missing some skills: that's more a note, could be placed under About You but not a heading. Could be placed under Requirements as a note? Might be considered boilerplate? It's substantive but not a requirement. Could be placed under About You but we don't have that heading. Could be placed under Requirements as a note. But we must not invent headings. We could put it under Requirements as a
  • maybe. But we need to avoid filler like "commensurate with experience". This note is not filler. Now "The Team: Solutions Architect" paragraph: describes team. Could go under About the role? Or maybe a separate section like "About the Team". Not in allowed headings. Could be omitted? But we must preserve ALL substantive information. So we need to include it somewhere. Perhaps under About the role as additional paragraph. Now "Total Rewards & Benefits": includes salary, OTE, then sub-sections: Health & well-being, Financial rewards, Growth & everyday perks. We need to map to headings: Pay, Benefits, Schedule. Pay: salary and OTE. Benefits: health & well-being, financial rewards, growth & everyday perks. Schedule: hybrid work schedule: in office M/W/Th with option to work from home Tu/Fr. Also location? Could be location under About the role. Thus we will have sections: - About the role (intro paragraph + location + team description) - Responsibilities (What you'll do bullet list) - Requirements (experience, eligibility, maybe note about applying) - Qualifications (proven track record, ability to coach) - Skills (technical acumen, communication, organized) - Pay (base salary, OTE) - Benefits (health & well-being, financial rewards, growth & everyday perks) - Schedule (hybrid schedule) We must not create sections with filler. Ensure each has content. Now we need to format using

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

      for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft. First, About the role: Paragraph: "You'll build, grow, and scale partner practices across our channel and managed service provider (MSP) network, serving as the technical and product expert across the full partner lifecycle. Instead of focusing solely on individual deals, you will enable entire partner organizations, coaching their technical practitioners and delivery teams to independently deliver solutions on Everlaw's platform." Then location: "This is a full-time, exempt position based in our Oakland, CA, New York City, or Washington, D.C. office." Then team description: "The Solutions Architect team brings together product, technical, and ediscovery expertise to show customers how Everlaw can address their most important challenges. Through discovery, tailored demonstrations, technical deep dives, evaluations, and solution design, the team translates complex legal workflows into a clear vision of what better work can look like. This work gives customers confidence in Everlaw while bringing field insights back into the company's product and strategy." We could combine into one or multiple

      tags. Now Responsibilities: bullet list from "What you'll do": - Serve as the technical expert across the partner lifecycle, evaluating prospective partners' delivery capabilities and translating complex workflow requirements into platform-native solutions. - Build onboarding programs, technical playbooks, certification paths, and demonstration enablement materials that accelerate partner ramp-up and independence. - Deliver polished demonstrations and technical deep dives (including generative AI capabilities and API integration architectures) to technical and executive stakeholders. - Partner with Business Development and direct sales teams on strategic joint opportunities, RFP responses, and co-sell pursuits. - Act as an escalation point and technical mentor for partner-side solutions architects, consulting on how Everlaw fits into broader legal technology stacks. - Gather field insights from partner engagements to collaborate with product and engineering teams on platform features and API surface expansion. Now Requirements: bullet list: - 3+ years of experience in a sales engineering, solutions architecture, or technical consulting role, with roughly 8+ years of total technology experience and deep hands-on expertise with legal technology platforms. - Authorized to work in the United States. (Note: Everlaw is not sponsoring U.S. employment visas for this role.) - Encouragement to apply even if you feel you may be missing some skills; we do not believe in the 'perfect' candidate and encourage you to apply if you feel you can bring value to our team. We often revisit candidates who may have applied for a different role if something comes up that's a better fit. We could combine the last two as separate

    • . Now Qualifications: bullet list: - Proven track record of working with managed service providers or legal industry delivery teams, with the ability to coach and enable other technical practitioners. Maybe also include "You bring a proven track record..." That's it. Now Skills: bullet list: - Strong technical acumen and a solid command of litigation technology processes, data processing, analytics, and platform integrations. - Excellent communicator and presenter who can influence both delivery engineers and partner executives. - Organized and process-oriented, comfortable managing long partnership cycles, concurrent enablement workstreams, and up to 25% travel. Now Pay: paragraph: "The annual base salary for this position is $172,000, with a total On-Target Earnings (OTE) of $246,000. Eligibility for the commission portion is performance-based and subject to the achievement of specific performance metrics, which are governed by Everlaw's policies and incentive plans. The final offered salary will be dependent upon many factors including the candidate’s experience and skills. The role's compensation is subject to change in the future." Now Benefits: we need to list health & well-being, financial rewards, growth & everyday perks as sub-items maybe under a
        with each benefit category as
      • containing a
          of specifics? The instruction: Use
          • for any list of duties/requirements/benefits. So we can treat each benefit category as a list item, and inside we can have
              for details? Might be okay but could be nested lists. Simpler: make a
                where each
              • contains a heading? But we cannot add extra headings inside? Not prohibited. But we could just list each benefit as a
              • with the details as text. Thus Benefits section:
                • Health & well-being: Comprehensive medical, dental, and vision coverage; Flexible Spending Accounts for health and dependent care expenses; Membership to Modern Health to support mental health and wellness; Paid parental leave; Company-sponsored life and disability insurance.
                • Financial rewards: Competitive equity grants, so you share in Everlaw's long-term growth; 401(k) plan with company matching of up to 4% of eligible annual compensation.
                • Growth & everyday perks: 17 paid vacation days, 11 federal holidays, and paid sick leave; Four "Everlawlidays" (additional paid company-wide days off) per year; Annual allocation for learning & development and relevant professional membership dues; Hybrid work with regular work-from-home days and flexibility

  • Similar jobs