Applications Programmer 3

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as 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 extract substantive content: Job Summary, Minimum Qualifications, Preferred Qualifications, Key Responsibilities, Department Overview, POSITION INFORMATION (salary, schedule, location, benefits, etc.), Benefits description, Physical Demands, Mental Demands, Work Environment, Special Requirements (but these may be considered boilerplate? They are not EEO but maybe still considered "special requirements" like background check, mandated reporter, misconduct disclosure. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Special Requirements like background check, mandated reporter, misconduct disclosure might be considered legal boilerplate. Probably we should drop them. Also "Physical Demands", "Mental Demands", "Work Environment" might be considered boilerplate? Not sure. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical Demands etc are not those categories, but they might be considered generic boilerplate. However they contain specific info (e.g., Standing - Occasional Up to 3 Hours). Might be considered substantive? Usually they'd be considered boilerplate but they are specific to the job. The instruction didn't explicitly say to remove them. It only says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep Physical Demands, Mental Demands, Work Environment if they are not duplicated. However they are quite detailed; we could keep them under a section like "Working Conditions" but we don't have a heading for that. Allowed headings are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot create other headings. So we must fit content into those allowed headings. If we cannot fit, we may need to omit those sections if they don't fit. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but likely we should only use those headings. It also says "Prefer a few substantive sections over many thin ones." So we should combine info into these sections. We need to decide which sections to include: About the role (job summary), Responsibilities (key responsibilities), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe combine with requirements?), Benefits, Pay, Schedule. We have salary info: Salary or Pay Range: $3,101.60 - $5,628.00, Salary Frequency: Bi-Weekly. So we can create Pay section with that. Schedule: Shift (Work Schedule): Mon-Fri, 8 AM - 5 PM. Also "This position is 100% remote". So schedule section can include that. Benefits: There's a Benefits Outstanding benefits and perks are among the many rewards... then list of benefits. So we can create Benefits section with that list. Now we need to avoid duplication: Many lines duplicated in Minimum Qualifications and Preferred Qualifications. We need to preserve all substantive information but not duplicate lines. So we need to deduplicate. Let's extract Minimum Qualifications bullet list (though it's not formatted as bullets but lines). We'll parse. Minimum Qualifications - For full consideration, applicants are encouraged to upload license and/or certification if required of the position Bachelor of Science in Computer Science or equivalent experience and/or training 2+ years of experience using Angular 2+ years of experience using Java 8 and above 2+ years of experience using Spring 2+ years of experience using JPA 2+ years of experience using Maven Software development experience using Java, JavaScript, or similar web development programming language(s) Understands latest technology trends and has used at least some of the latest technologies Willing to provide a portfolio of work produced. Experience using design patterns and data structures Experience using Eclipse or similar IDE Advanced technical skills and understanding of a myriad of technology used in web application development Coding experience using Java and JavaScript, preferably using or familiar with Spring Boot and Angular. Ability to design, develop, implement, debug and test user interfaces. Experience using or familiarity with front-end API programming a plus. Must be able to work independently with little direction. Must be able to provide work estimates and deliver maintainable projects on schedule. Must possess excellent testing, debugging and problem solving skills. Strong oral and written communication skills. Expected to adapt to a dynamic and collaborative work environment and make independent decisions. Adequate technical skills and understanding of a myriad of technology used in web application development. Knowledge of the Software Development Life Cycle and respective roles. Experience developing applications at some level (desktop or web) Strong oral and written communication skills. (duplicate) Must be a good team player Ability to integrate new and existing applications Ability to re-factor existing applications or understand the practice of refactoring Preferred Qualifications list (with many duplicates): Experience working in a University environment with faculty clients is essential. Experience creating and maintaining support application development documentation. Experience with Spring Boot Experience using RxJS Experience with JUnit or others Experience with Cypress Experience with Docker Experience with Node.Js Experience with CSS Experience with SLF4J Experience with web containers such as Tomcat, Netty, Jetty, and Glassfish Experience using relational databases such as MySQL, MS SQL, Oracle Experience supporting legacy JEE applications (including JSF) Writing functional and detailed technical specifications for application code developed Proactively participate in research and evaluation of emerging application development tools and technology Experience creating and maintaining support application development documentation (duplicate) Experience with JUnit, TestNG or others Experience with Cypress. Experience with Docker. Experience with Node.Js. Experience with CSS. Experience with web containers such as Tomcat, JBoss, and Glassfish. Experience using relational databases such as MySQL, MS SQL. Writing functional and detailed technical specifications for application code developed. Ability to work in a team environment using Agile XP practices and principles. Ability to manage and prioritize project requirements. Ability to interact with non-technical business peers. Ability to translate user stories into technical requirements Ability to propose creative technical solutions in a team environment We need to deduplicate. Also Key Responsibilities: 85% - Web Application Programming 15% - Business Systems Analysis and System Design Department Overview: Academic Information Systems develops and delivers critical web applications and services for the schools of medicine and nursing. POSITION INFORMATION includes many metadata like Salary or Pay Range, Salary Frequency, Salary Grade, UC Job Title, UC Job Code, Number of Positions, Appointment Type, Percentage of Time, Shift (Work Schedule), Location, Union Representation, Benefits Eligible, This position is 100% remote. We need to fold minor metadata into a short

  or drop it. We should keep schedule and location and maybe benefits eligibility? But we have separate Benefits section. We can include location and maybe appointment type in a short paragraph under About the role or a separate meta paragraph. But we must not create headings for Job ID etc. So we can include a short

  with position info like "Appointment Type: Staff: Career; Percentage of Time: 100%; Location: UCDHAS Building (HSP165), Rancho Cordova; Union Representation: TX-Technical Professionals; Benefits Eligible: Yes; This position is 100% remote." That's minor metadata. We must not repeat job title as heading. The job title is "APPLICATIONS PROGR 3 TX". We should not use that as heading. Now we need to produce HTML fragment with sections. We need to decide which sections to include: About the role (job summary + department overview + maybe position info), Responsibilities (key responsibilities), Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (maybe we can combine with requirements? But we could have Skills section listing technical skills like Angular, Java, Spring, etc. However we already have those in Requirements. To avoid thin sections, we could merge Requirements and Skills into one "Requirements" section that includes both minimum qualifications and skills. But the instruction says we can use those headings; we can choose to include only those with real content. We could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's many sections but each substantive. We must avoid filler like "commensurate with experience". Not present. Now we need to format lists with

  • . For prose, use

    . We need to ensure we don't duplicate lines. Let's craft content. About the role: combine Job Summary and Department Overview. Job Summary: "This position reports directly to the Supervisor of Application Development and is considered entry/intermediate skill level. This position will have a primary responsibility of supporting smaller-scale enhancements of existing web applications or participating in projects for the creation of new web applications while adhering to defined coding standards and practices. The position will be expected to become familiar with the team’s current choice of technology." Department Overview: "Academic Information Systems develops and delivers critical web applications and services for the schools of medicine and nursing." We can also add a short paragraph with position metadata: "Appointment Type: Staff: Career; Percentage of Time: 100%; Location: UCDHAS Building (HSP165), Rancho Cordova; Union Representation: TX-Technical Professionals; Benefits Eligible: Yes; This position is 100% remote." We'll put that as a

    after the overview. Responsibilities: Key Responsibilities: "85% - Web Application Programming; 15% - Business Systems Analysis and System Design." Could be a list? It's just two items. We'll make

    • 85% - Web Application Programming
    • 15% - Business Systems Analysis and System Design
    . Requirements: Minimum Qualifications (deduplicated). We need to list each unique item. Let's deduplicate Minimum Qualifications list: - Bachelor of Science in Computer Science or equivalent experience and/or training - 2+ years of experience using Angular - 2+ years of experience using Java 8 and above - 2+ years of experience using Spring - 2+ years of experience using JPA - 2+ years of experience using Maven - Software development experience using Java, JavaScript, or similar web development programming language(s) - Understands latest technology trends and has used at least some of the latest technologies - Willing to provide a portfolio of work produced. - Experience using design patterns and data structures - Experience using Eclipse or similar IDE - Advanced technical skills and understanding of a myriad of technology used in web application development - Coding experience using Java and JavaScript, preferably using or familiar with Spring Boot and Angular. - Ability to design, develop, implement, debug and test user interfaces. - Experience using or familiarity with front-end API programming a plus. - Must be able to work independently with little direction. - Must be able to provide work estimates and deliver maintainable projects on