Website:
xalen.io
Job details:
Xalen
We’re looking for someone who can sit inside the Founder’s Office and understand technology beyond the surface.
The Discerner is not just an engineer, product manager, architect, or technical program manager. This role exists for someone who can look at a messy technical situation, separate signal from noise, understand what is actually happening underneath, and decide what needs to be built, fixed, killed, automated, rewritten, or escalated.
You’ll work directly with the founder across AI, product, infrastructure, engineering, automation, internal systems, experiments, and high-priority technical problems.
A lot of the work will begin without a perfect brief.
You may get a broken workflow, a strange production issue, a half-built product idea, an AI agent behaving unpredictably, an architecture decision, an internal bottleneck, or simply: “figure out why this is stupid and fix it.”
Your job is to discern.
Understand the system. Find the real problem. Make the right technical call. Drive it to execution.
What you’ll do
- Work directly with the founder on Xalen’s most important technical initiatives.
- Understand unfamiliar codebases, systems, APIs, infrastructure, and architectures quickly.
- Diagnose why products, agents, automations, or engineering workflows are failing.
- Separate symptoms from root causes.
- Turn vague technical ideas into executable architecture and implementation plans.
- Prototype aggressively when discussion is slower than building.
- Review technical approaches and challenge unnecessary complexity.
- Work across frontend, backend, infra, AI, data, automation, security, and developer tooling.
- Use modern AI coding tools and agents as force multipliers instead of treating them as autocomplete.
- Build internal tools and automation wherever humans are repeatedly doing machine work.
- Investigate new models, frameworks, APIs, infrastructure providers, and technical capabilities.
- Identify where Xalen should build, buy, integrate, automate, or ignore.
- Push technical projects across teams when ownership is fragmented.
- Break large engineering problems into the smallest useful executable path.
- Find edge cases before users find them.
- Question architecture when architecture becomes religion.
- Kill technical debt that is actively slowing the company down.
- Make sure technical decisions survive contact with production.
What makes someone good at this
You can read a system faster than most people can explain it.
You naturally ask, “What is actually causing this?”
You don’t confuse complexity with sophistication.
You can move between code, product thinking, architecture, infrastructure, AI systems, and business context without needing a translator.
You know when to investigate deeply and when to ship the ugly version today.
You are comfortable entering systems you did not build.
You can use documentation, logs, source code, metrics, experiments, and first-principles reasoning to reach a conclusion.
You are technically opinionated but willing to change your mind when the evidence changes.
You don’t need someone to convert every problem into Jira tickets before you can act.
You communicate technical reality clearly, especially when the answer is inconvenient.
Most importantly, you can take a technically ambiguous problem and come back with clarity.
This role is not
This is not a ticket-closing engineering role.
It is not purely management.
It is not a research role where the output is a document nobody executes.
It is not an architecture role where diagrams are considered delivery.
And it is definitely not a role for someone who needs perfectly defined requirements before starting.
Background
We care more about demonstrated technical range and judgement than a specific degree or title.
You could come from engineering, infrastructure, AI, security, product engineering, developer tooling, systems architecture, startups, technical consulting, or your own failed and successful experiments.
Bonus points if you’ve built things across multiple layers of the stack and broken enough systems to know where systems usually fail.
The operating principle
Observe deeply. Separate signal from noise. Find the truth. Execute.
That is the job of The Discerner.
Click on Apply to know more.
