Information Systems Architect

We need to output HTML fragment with sections: About the role? The posting includes description after "Responsibilities". There's no explicit "About the role" heading but we can treat the introductory paragraph as maybe "About the role". The instructions: 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 — fold minor metadata into a short

  or drop it. 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 include sections only if there is real content. Let's parse the posting: - Intro: "Red Cedar TG is seeking a dynamic, proactive, and self-starting Information Systems Architect to join our team. Missing a certification for this position? Red Cedar TG will work with candidates that are otherwise fully qualified to help them obtain required certifications such as CompTIA Sec+, ITIL, CISSP, and other required certifications." This is about the role and certification assistance. - Then: "The salary range for this position is $60,000-$85,000 annually and is dependent on geographical location, qualifications, and experience." This is Pay info. - Then heading "Responsibilities" followed by paragraphs. - Then heading "Requirements" followed by bullet-like lines: "BA/BS degree in an IT or related discipline", "3-5 years of experience; may substitute work experience", "Ability to obtain a US government Secret clearance", "Strong analytical and problem-solving skills", "Ability to work individually as well as with cross functional teams", "Excellent oral and written communication skills". These are requirements. - Then "Desired Experience with ..." lines: these could be considered "Desired Experience" or "Qualifications" or "Skills". The instructions list possible headings: Qualifications, Skills. We could combine desired experience under "Qualifications" or "Skills". Since they are desired experience, maybe "Qualifications". We'll treat them as qualifications. - Then "About Red Cedar TG" paragraph about company. - Then benefits: "We offer a comprehensive compensation and benefits package including: Generous PTO Package, 11 Paid Holidays, Health Benefits Effective Immediately, 401K and Immediate Company Matching, Education Assistance, Paid Parental Leave". That's Benefits. - Then EEO statement etc which we should remove. - Also "Powered by JazzHR dLllNR3CN3" is boilerplate, remove. We need to avoid repeating job title as heading. So we will not have an

  for "Information Systems Architect". We'll have sections: About the role (maybe combine intro and certification assistance), Responsibilities, Requirements, Qualifications (desired experience), Benefits, Pay (salary range). Schedule not present, so omit. We need to ensure we don't create sections with filler. All have content. We need to use

  for each section heading. Use

  • for any list of duties/requirements/benefits. For prose, use

    . We need to preserve all substantive information. Let's extract. About the role: The first paragraph plus certification assistance sentence. Could be two sentences. We'll put in

    . Responsibilities: The block after "Responsibilities". It's multiple paragraphs. We could convert each sentence into

    or combine into

    . But we need to use

    • for any list of duties/requirements/benefits. Responsibilities are not explicitly a list but could be considered duties. The instruction: "Use
      • for any list of duties/requirements/benefits". So if we treat responsibilities as a list of duties, we should use
        • . However the responsibilities paragraph is prose describing duties. Could we split into bullet points? The instruction says to use list for any list of duties. If we don't have explicit bullet list, we could still use

          for prose. But to be safe, we could treat as

          because it's not a list. The instruction says "Use

          • for any list of duties/requirements/benefits". If it's not a list, we can use

            . So we will keep responsibilities as

            (maybe multiple

            ). Requirements: The bullet-like lines after "Requirements". Those are a list. So we should use

            • . Qualifications: The desired experience lines after "Desired Experience with ...". Those are also a list. Use
              • . Benefits: The list after "We offer a comprehensive compensation and benefits package including:" includes items separated by commas. Could be a list. Use
                • . Pay: The salary range sentence. Use

                  . We must not include any boilerplate like EEO, etc. Now produce HTML fragment. Let's craft:

                  About the role

                  Red Cedar TG is seeking a dynamic, proactive, and self-starting Information Systems Architect to join our team. Missing a certification for this position? Red Cedar TG will work with candidates that are otherwise fully qualified to help them obtain required certifications such as CompTIA Sec+, ITIL, CISSP, and other required certifications.

                  Responsibilities

                  We're looking for a Information Systems Architect who can see the big picture of our technology landscape and turn that vision into reality. In this role, you'll shape how our application systems and IT infrastructure are designed, built, and evolved — serving as the architectural backbone for everything from new development efforts to long-term system enhancements. You'll partner closely with users and business stakeholders to truly understand what they need, then translate those requirements into high-quality technical solutions that actually deliver. This isn't a role where you work in isolation — you'll collaborate hand-in-hand with our developers and engineers, helping build application roadmaps, aligning development plans, and making sure every piece of our information systems and infrastructure fits together seamlessly. Technology doesn't stand still, and neither will you. You'll keep a close eye on emerging trends and technological advancements, using that knowledge to continuously improve our solutions and keep them aligned with both industry best practices and where our business is headed. Because our systems, applications, and services are deeply interconnected, you'll need a sharp understanding of how changes ripple across the environment — evaluating the impact of any change or addition before it happens, not after. You'll also be hands-on when it comes to quality: analyzing systems, running usability testing, and validating performance and reliability. Whether it's improving scalability or strengthening security, you'll make sure our architecture doesn't just work today, but is built to grow and hold up under real-world demands. If you enjoy connecting the dots between technology and business strategy, thrive on solving complex integration challenges, and want your work to directly shape the future of our IT ecosystem, we'd love to hear from you.

                  Requirements

                  • BA/BS degree in an IT or related discipline
                  • 3-5 years of experience; may substitute work experience
                  • Ability to obtain a US government Secret clearance
                  • Strong analytical and problem-solving skills
                  • Ability to work individually as well as with cross functional teams
                  • Excellent oral and written communication skills

                  Qualifications

                  • Experience with Air Mobility Command (AMC), US Transportation Command (USTRANSCOM) or Army Transportation Command (ARTRANS) business, C2, or IT systems
                  • Exposure to IT systems requirements, analysis, and engineering
                  • Experience with Microsoft Office and Visio
                  • Exposure to enterprise architecture frameworks such as DoD Architecture Framework (DoDAF), Federal Enterprise Architecture Framework (FEAF), or The Open Group Architecture Framework (TOGAF)
                  • Exposure to Business Process Modeling Notation, flow charting, or other process mapping approaches

                  Benefits

                  • Generous PTO Package
                  • 11 Paid Holidays
                  • Health Benefits Effective Immediately
                  • 401K and Immediate Company Matching
                  • Education Assistance
                  • Paid Parental Leave

                  Pay

                  The salary range for this position is $60,000-$85,000 annually and is dependent on geographical location, qualifications, and experience.

                  We should not include About Red Cedar TG section? The instructions list possible headings but not required. Could we include "About the company"? Not in list. The list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add a section for About Red Cedar TG unless we map it to something like "About the role"? But we already have About the role. The company description is not required but could be considered part of "About the role"? Might be extra. The instruction: "Prefer a few substantive sections over many thin ones." Including company description may be extra but still substantive. However the allowed headings list does not include "About the company". We could omit it to keep to allowed headings. The instruction says use

                  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. But to be safe, we could include a section like "About Red Cedar TG" but that's not in the examples. Might be okay but risk. Better to omit company description to stay within guidance. However we must preserve ALL substantive information. If we omit company description, we lose substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include it somewhere. Could we incorporate it into "About the role" paragraph? That would be mixing role description with company info, but still preserving. Could add a paragraph after About the role about the company. That would still be under About the role heading? Might be okay. But the heading "About the role" might be misleading if we add company info. However we could rename heading to "About the role & company"? Not in list. Perhaps we can add a separate section "About Red Cedar TG" even if not in examples; the instruction says e.g., not exclusive. So it's permissible. Let's include it. Thus add:

                  About Red Cedar TG

                  Headquartered in New Braunfels, TX, Red Cedar TG is focused on delivering enterprise application architecture, project management, and telecommunications solutions to federal, state, local government, and commercial clients. We deliver information technology support, solutions, engineering, architectures, telecom cloud solutions, and engineering and consulting services to Federal Government and commercial clients. We also specialize in fiber optic solutions, Cat-6 network cabling, and all other low voltage cabling solutions. Red Cedar TG is owned by the Modoc Nation of Miami, Oklahoma, a federally recognized Native American Tribe, and is a registered SBA Small Disadvantaged Business and certified 8(a) company. At Red Cedar TG, we know employee well-being is important. That’s why we’re committed to making resources available to you that will enable you to become happier, healthier, and more productive in all areas of your life. We offer a