Applications Programmer 3
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We have 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."
That's about the role. So we can have About the role
with
containing that. Responsibilities: There's a "Key Responsibilities" section: "85% - Web Application Programming 15% - Business Systems Analysis and System Design". That's specific. So we can have
Responsibilities
with- ... maybe each bullet? Could be two items: "Web Application Programming (85%)" and "Business Systems Analysis and System Design (15%)". We'll put as list.
Requirements: There's Minimum Qualifications list (many bullet-like lines). Also Preferred Qualifications list. We need to decide sections: Requirements vs Qualifications vs Skills. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content appropriately.
Minimum Qualifications likely go under Requirements (or Qualifications). Preferred Qualifications maybe under Qualifications. Skills could be extracted from qualifications? But we can also put technical skills under Skills. However we must not invent sections with filler. We need to ensure each section has real specific content.
We have Pay: "Salary or Pay Range: $3,101.60 - $5,628.00 Salary Frequency: Bi-Weekly". That's specific pay info, so we can include Pay section.
Schedule: "Shift (Work Schedule): Mon-Fri, 8 AM - 5 PM". Also "This position is 100% remote". That's schedule info (work hours). So we can include Schedule section.
Benefits: There's a Benefits section describing benefits. So include Benefits.
Now we need Requirements and Qualifications sections. We have Minimum Qualifications (a long list) and Preferred Qualifications (also a list). We could put Minimum under Requirements, Preferred under Qualifications. Or we could combine but better to separate.
We must not repeat job title as heading. Also not include Job ID etc. We'll drop metadata like Apply By Date, POSITION INFORMATION etc unless they are substantive? Apply By Date maybe not needed? It's metadata but could be considered minor; we can drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Apply By Date, POSITION INFORMATION lines (Salary etc we already used for Pay and Schedule). The rest like Department Overview etc maybe not needed? Could be part of About the role? But we already have summary. Department Overview: "Academic Information Systems develops and delivers critical web applications and services for the schools of medicine and nursing." That's additional context about the role; could be included in About the role paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all substantive info from the posting, but we can format it. Thus we need to include: - About the role: includes job summary + department overview maybe. - Responsibilities: key responsibilities percentages. - Requirements: Minimum Qualifications list (each bullet). Must preserve all details. - Qualifications: Preferred Qualifications list. - Skills: maybe we can extract skills from qualifications? But we already have qualifications sections; maybe we can omit Skills if no distinct content beyond qualifications. However we need to decide if we should include Skills heading only if there is real specific content for skills not already covered. The qualifications lists include many skills (e.g., Angular, Java, Spring, etc). Could treat those as Skills. But we already have Requirements and Qualifications sections; maybe we can put technical skills under Skills and keep Requirements for education/experience? However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they ask to use those headings; we can include both if they have content. We have Minimum Qualifications (requirements) and Preferred Qualifications (qualifications). So we can have both. Skills: Could we extract a list of skills like "Ability to design, develop, implement, debug and test user interfaces", "Experience using or familiarity with front-end API programming", etc. Those are more like abilities. Might be considered skills. But we already have many in qualifications. To avoid thin sections, maybe we omit Skills if content would be duplicate. However we must preserve all substantive info; if we omit Skills heading, we still need to include that info somewhere else. We could place those ability statements under Requirements or Qualifications as appropriate. Many of those are in Minimum Qualifications already (e.g., "Ability to design, develop, implement, debug and test user interfaces" appears in Minimum Qualifications). So we can keep them there. Thus we can have: - About the role (p) - Responsibilities (ul) - Requirements (ul) containing Minimum Qualifications items. - Qualifications (ul) containing Preferred Qualifications items. - Benefits (ul) maybe list of benefits? The benefits paragraph is prose; we can keep as
. - Pay (p) with salary range and frequency. - Schedule (p) with shift and remote. We must not include sections with filler like "commensurate with experience". We have specific pay and schedule. Now we need to format HTML. We'll output:
About the role
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. Academic Information Systems develops and delivers critical web applications and services for the schools of medicine and nursing.
Responsibilities
- Web Application Programming (85%)
- Business Systems Analysis and System Design (15%)
Requirements
- 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)
- 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
Qualifications
- 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
- 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
Benefits
Outstanding benefits and perks are among the many rewards of working for the University of California. UC Davis offers a full range of benefits, resources and programs to help you bring your best self to work, as well as to help you and your family achieve your health, wellness, financial and career goals. Learn more about the benefits below and eligibility by visiting UCnet Benefits Page or Benefits Summary for UC Davis Health Employees or Benefits Summary for UC Davis Employees. High quality and low-cost medical plans to choose from to fit your family's needsUC pays for dental and vision coverage for you and your familyRetirement plans for eligible employees including Pension and other Retirement Saving PlansSupplemental insurance offered including additional life, short/long term disability, pet insurance, legal coverage, accident, critical illness and hospital indemnityPregnancy and Parental Leave, Family & Medical Leave, Adoption Assistance and Pay for Family Care and Bonding for eligible employeesLactation Support Program and Family Care discounts and resourcesEmployee Well-being resources and programming to support thriving in all aspects of employee’s livesOn-site Employee Assistance Program including access to free mental health servicesGenerous amount of paid Holidays annually as outlined in the UC Policies or Collective Bargaining AgreementsPaid Time Off/Vacation/Sick Time as outlined in the UC Policies or Collective Bargaining AgreementsContinuing Education (CE) allowance and Staff Education Reimbursement Program for eligible employeesAccess to free professional development courses and learning opportunities for personal and professional growthPublic Service Loan Forgiveness (PSLF) Qualified Employer and Student Loan Debt Counseling Program for eligible employees
Pay
Salary or Pay Range: $3,101.60 - $5