.NET Cloud Architect
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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 decide which sections to include based on content. The posting includes: - Intro about CapTech (company description). Could be "About the role"? Actually "About the role" is generic; but we have description of role. Could use "About the role" heading and then paragraphs describing role. - Responsibilities: there is a list of specific responsibilities. - Qualifications: there is a list of qualifications. - Benefits: there is a list of benefits (CapFlex, Learning & Development, Modern Health, Carrot Fertility, Fringe, Employee Resource Groups, Philanthropic Partnerships, 401(k) Matching). Also mention "comprehensive benefits package". So we can include Benefits section. - Pay: not mentioned. So we should NOT include Pay section. - Schedule: not mentioned. So no Schedule. - Skills: maybe we could include Skills but qualifications already cover skills. The instruction says prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills? But we have Qualifications section already. Could also include Skills if distinct, but qualifications already list many skills. Might be redundant. Better to have Qualifications (which includes skills). Could also have Responsibilities and Qualifications and Benefits. Also maybe "About the role" for intro. We need to avoid duplication: The qualifications section repeats some lines (Extensive knowledge of the concepts and tools required for effective software development including: Integrated Development Environments, Continuous Integration, Operating Systems (specifically UNIX/Linux), Test-driven Development, SDLC Methodologies including Waterfall, Scrum, XP, Kanban, and SAFe.) appears twice. We should preserve all substantive information but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly forbid removing duplicate lines, but says remove duplicated lines. So we should deduplicate. Also need to remove boilerplate: EEO, equal opportunity, visa sponsorship, contact Laura Massa, etc. Also remove "Additional Information" heading? That's not a standard heading; we can incorporate its content into Benefits section. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Intro paragraph(s): "CapTech is an award-winning consulting firm that collaborates with clients to achieve what’s possible through the power of technology. At CapTech, we’re passionate about the work we do and the results we achieve for our clients. From the outset, our founders shared a collective passion to create a consultancy centered on strong relationships that would stand the test of time. Today we work alongside clients that include Fortune 100 companies, mid-sized enterprises, and government agencies, a list that spans across the country." Then job description: "Cloud Architects at CapTech are called upon to perform various responsibilities within CapTech’s Systems Integration practice area, usually in the context of a technology assessment, strategy formation, or a development project performed for a particular client. They often lead a team of developers and collaborate with experienced project managers, analysts, designers, and clients to architect and deliver vital internal and customer facing systems in partnership with a variety of Fortune 500 clients. Typically, CapTech Architects have a broad understanding of many tools, technologies, and products, with some specialization in a few areas. Over time these specialties may change due to industry transformation or a changing client profile, and as such, our architects have the opportunity to get hands-on experience with the latest technologies while working with passionate CapTechers solving complex problems across numerous industries." Then "Specific responsibilities for the Cloud Architect position include:" followed by a list (looks like a paragraph with sentences separated by spaces). Let's extract each responsibility as bullet. List: - Position yourself as a trusted advisor to CapTech clients. - Oversee and set the technical direction of client projects, collaborating directly with client staff to define and adhere to architectural standards. - Lead internal teams and act as a Service Offering liaison - Design, implement, integrate, and support Cloud solutions - Work closely with clients, subject matter experts and the CapTech team to understand requirements, establish priorities and project scope, and manage expectations and project delivery - Define the technical and solution architecture for phased software development - Provide hands-on technical direction to other developers to review code and resolve issues - Create documents that specify strategy, assessment, or design in a way that delivers obvious value to the client and is understandable by any stakeholder - Articulate architectural differences between solution methods and the challenges and approaches to integrating solutions built on different platforms, including a working knowledge of architectural frameworks that may be used by our clients. - Apply detailed knowledge of organizational procedures to make independent decisions and serve as a credible resource for the client’s senior management team - Collaborate with CapTech business development team members during sales efforts to demonstrate CapTech’s technical capabilities, create a vision for a solution that CapTech can build, and produce estimates and work plans Note: Some lines may have missing punctuation; we keep as is. Qualifications: "Specific qualifications for the Cloud Architect position include:" then list: - Bachelor's Degree in Computer Science, Information Technology, or equivalent degree and/or experience - Cloud architecture experience utilizing AWS, Azure, or GCP - Demonstrated software development experience over 7+ years with a broad range of development tools and technologies - Ability to think strategically and relate architectural decisions/recommendations to business needs and client culture. - Ability and desire to lead multiple technical project teams - Ability to compromise and build consensus on architectural issues - In-depth experience with some or all of these cloud concepts: Infrastructure as a Service, Serverless Architecture, Container Architecture, Platform as a Service, Storage, Infrastructure as Code, and Identity and Access Management. - Knowledge of the concepts and tools required for effective software development including: Integrated Development Environments, Continuous Integration, Operating Systems (specifically UNIX/Linux), Test-driven Development, SDLC Methodologies including Waterfall, Scrum, XP, Kanban, and SAFe. - Cloud Architecture Certifications recommended but not required. - Extensive knowledge of the concepts and tools required for effective software development including: Integrated Development Environments, Continuous Integration, Operating Systems (specifically UNIX/Linux), Test-driven Development, SDLC Methodologies including Waterfall, Scrum, XP, Kanban, and SAFe. (duplicate) We need to deduplicate: The last bullet duplicates the previous knowledge bullet. So we keep one. Also there is "Additional Information" section about benefits. Let's extract benefits: "Alongside our suite of traditional benefits encompassing generous PTO, health coverage, disability insurance, paid family leave and more, we’ve launched extended benefits to help meet our employees’ needs. CapFlex – Employee-first mentality that supports a hybrid workforce and empowers daily flexibility while servicing our clientsLearning & Development – Programs offering certification and tuition support, digital on-demand learning courses, mentorship, and skill development pathsModern Health –A mental health and well-being platform that provides 1:1 care, group support sessions, and self-serve resources to support employees and their families through life’s ups and downsCarrot Fertility –Inclusive fertility and family-forming coverage for all paths to parenthood – including adoption, surrogacy, fertility treatments, pregnancy, and more – and opportunities for employer-sponsored funds to help pay for careFringe –A company paid stipend program for personalized lifestyle benefits, allowing employees to choose benefits that matter most to them – ranging from vendors like Netflix, Spotify, and GrubHub to services like student loan repayment, travel, fitness, and moreEmployee Resource Groups – Employee-led committees that embrace and incorporate diversity and inclusion into our day-to-day operationsPhilanthropic Partnerships – Opportunities to engage in partnerships and pro-bono projects that support our communities. 401(k) Matching – Generous matching and no vesting period to help you continue to build financial wellness" We need to format as list items. Also note there is a run-on missing spaces after some dashes; we can keep as is but maybe add spaces for readability? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation might be considered altering? Safer to keep as is but we can add spaces where missing? The original text had missing spaces due to formatting. For example: "CapFlex – Employee-first mentality that supports a hybrid workforce and empowers daily flexibility while servicing our clientsLearning & Development – Programs offering certification and tuition support, digital on-demand learning courses, mentorship, and skill development paths". There's no space between "clientsLearning". That's likely a formatting error. Should we preserve exactly? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Adding a space could be considered inventing? But it's minor formatting; maybe we should keep as is. However, readability may suffer but it's okay. We also need to remove boilerplate: EEO, equal opportunity, visa sponsorship, contact Laura Massa, etc. Also remove "At this time, CapTech cannot transfer nor sponsor a work visa for this position. Applicants must be authorized to work directly for any employer in the United States without visa sponsorship." That's boilerplate (visa). Remove. Also remove "For more information about our Diversity, Inclusion and Belonging efforts, click HERE." Remove. Also remove "As part of this commitment, CapTech will ensure that persons with disabilities are provided reasonable accommodations. If reasonable accommodation is needed to participate in the job application or interview process, to perform essential job functions, and/or to receive other benefits and privileges of employment, please contact Laura Massa directly via email lmassa@captechconsulting.com." Remove. Now we need to decide sections. Potential sections: - About the role (intro + job description overview) - Responsibilities - Qualifications - Benefits We could also include "Skills" but qualifications already cover. We must not create Pay or Schedule sections. Now produce HTML:
About the role
CapTech is an award-winning consulting firm that collaborates with clients to achieve what’s possible through the power of technology. At CapTech, we’re passionate about the work we do and the results we achieve for our clients. From the outset, our founders shared a collective passion to create a consultancy centered on strong relationships that would stand the test of time. Today we work alongside clients that include Fortune 100 companies, mid-sized enterprises, and government agencies, a list that spans across the country.
Cloud Architects at CapTech are called upon to perform various responsibilities within CapTech’s Systems Integration practice area, usually in the context of a technology assessment, strategy formation, or a development project performed for a particular client. They often lead a team of developers and collaborate with experienced project managers, analysts, designers, and clients to architect and deliver vital internal and customer facing systems in partnership with a variety of Fortune 500 clients. Typically, CapTech Architects have a broad understanding of many tools, technologies, and products, with some specialization in a few areas. Over time these specialties may change due to industry transformation or a changing client profile, and as such, our architects have the opportunity to get hands-on experience with the latest technologies while working with passionate CapTechers solving complex problems across numerous industries.
Then responsibilities:Responsibilities
- Position yourself as a trusted advisor to CapTech clients