Technical Alignment Engineer for Managed Service Provider

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You'll Do), Requirements, Benefits, maybe Pay? The posting includes Benefits and mentions Competitive Pay but not specific amount. The instruction: include a section ONLY when 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. Benefits: they list Competitive Pay, Company subsidized medical, dental and vision insurance, PTO, Paid parental leave, Company Retirement Plan, Subsidized Gym Membership. That's specific enough. Pay: they say Competitive Pay but no specific number; that is vague but still "Competitive Pay" is a statement. Is that considered specific content? It says "Competitive Pay" which is not a number but still a statement. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive Pay". So we can include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits? But they are separate headings in the list. We could include Benefits section that includes the bullet list, and maybe include Pay as a bullet within Benefits? But they said use headings for Benefits, Pay, Schedule. If we include Pay heading with just "Competitive Pay" that's thin but still substantive? Might be considered thin. Better to incorporate Pay into Benefits as a bullet? But the instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So they expect separate headings if content exists. Since they gave Competitive Pay, we can include Pay section with that line. It's not filler like "commensurate with experience". It's a statement. So include. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate. We need to preserve all substantive information. So we need to capture About the role paragraph, Responsibilities (What You'll Do) broken into subparts: Technical Alignment & Client Audits, New Client Onboarding, Collaboration with Internal Teams, Documentation & Standards. Could combine under Responsibilities with

• each duty. But we have multiple sub-sections; we could keep them as
  • items. Requirements: list of bullet points. Experience That Would Be a Plus: could be under Requirements or separate Qualifications? The instruction includes Qualifications, Skills headings. We could treat "Experience That Would Be a Plus" as Qualifications or Skills. Probably better as Qualifications. We also have "What Success Looks Like" and "Work Environment & Travel". Those could be under Responsibilities or maybe a separate section like "Work Environment". The instruction says include a section only when posting has real specific content. We have content for Work Environment & Travel. Could make a section "Work Environment". But they didn't list that as example headings; they gave list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those headings. So we need to map content to those headings. About the role: we have that. Responsibilities: we have What You'll Do (including subparts). Requirements: we have Requirements bullet list. Qualifications: we have Experience That Would Be a Plus. Skills: maybe we could pull out skills from Requirements? But we already have Requirements covering skills. Could leave Skills empty? Better not to create empty heading. So we omit Skills if no specific content beyond what's already in Requirements. Benefits: we have Benefits list. Pay: we have Competitive Pay. Schedule: not mentioned; omit. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no markdown fences. Let's craft:

    About the role

    Straight Edge Technology is looking for a Technical Alignment Engineer to proactively assess, document, and improve our clients' technology environments. This is an independent, client-facing technical role that combines onsite field work with technical assessment, documentation, and planning. After completing training on Straight Edge Technology's standards, tools, and Technical Alignment process, you will be responsible for conducting scheduled onsite visits for assigned clients, evaluating their technology environments, documenting your findings, and identifying areas that require attention. You'll also play an important role in onboarding new clients by conducting technical discovery, documenting their environments, identifying risks and gaps, and helping prepare them for transition into ongoing managed services. You won't be expected to know everything. You will, however, be expected to know how to investigate, follow established standards, document what you find, recognize when something isn't right, and escalate appropriately when an issue requires additional expertise. Your findings help our teams understand the technical health of our clients, identify what needs attention, and determine the appropriate next steps.

    Responsibilities

    • Technical Alignment & Client Audits: Independently conduct scheduled onsite Technical Alignment visits for assigned clients; evaluate client technology environments against Straight Edge Technology's established standards and best practices; inspect network closets, server rooms, firewalls, switches, wireless equipment, UPS systems, workstations, and other technology assets; review Microsoft 365, servers, endpoints, backups, security solutions, networking, and other business-critical systems; verify that technical documentation accurately reflects the client's current environment; identify aging or unsupported technology, security concerns, configuration inconsistencies, documentation gaps, and other areas that do not meet established standards; document findings clearly and consistently; determine when findings require escalation, remediation, additional investigation, or project-based work; track previously identified findings and verify their status during future reviews; maintain a current understanding of assigned client environments; communicate significant technical or security concerns promptly to the appropriate internal resources.
    • New Client Onboarding: Conduct technical discovery and environmental assessments for assigned new client onboardings; develop an understanding of the client's networks, infrastructure, servers, endpoints, Microsoft 365 environment, backups, security solutions, vendors, and other business-critical technology; conduct onsite discovery of server rooms, network closets, infrastructure, workstations, and technology assets; identify technical risks, unsupported technology, security concerns, configuration issues, and documentation gaps; gather and organize the technical information necessary for Straight Edge Technology to support the new client; establish accurate technical documentation and a baseline of the client's environment; identify items requiring immediate attention and those that should be considered for future improvement; communicate findings to the appropriate internal teams; escalate issues requiring deeper engineering expertise or additional technical investigation; help ensure the client's technical environment is properly documented before transition into ongoing managed services.
    • Collaboration with Internal Teams: Share technical findings, risks, documentation, and recommendations with the appropriate internal teams; provide the technical context needed to help plan remediation, projects, and future technology improvements; communicate significant risks, lifecycle concerns, and opportunities identified within client environments; participate in internal or client discussions when additional technical context is needed; escalate findings that require deeper technical expertise or additional resources; follow up on identified items to help ensure they continue moving toward resolution.
    • Documentation & Standards: Maintain accurate technical documentation for assigned clients; update network diagrams, system information, asset information, configurations, vendors, warranties, and other required technical records; follow established Technical Alignment standards and processes; document findings accurately and consistently; ensure changes discovered during client visits are reflected in documentation; identify gaps between the documented environment and the actual environment; maintain organized records of findings and outstanding alignment items.

    Requirements

    • 2+ years of hands-on IT support, systems administration, network support, or similar technical experience
    • Working knowledge of Microsoft 365 and Windows environments
    • Working knowledge of business networking, including switches, firewalls, wireless networks, TCP/IP, and common network infrastructure
    • Familiarity with servers, endpoints, backups, and business technology environments
    • Understanding of cybersecurity fundamentals, including MFA, endpoint protection, patching, email security, and access management
    • Strong troubleshooting and problem-solving skills
    • Ability to independently work through an unfamiliar technical environment and gather the information you need
    • Ability to recognize when an issue requires escalation or additional expertise
    • Strong attention to detail and documentation skills
    • Ability to follow established technical standards and processes
    • Strong organizational and time-management skills
    • Comfortable working independently at client locations
    • Professional communication skills and the ability to interact directly with clients
    • Valid driver's license and ability to safely operate a company vehicle

    Qualifications

    • Previous MSP experience
    • Experience working onsite with business clients
    • Experience conducting IT assessments, audits, or technical discovery
    • Experience onboarding new client environments
    • Experience with Microsoft 365 administration
    • Familiarity with RMM, PSA, and IT documentation platforms
    • Experience with firewalls, switches, wireless infrastructure, servers, or backup systems
    • CompTIA, Microsoft, networking, security, or other relevant certifications
    • Previous Technical Alignment or TruMethods experience is not required. We will train you on our process and standards.

    Benefits

    • Competitive Pay
    • Company subsidized medical, dental and vision insurance
    • PTO
    • Paid parental leave
    • Company Retirement Plan
    • Subsidized Gym Membership
    We included Pay as a bullet inside Benefits? Actually we made Benefits list includes Competitive Pay as first bullet. But we also have a separate Pay heading? We omitted Pay heading to avoid duplication. The instruction: Use headings for Benefits, Pay, Schedule. If we put Competitive Pay inside Benefits, we are not creating a Pay section. That's okay because we still have the info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." We have Benefits section (yes). We don't have a separate Pay heading; we included Competitive Pay as a bullet under Benefits. That's acceptable. But we might want to separate Pay heading for clarity. However they said prefer few substantive sections over many thin ones. Having a Pay section with just "Competitive Pay" is thin. Better to keep it under Benefits. So we will not create a Pay heading. Thus final HTML includes About the role, Responsibilities, Requirements, Qualifications, Benefits. Check we didn't repeat job title. Good. We removed boilerplate like "What Success Looks Like", "Work Environment & Travel". Those are not included; but we might lose some substantive info. The instruction says preserve ALL substantive information. So we need to include that info somewhere. Where can we put it? Could be under Responsibilities or About the role? "What Success Looks Like" and "Work Environment & Travel" are substantive. We should incorporate them. Perhaps add a section "Work Environment" but not in allowed headings. However we could incorporate into Responsibilities or About the role as extra paragraphs. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections, but we could also use other headings if needed? The examples are given, but not explicitly forbidden to use others. However they say "include a section ONLY