MuleSoft Developer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: About Us (company description), Scope of Work (description of tasks), Mandatory Experience (requirements/qualifications), Salary info (Pay). Also maybe Benefits? Not mentioned. Schedule? Not mentioned (just full-time remote). Could include Schedule as full-time remote? But we should only include if posting actually states them. It says "Full-time employee - Remote". That's schedule info: full-time, remote. Could be considered Schedule. But we need to see if we should create Schedule section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state full-time remote, so we can include Schedule. Pay is stated: Salary: $130,000 - $140,000. Benefits not stated explicitly (they mention "We offer the salary and benefits of the bigger companies" but not specific benefits; that's vague. Probably not specific enough to create Benefits section. So we omit Benefits. We need headings: About the role? Could use About Us as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content: About the role could be the "About Us" and scope? Actually About the role likely describes the role. We have Scope of Work describing responsibilities. Could treat that as Responsibilities. About the role could be a brief summary: "Capio Group is looking for an experienced MuleSoft Developer..." Might be okay. But we must not repeat job title as heading. We'll create sections: About the role (short paragraph), Responsibilities (list of duties from Scope of Work and task list), Requirements (maybe combine Mandatory Experience and qualifications), Qualifications (maybe education), Skills (list of technologies). However we must avoid thin sections. Better to combine: Responsibilities (detailed list), Requirements (mandatory experience + education + experience), Skills (list of technologies). Pay and Schedule sections. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting. That's a lot. We need to embed them in

or

• . Must not lose any detail. We need to be careful not to duplicate lines. We'll extract unique content. Let's parse posting: - Capio Group is looking for an experienced MuleSoft Developer! Full-time employee - Remote Salary: $130,000 - $140,000 - About Us: Capio Group is a California-based Information Technology Consulting firm serving the public sector since 2010. We assist the Government in delivering large, complex systems and solutions. Capio Group is a small, but quickly growing firm that mixes good ideas, with great people, to achieve extraordinary results for our clients. We offer the salary and benefits of the bigger companies, with the added bonus of a flexible workplace and a great work-life balance. - Scope of Work: Capio Group is looking for an experienced MuleSoft Developer to work as part of a team on assisting with modernizing the client legacy systems by migrating to Salesforce and supporting integration efforts between legacy platforms and new technologies. The scope includes, but is not limited to, control cashier inventory management, vehicle registration, and integration to various legacy mainframe and Java applications within the enterprise. The MuleSoft Developer will help architect the solution, develop a detailed plan, and execute the transition to or with Salesforce. Additionally, will help with integrating legacy systems, including those built on Java, z/OS Connect, IBM Host Access Transformation Services (HATS), and other applicable technologies, ensuring seamless data flow and operational continuity. The MuleSoft Developer shall be able to provide expertise in client legacy systems and business processes, and Salesforce, and architectural design in support of the department’s modernization efforts. efforts. Support may be required in but is not limited to: IBM Host Access Transformation Services (HATS), Java, JavaScript, html, CSS, EDX/EDL integration with Modern C, Bash/Ksh, and J2EE, GitHub, Gitlab, Liberty/WebSphere applications, AIX, Red Hat Enterprise Linux, IBM Integration Bus (IIB), HP Exstream/OpenText, COBOL, DB2, VSAM, CICS, Endevor, Salesforce, MuleSoft, Copado, Talend, Red Hat Decision Manager, and mainframe support. Services requested may include, but are not limited to, business and technical analysis, project business and technical documentation, architectural and data plans, project management, code and report development and implementation, testing, conversion, training, and knowledge/skills transfer. - The MuleSoft Developer will be responsible for tasks including but not limited to: (then a huge list of tasks grouped under categories: Solution Specifications Development, Solution Development and System Testing, Perform Project Management, Analysis, Release Management and Deployment, Knowledge Transfer, Post-Implementation Support, Maintenance and Operations (M&O)) We need to preserve all those tasks. Then Mandatory Experience: list of requirements. We need to output HTML with sections. Let's decide sections: - About the role: maybe a brief paragraph summarizing role and company? Could combine About Us and maybe first sentence. But we must not lose info. Could put About Us content under About the role? But About Us is about company, not role. However instruction says use headings e.g. About the role, Responsibilities, etc. It's okay to put company description under About the role? Might be okay but could be considered not exactly role. However we need to preserve all substantive info; we can put About Us content under About the role heading. It's not ideal but acceptable. Alternatively we could omit About the role and just have Responsibilities, Requirements, Skills, Pay, Schedule. But we need to include company info somewhere; maybe we can put it in a

  before any heading? The instruction says output only HTML fragment, no restrictions on having a leading paragraph before headings. It didn't forbid. So we could start with a

  containing About Us, then headings for Responsibilities, Requirements, Skills, Pay, Schedule. That would preserve all info without misusing headings. But they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use those headings, just that if we use headings they should be those. We can have a leading paragraph without heading. That seems okay. Thus:

  About Us: Capio Group is a California-based Information Technology Consulting firm serving the public sector since 2010. We assist the Government in delivering large, complex systems and solutions. Capio Group is a small, but quickly growing firm that mixes good ideas, with great people, to achieve extraordinary results for our clients. We offer the salary and benefits of the bigger companies, with the added bonus of a flexible workplace and a great work-life balance.

  Then

  Responsibilities

  with
  • ... all tasks. But we need to include also the Scope of Work description (which is part of responsibilities). Could incorporate that as part of responsibilities list or as a preceding paragraph. Probably better to include Scope of Work as part of responsibilities description (maybe a

    then list). We'll include a

    summarizing scope then list of specific tasks. We must preserve all tasks exactly as written. The tasks list is long with many sub-items. We'll need to replicate them as list items. We must be careful not to miss any. Let's extract the tasks list from posting: "The MuleSoft Developer will be responsible for tasks including but not limited to:" Then bullet-like sections: Solution Specifications Development - Develop detailed solution specifications and recommendations - Document all business rules relating to requirements - Develop integrations with other systems - Develop conceptual designs - Develop data models - Gather and document requirements for business process realignment - Create Application Developer and Administrator Support Guides - Create System Design Documents Solution Development and System Testing - Develop and implement a new solution, as well as new code for the integration of applications - Modify existing code and documentation - Transition of code through various application environments, including documentation - Deliver defect fix, including documentation - Write automated tests to validate code functionality and coverage - Complete development of system enhancements - Complete unit testing and document results in a Unit Testing Report - Run automated test scripts for mission critical and high-volume transactions and complete system integration testing (SIT) and document results in a SIT Report - Provide defect fixes and resolutions for end-to-end (E2E) testing and document the results in an E2E Testing Report - Provide defect remediation for other relevant test cycles - Complete user reports analysis, development, and/or conversion Perform Project Management - Assess and update Master Project Management Plan - Perform Risk Management activities. - Perform Schedule Management activities - Perform Communication Management activities - Manage Work Breakdown Structure (WBS) - Perform Cost Management activities - Create Project Reports - Enforce Change Control Processes - Perform Project Plan and Process Quality Assurance activities - Perform Project Management team activities, facilitate team communication, track progress and maintain project plan documentation Analysis - Review the As-Is architecture, analyze legacy systems, and deliver solutions for platform-based architecture - Gather and document requirements and identify gaps. - Analyze current processes and deliver solutions for business process realignment - Analyze reports and provide architectural framework enhancements and defect fixes for data conversion efforts Release Management and Deployment - Create a Continuous Integration / Continuous Deployment pipeline - Create and manage release management processes. - Build and align organization’s release calendar with external and internal customers - Prioritize and plan release build activities for critical defect fixes and product enhancements and publish production incident, release and resolution reports Knowledge Transfer - Conduct knowledge sharing/mentoring sessions, walkthroughs including documentation - Develop training materials. - Provide post-go-live defect triage and system monitoring activities - Document critical information, responsibilities and workflows into a Knowledge Transfer Report - Submit monthly Knowledge Transfer Reports summarizing activities completed for the period - Provide/perform functional and technical mentoring sessions to maintain the application software - Develop, and maintain system documentation for technical and non-technical staff to maintain and operate the application software Post-Implementation Support - Perform technical lead post-implementation support for production issues and resolution - Deliver documentation for production and maintenance operations issues resolution and support. - Perform technical delivery on enhancements to address degradation of system or application - Monitor the system applications through the hypercare phase Maintenance and Operations (M&O) - Create the M&O Plan – showing the processes, methodologies, and tasks to maintain and operate the Solution - Create the Transition Exit and Interaction Plan - the approach to ensuring engagement transfer to the client. - Create Technical Guide - Create a glossary, definition of each module, and data dictionary - Setup monitoring, automation, or reporting We need to preserve all that. Now Requirements / Qualifications / Skills. Mandatory Experience section: "Mandatory Experience: Within the last ten (10) years, must have a minimum of five (5) years of experience in electronic data processing systems study, design, and programmingWithin the last ten (10) years, at least three (3) years of experience in electronic data processing systems study, design, and programming must be in a lead CapacityMust possess a bachelor’s degree in an IT-related or Engineering field. Additional qualifying experience may be substituted for the required education on a year-for-year basis. A copy of the degree must be provided upon requestA minimum of two (2) years of MuleSoft system development, and testing experience in the last ten (10) years on projects involving system customization with a contract value of at least $250,000 A minimum of two (2) years of experience in the last ten (10) years