> Markdown version of [/jobs/ext/3969447-software-architect](https://www.wearedevelopers.com/jobs/ext/3969447-software-architect). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Architect - **Company:** Harris Computer Systems - **Location:** Elizabethtown, PA, United States - **Experience:** Expert - **Salary:** $115,000.0 - $125,000.0 - **Contract:** Permanent contract - **Skills:** Query Performance, Java (Programming Language), Audit Trail, Microsoft Azure, Cloud Engineering, Code Coverage, Code Review, Continuous Integration, Learning Management Systems, Relational Databases, Software Design Patterns, Monitoring of Systems, Hibernate (Java), Java Persistence API, PostgreSQL, Linux Servers, Oracle (Applications), Software Architecture, Software Engineering, TypeScript, Web Content Accessibility Guidelines, Enterprise Software Applications, ReactJS, Liferay, Spring-boot, Data Layers, AngularJS, Infrastructure Automation Frameworks, Information Technology, Restful APIs - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-architect-elizabethtown-pa--cf8068c0-d246-4c30-a59c-b97ea8d54e0c ## About the Role Software Architecture, Learning Management System (LMS), Secondary School, Statement of Work (SOW), Oracle, Hibernate, XDoclet, Java Persistence API (JPA), PostgreSQL, REST (Representational State Transfer), * 8+ years building enterprise software, including 5+ leading engineering teams or owning architecture on significant programs * You have actually modernized a large legacy system - decomposed a monolith, replaced a data layer, migrated a platform off an unsupported stack. We care far more that you have done it than which technologies it happened to be. * Strong Java and Spring Boot, and genuine comfort in a modern front-end stack. We are targeting Angular, React, and TypeScript. * Relational database depth - schema design, ORM behaviour, query performance. Oracle and PostgreSQL are both in play. * Experience owning a vendor or systems-integrator relationship: writing the specification, defining acceptance, and holding the line when delivery drifts. * Cloud-native delivery on Azure or equivalent - CI/CD, infrastructure as code, monitoring and observability. * Building to WCAG 2.2 AA. Accessibility is a contractual obligation passed to us by the districts we serve, not a nice-to-have. * Experience working with Linux servers, Bachelor's degree in software engineering, computer science or a related field, or the equivalent in demonstrated experience. We mean the second half of that sentence. ## Description * Define the target architecture and the sequence to reach it. The platform has no module seams today, so this is strangler-fig work around functional verticals on a shared foundation. * Specify and accept our modernization partner's deliverables against defined criteria. You are the technical counterpart holding a fixed-price statement of work to account. * Lead the data-layer modernization: retire the XDoclet-generated Hibernate mappings in favour of JPA, and oversee the Oracle to PostgreSQL conversion alongside a specialist contractor. * Stand up the REST API façade and the identity, organization and enrollment foundation that everything else depends on. * Establish engineering practice from close to zero - CI/CD, code review, and characterization tests on a system with almost no test coverage today. * Recommend the shape of the team, and help us hire it. Ongoing * Architecture standards, design patterns and technical governance * Mentoring engineers and contractors * Making AI-assisted development a normal part of how the team works * Ensuring quality, maintainability, accessibility and security are built in rather than retrofitted WHAT GOOD LOOKS LIKE AT 90 DAYS A validated target architecture and a sequenced roadmap that leadership can fund · acceptance criteria agreed in writing with our modernization partner · your recommendation on the team we should build and in what order., * K-12 or higher-education technology, and the 1EdTech standards - LTI 1.3, Common Cartridge and Thin Common Cartridge, OneRoster, QTI * Oracle-to-PostgreSQL migration, ora2pg, cutover planning and rollback strategy * Establishing test coverage on systems that have none * Remediating security findings in legacy code - secrets management, dependency CVEs, audit logging * Student data privacy: FERPA, COPPA, and district data-protection agreements * Portal frameworks such as Liferay. We are migrating away from it, so we are interested in the experience rather than a plan to keep it. * Gamified learning experiences and engagement mechanics * Fluent use of AI-assisted development tools in real delivery work, not just experimentation