Technical Lead/Architect

Job Description

Introduction

\n

Maryland Benefits (MD Benefits) is a dynamic, cloud-based platform. This enterprise-wide digital service allows organizations to build, test, host, operate, and integrate mission-driven applications, data, and emerging technologies. MD Benefits offers cloud-based Platform-as-a-Service (PaaS) capabilities, a shared data architecture, and product development services, all developed by the State of Maryland to help multiple agencies deliver and manage health, human, and social service benefits and programs. On July 1, 2025, the operation of the MD Benefits shared platform and statewide applications transitioned from the Department of Human Services (DHS) to the Department of Information Technology (DoIT).

\n

\n

***This is a contractual position, with limited benefits***

\n

***All hires need to be eligible to work in the U.S., either as a U.S. Citizen or those who have a Permanent Resident or green card, as the state of Maryland does not have the ability to sponsor employees***

\n

***Applicants are required to submit an up-to-date and accurate resume.***

\n

\n

Description of Work

\n

As part of the core PLX team, the Tech Lead / Architect partners closely with a Product and a UX to form the leadership trio responsible for delivery. This team builds the enterprise permitting and licensing solution itself — the shared platform other state agency programs migrate onto — and, in parallel, advises and consults on permitting and licensing (P&L) solutions across the state that sit outside the enterprise solution. The role serves as the senior-most engineering and architecture authority across both mandates, accountable for the technical strategy and the hands-on execution of the enterprise solution, and for the technical credibility PLX brings into every agency conversation.

\n

Stakeholder engagement is core to the role. The Tech Lead / Architect represents PLX's technical direction directly to agency partners, vendors, and leadership, and is expected to hold that room as capably as the codebase. Hands-on delivery carries equal weight: the person in this seat writes code, reviews it, and builds alongside the team on the enterprise solution, while also showing up as a trusted technical advisor when other agencies bring their own P&L problems to PLX.

\n

The role is hands-on across the stack, with backend depth as the primary strength: solution architecture, data and integration architecture, and system reliability are where the role spends most of its time, while remaining comfortable working in the front end to unblock delivery, pair with engineers, or prototype a pattern directly. The Tech Lead / Architect builds capability in agency teams across feature scoping, operations planning, software testing and debugging, and test-driven programming — leading by example rather than directing from a distance.

\n

The role owns architectural decisions for PLX as a program built on Platform MD infrastructure — defining integration patterns, data models, and service boundaries that other agency programs can extend. It ensures secure, scalable, and maintainable systems are built in alignment with agency needs and Platform MD's shared services, and it guides agencies from legacy environments toward modern, product-driven digital delivery.

\n

This is a senior individual contributor role requiring deep technical expertise, strong communication and leadership skills, and the ability to influence agency stakeholders, vendors, and internal teams. The Tech Lead / Architect operates with significant autonomy and executive presence.

\n

Tasks and Responsibilities

\n

Applications Software Engineering and Development

\n

\n
• Provides expert technical direction on system design, security, performance, accessibility, reliability, and maintainability, working hands-on in the codebase — backend by default, front end when delivery calls for it.

\n

• Engages with customer agencies to perform needs analyses and define opportunities for new or improved business processes, solutions, and services based on user needs.

\n

• Consults with agency partners to refine functional requirements and translates them into user stories and technical specifications.

\n

• Acts as a recognized and respected authority on a diverse range of highly technical software issues.

\n

• Collaborates closely with the Product and UX to ensure engineering decisions support user and program needs.

\n

• Communicates technical decisions, risks, and trade-offs clearly and persuasively to technical and non-technical stakeholders.

\n

• Implements modern engineering best practices — DevOps, CI/CD, test-driven and domain-driven development, and observability.

\n

\n

Architecture and Technical Strategy

\n

\n
• Defines, documents, and communicates the architecture patterns, standards, and blueprints that let PLX extend Platform MD's shared services without duplicating them — for application, data, and integration layers.

\n

• Designs secure, scalable integration approaches across systems — API management, authentication and authorization, and service-to-service communication — so agency programs can plug into PLX consistently.

\n

• Leads architecture reviews and technical risk assessments across application and data integration platforms, weighing trade-offs in the open rather than presenting decisions as already made.

\n

• Guides development teams in selecting frameworks, design patterns, and toolchains that support reusable, maintainable, compliant software — favoring what fits the team and the platform over a fixed stack.

\n

• Advises on modernization of legacy applications and refactoring toward cloud-native, service-oriented architectures, grounded in the constraints of the legacy systems PLX is retiring.

\n

• Maintains technical documentation and architecture decision records so architectural reasoning survives staff turnover and vendor transitions.

\n

• Mentors agency developers and junior architects on architectural thinking, scalability, and best practices, building agency-owned capability rather than dependency on the PLX team.

\n

\n

IT Project / Cross-Functional Leadership

\n

\n
• Reviews projects for technical feasibility and alignment with program objectives, and advises leadership before IT projects commence.

\n

• Determines project objectives and sets priorities; anticipates potential threats or opportunities.

\n

• Identifies, triages, and resolves technical blockers, including those tied to legacy systems, policy constraints, and staffing.

\n

• Applies human-centered design techniques to drive IT project decisions and confirm the right product is being built.

\n

• Leads cross-functional teams to develop innovative IT services and plans, develops, and executes complex IT projects.

\n

• Determines the size, skills, and roles a project team needs to deliver, and identifies appropriate team members.

\n

• Engages leadership in the design, development, and deployment of IT solutions using current and emergent technologies and best practices.

\n

• Represents PLX's architecture and technical direction in advisory conversations with other agencies pursuing their own permitting or licensing solutions, balancing PLX delivery commitments against statewide advisory demand.

\n

\n

\n

Relationship Management

\n

\n
• Works closely with customer agencies in a leadership role, navigating conflicting priorities from stakeholders.

\n

• Provides agency partners accurate, expert, and authoritative technical advice.

\n

• Builds cooperative relationships across agency, vendor, and internal teams.

\n

\n

Customer Enablement

\n

\n
• Enables agency ownership of the technical architecture and strategy for their programs, aligned to agency goals and user needs.

\n

• Coaches and mentors agency staff, vendors, and peers in engineering practices, contributing to long-term capability-building.

\n

• Serves as a technical advisor to agencies building or evaluating their own permitting and licensing solutions outside PLX, translating PLX's architecture and lessons learned into guidance those teams can act on.

\n

\n

Qualifications

\n

Experience

\n

\n
• 10+ years of IT experience in application development, system integration, or technical leadership roles.

\n

• 5+ years as a hands-on application or solution architect, with demonstrated backend depth — solution architecture, data modeling, and integration architecture — alongside working comfort in the front end.

\n

• Experience architecting solutions in cloud environments, including native cloud services for compute, storage, and managed data.

\n

• Working knowledge of data integration platforms, ETL pipelines, and data flow design across disparate systems.

\n

• Experience designing systems with security, performance, accessibility, and compliance built in from the start.

\n

• Proficient with version control, CI/CD pipelines, and modern DevOps tooling.

\n

• Exposure to government or benefits-adjacent systems — permitting, licensing, eligibility, or similarly regulated domains — is a strong plus.

\n

\n

Education

\n

\n
• Bachelor's degree in Computer Science, Information Systems, or a related field; or three years of equivalent experience in a related field.

\n

\n

Attributes

\n

\n
• Comfortable owning both the whiteboard and the pull request — this role designs the architecture and builds parts of it.

\n

• Equally at home in a stakeholder meeting and a code review; treats both as core to the job.

\n

• Writes and speaks plainly; can make a technical trade-off legible to a non-technical stakeholder without losing the substance.

\n

• Treats architecture as something the agency will own after the engagement ends, and mentors accordingly.

\n

\n