Customer identity and conversation context
Keep customer history coherent as channels, devices and people change.
COAX FUTURES // CANDIDATE CHANNEL 001Melbourne preferred / Australia
SIGNAL RECOVERY.FIND THE ROLE.
A Senior Developer role is buried inside a live production system. Use the terminal to recover the product, the problem and the people—or skip straight to the unredacted brief.
LINK ESTABLISHED. Six signals are obscured by ambiguity.
Type scan or select any command below. Every recovered signal clears one target.
This is discovery, not an assessment. Your progress or score never affects your application.
Try a command:
Senior Developer · Melbourne preferred / Australia
Shape howbusinessestalk.
RoleSenior Developer
LocationMelbourne preferred / Australia
TeamSmall product and engineering team
PlatformProduction SaaS
MandateHigh technical ownership
MethodAI-native development
The product
One customer. Many channels. The context has to survive.
COAX / THE SYSTEM
Customers move between phone, SMS, email and web while expecting one coherent conversation. Identity, timing, state and human handoff must survive.
Trace the real behaviour before changing it. Find the hidden contracts, risky edges and assumptions nobody wrote down. This is brownfield engineering, not a clean-room rewrite.
What you’ll be working on
Concrete work.
Visible impact.
This is not a ticket-taking role. You’ll help decide architecture, sequencing and implementation rather than receiving fully specified tickets from above.
Telephony and messaging workflows
Make calls, messages, routing, timing and handoff predictable.
APIs and third-party integrations
Design for retries, idempotency, partial failure and clear state ownership.
Reliability, deployment and observability
Make failures visible, releases safer and production behaviour explainable.
AI-assisted product workflows
Set the boundary between autonomous action and human judgement.
Simplify an existing architecture
Remove accidental complexity without breaking customer contracts.
Problems on
the table.
Product and engineering questions you would help turn into decisions and safe releases.
01
How should one customer identity survive across channels without losing conversation context?
02
Where should AI act autonomously, and where should a human remain in the loop?
03
How do we simplify a rapidly evolved production platform without stopping product development?
04
How do we keep communications dependable while shipping quickly?
People you’ll build with
Direct access.
Real decisions.
You’ll work directly with the people shaping the product and technical direction. Good evidence can change the plan.
The first stage is a short technical conversation focused on a real difficult problem. No trivia or algorithm theatre.
PS
01 / Technical leadershipMelbourne
Dr Peter Stanski
Coax CTO · Technical Lead
Peter leads Coax’s technical direction and works with you on architecture, sequencing and hard decisions. He stays on the tools and gives strong engineers room to own outcomes.
OL
02 / Product and interfacesMelbourne
Oliver Lardner
Product & Technology Consultant
Oliver helps translate customer and organisational problems into systems the engineering team can actually build. His background spans software, human-computer interaction, games and immersive technology.
The engineering bar.
Calm around complexity. Opinionated, not precious. Close to the customer.
01Senior software engineering judgementRead unfamiliar production systems.
02Architecture and API designBoundaries that survive change.
03Debug across system boundariesTrace the real behaviour.
04Break ambiguity into safe releasesProduction ownership included.
05Review coding-agent outputNever outsource judgement.
06Clear technical communicationExplain the trade-offs.
Melbourne preferred.
Elsewhere in Australia can work. Practical overlap with Australian working hours matters more than a pin on a map.
Show us
your thinking.
A CV gives us history. A clear account of a difficult system you made simpler tells us how you work.
If there is a fit, the first step is the technical conversation described above.