Why Workforce Development Is One of the Hardest Jobs in the Social Sector

Stay Connected

Get the fifth lens on the work that’s changing communities. Our take on what actually moves the work forward.

Ask a workforce development professional to describe their job, and you’ll usually get a response that vastly undersells the work. “Career navigator.” “Employment specialist.” “Case manager.” “Job developer.” Each of these titles captures only a sliver of what the role actually entails: labor market analyst, behavioral coach, benefits eligibility expert, relationship manager, and translator. Not to mention all the unnamed emotional work required to support a caseload of dozens of job seekers: cheerleader, trauma specialist, motivator, accountability partner, coach.

It’s a lot! And it’s so much more than simply “getting someone a job.”

Being successful in this role requires a massive amount of coordination and collaboration with multiple social service agencies. Ensuring clients have stable housing, reliable transportation, consistent childcare, appropriate work clothes, sufficient access to food, and proper physical and mental health care are all precursors to the actual work of training, resume development, and interview prep. Over time, the job has quietly absorbed these additional functions, often without training, credentialing, supervision, or compensation catching up.

Quite simply, workforce development professionals are overworked because the system isn’t designed for success.

Fragmented funding streams, siloed training providers, disparate higher education programs, antiquated technology and data sharing platforms, and perverse incentives all contribute to a system designed for compliance rather than actual problem solving. It’s in the midst of this broken system that workforce development professionals are expected to help job seekers meet their basic needs, achieve career stability, and increase their economic mobility.

It’s little wonder burnout is so common!

Challenge #1: Coordination

A single client might touch WIOA-funded services, a community college’s non-credit workforce program, a TANF work requirement, SNAP E&T, an employer’s HR system, a criminal background check vendor, a childcare subsidy office, and a housing authority—each with its own eligibility rules, its own intake form, its own definition of “enrolled,” and its own outcome metric that has nothing to do with any other system’s outcome metric.

The workforce professional’s role is the only one in that entire network whose job is to see the whole picture across all the silos. They’re asked to coordinate with none of the authority, data access, or funding flexibility that actually makes that possible.

Challenge #2: Time

Supporting an individual to get a good job takes time, lots of time. Something workforce development professionals aren’t afforded much of. (Re)building a job seeker’s confidence, ensuring they are connected to appropriate wrap-around supports, identifying their work values, skills, and competencies and then connecting those to available jobs—all of this takes multiple conversations to yield quality outcomes. But funders tend to pay for what they can count, so the most important part of the job—where the transformation actually occurs—is structurally under-recognized and underfunded.

Challenge #3: Disconnected Data Systems

Workforce data systems are typically built to satisfy a single funding stream’s reporting requirements, not to be interoperable with anything else. A community college’s student information system, a workforce board’s case management platform, and a TANF agency’s eligibility system were procured years apart, from different vendors, for different compliance purposes, often without anyone in the room asking whether they’d ever need to share a client record.

The result is that the workforce professional becomes the manual data integration layer. They’re the ones re-entering the same intake information into four systems, or calling a partner agency to ask whether a client actually completed a program because the systems can’t confirm it electronically, or holding the longitudinal picture of a person’s progress in their own notes because no shared record exists.

A sticky note that says help on a laptop keyboard

What Actually Needs to Change

The fix isn’t training for frontline staff on “better collaboration skills.” The people doing this work are often more sophisticated systems thinkers than the systems they’re navigating. They need (and deserve) upstream solutions: funding models that reward shared outcomes instead of siloed outputs, support for long-term program models, and data-sharing agreements built before programs launch rather than retrofitted after. Until that redesign happens, workforce professionals will continue shepherding job seekers through this maze, wearing as many hats as they need in order to serve as the throughline across this fragmented system.

Promising Solutions

Co-located, cross-trained “one-stop” teams with actual shared supervision.
American Job Centers were supposed to be this. Most became landlord arrangements with different agencies sharing a building, not a practice. A deeper version: staff from WIOA, TANF, SNAP, reentry services, unemployment, community college workforce programs, etc. report to a blended supervisory structure with a shared caseload. Cross-training is provided so a WIOA navigator can answer a basic TANF question without a referral, and a SNAP recipient can meet with both their safety-net case manager and employment specialist at the same time. Co-location without shared supervision and cross-training just recreates the silos under one roof.
Fund the boring translation layer.
A lot of interoperability money goes to shiny new platforms. The actual unlock is often just funding a translation/API layer that sits between existing legacy systems, so agencies don’t have to rip and replace what they already have (and already know how to use) in order to connect to partners. This is less exciting to fund but far more achievable on realistic public-sector budgets and timelines.
Regional data trusts with a neutral third-party governance body.
Rather than bilateral data-sharing MOUs between every pair of agencies, a shared data trust lets multiple agencies contribute to and query a common record store under a single governance and consent framework, managed by a neutral entity (often a university, a regional workforce board, or a nonprofit intermediary) that no single agency controls. This is a heavier lift up front but is the only model that actually scales past two or three partners.

The fact that the public workforce system experiences any wins is due in large part to the individuals who have learned how to work around the system constraints, who have forged new ways of working in spite of the system. This job will always be hard—we’re talking about people’s livelihoods, after all—but the system doesn’t have to make it harder.