Job Description

We are looking for Laravel experts to join our fully remote and growing team. This specific position is a director seat for some internal facing applications.

A Director owns the execution of one cluster. You run the systems the department is built on, manage the people inside your area, and you’re the first to see (and name) when something is off.

If you are interested and ready to lead a team living and breathing Laravel, we would love to have you apply.

Position Summary

1. You make the calls in your cluster. Real authority comes with the seat. If you’re reaching for the phone to ask before deciding, the role hasn’t landed yet. Escalate only what you genuinely can’t decide.

2. You hold accountability. When your team misses, you feel it and you address it directly, with the person. You don’t quietly redo the work or slide the deadline so nobody notices. Giving critical feedback is part of the job, not a side task.

3. You estimate and surface risk before it bites. Timelines for your work, dependency risk, what’s blocked and why: weekly, in writing, before you’re asked.

4. You build transferable, not heroic. Your cluster should keep running when you’re out. If it only works because it’s in your head, that’s a gap to close, not a strength.

5. You own the quality and security of what your cluster ships. Anything in our Laravel stack that’s yours is yours, not “the team’s.”

6. You are still in the trenches. You lead by example being the first and the last to make things happen.

Qualifications

– Are the expert in the area. You’re the subject-matter authority for your cluster. When the VP or CTO asks “what’s the state of X,” you have the answer without going to dig.
– Solve operational friction. The small stuff that bogs the team down (handoff confusion, unclear scope, the recurring papercut) you fix or design around. You don’t escalate friction; you absorb and resolve it.
Manage the people executing. You set the schedule, assign the work, hold the standard. Your team’s misses and wins are yours.

Are first to identify an issue. Dependency risk, a slipping timeline, a quality problem: you raise it early, with the data and a proposed path. Not “here’s a problem,” but “here’s the problem, here’s what I’d do, here’s the default if we do nothing.”

Own your cluster’s rapid response. You directly manage a Triage/Support engineer for under-24hr urgent items in your area. You decide what’s urgent, what waits, and you own that the fast lane actually closes. It’s part of your cluster, not someone else’s queue.

Present solutions. You gather and present to the VP, the CTO, exec. Lead with the conclusion, data as backup. Translate engineering reality into a decision the room can make.

Hold high attention to detail. You catch the thing before it ships, not after the complaint comes in.

Share.
Leave A Reply