Payroll Systems Analyst

You learn how payroll, HR, and accounting actually work at Yeled—not the theory, but the real day-to-day. You become the person who can explain it clearly to leadership and staff alike.

Most issues blamed on ExcelForce are actually caused internally—timing, manual steps, retroactive changes, or process misunderstandings. You figure out which is which so we stop blaming the vendor for our own gaps.

When the CTO asks "what's going on with payroll?"—you have the answer. No more asking five people and getting five different stories.

You work in the Jira queue. When issues come in, you ask clarifying questions to understand: Is this user error? A timing issue? Something that's happened before? A real system problem?

You filter out the noise. Only real system issues get escalated. You communicate with the vendor calmly and with clear information—not in panic mode.

Root causes, workarounds, "this is just how it works" limitations. You document it so the next time this happens, we already know the answer.

How does time entry flow to payroll to accounting? Why did this person's check get messed up? You can explain it so a non-technical person understands.

You don't need perfect documentation. You can learn by watching, asking, and piecing together how messy real-world processes actually work.

You write well. You ask questions that get to the point without making people defensive. You explain things so they stick.

Payroll issues stress people out. You're the steady presence—methodical, not reactive, never adversarial.

This isn't a coding role. We have developers for that. You need to understand systems and processes, not build them.