Software Engineer in Sydney

Be part of something.

Every time a shipment moves, Yojee makes it visible, intelligent, and efficient.

We’re not building dashboards for clicks. We’re building technology that actually moves the world — optimising how freight flows across air, ocean and road.

Logistics is a global industry with real operational complexity.

With MOSAIC and TCMS, we are building products that handle real-time events, high data volume, and mission-critical workflows.

If you're a senior fullstack engineer who wants to own product features end-to-end — from problem framing, through Elixir services and React interfaces, to production health — this role is for you.

The Opportunity

We're hiring an experienced Software Engineer (Fullstack) to take ownership of significant product surfaces — backend through frontend — inside our product squads.

You’ll work closely with product, design, and other engineers as a product engineer: someone who owns the why as much as the what.

You'll deliver vertical slices across Elixir / Phoenix services and React / Type Script interfaces, set the quality bar across both halves of the stack, and shape the patterns the wider team relies on — not just ship features.

This isn't brochureware or content management.

You'll be working on enterprise-grade, data-intensive applications where performance and state management matter to global logistics networks.

Agentic AI is a real part of how we work — across our SDLC and inside the product.

We use coding agents, agentic prompting, and MCP-based tooling in day-to-day delivery, and we're building native agentic AI into the platform itself, not a bolted-on chatbot.

You'll grow your craft inside that environment, not separate from it.

• What You’ll Do
• Own Features End-to-End, Across the

Stack: Take features from problem definition through Elixir / Phoenix services, React / Type Script UI, rollout, and post-launch health — work is not done when the PR merges.

Make sound architectural decisions across both halves of the stack, and push back constructively when a brief is unclear or solving the wrong problem.

• Set the
• Quality

Bar: Write clean, well-tested, maintainable code that others reference as the standard — on both sides of the stack.

Give substantive code reviews — including on AI-generated code — that catch real issues and measurably improve the work.

• Shape
• Shared

Foundations: Lead the design and evolution of patterns, abstractions, and shared components — backend modules, frontend libraries, integration points — that let other engineers contribute effectively across the stack.

Improve performance, observability, and developer experience as deliberate outcomes, not side effects.

• Drive Squad-Level
• Technical

Decisions: Contribute resolutions in architecture and engineering standards conversations — backed with clear reasoning, updated with new information.

Influence how other engineers approach problems through code, reviews, and technical discussion.

• Multiply the

Team: Onboard and informally mentor more junior engineers as a natural part of how you work.

Translate technical context clearly for product, design, and non-engineers; keep async communication (PRs, design docs, Slack) complete enough that the team can act without follow-up.

• Own the
• User

Problem: Operate as a product engineer — understand the user problem and business rationale behind features, use data to validate that what shipped actually works, and propose the right scope rather than executing the requested scope blindly.

• Use AI Deliberately: Accelerate good work with coding agents, agentic prompting, and MCP-based tooling — applied to backend and frontend alike.

Recognise and manage the risk in your own work and in what you review.

• What You’ll Bring
• 6+ Years of

Experience: Building, shipping, and owning modern production web applications across both backend and frontend — including responsibility for production health, not just initial delivery.

• Backend

Depth: Strong functional backgrounds experience (commercial or substantial open-source), considered if Elixir adoption is realistic for you.

Solid understanding of distributed systems or event-driven architectures, relational databases (Postgre SQL ideal), and operational concerns (CI/CD, observability, performance).

• Frontend

Depth: Strong React, Type Script, Java Script, and solid CSS fundamentals.

Comfortable with state management, performance tuning, accessibility, and testing strategy in data-dense interfaces.

• Senior Data-Intensive

Knowledge: Track record on complex enterprise web applications (ERPs, trading platforms, logistics or operational systems) where state, latency, and edge cases matter — not content-heavy or CMS-driven projects.

• The Scaffolder Mindset, At

Scale: Hands-on experience designing and evolving patterns, libraries, and CI/CD pipelines that make other engineers faster and safer.

You've set a quality bar others adopt — on either side of the stack, ideally both.

• Product and
• Commercial

Context: Make engineering decisions with the user problem, business rationale, and maintainability in mind — not just the ticket.

Able to articulate technical debt and trade-offs in terms non-engineers can act on.

• Ownership and

Judgement: Operate effectively when problems are ambiguous: break them down into executable work for yourself and others, raise risks early, and follow through to verify what shipped behaves as expected.

• AI-Fluent

Delivery: Practical experience using coding agents, agentic prompting, and MCP-style tooling across backend and frontend.

You can articulate where AI accelerates you, where it misleads you, and how you validate its output.

• Communication and

Collaboration: Clear, calibrated, and direct.

Comfortable giving and receiving substantive feedback; able to disagree well and update your view when the evidence does.

• Bonus Points For
• Experience leading a meaningful slice of a backend service, frontend platform, or design-system effort
• Experience with intricate workflows and high information-volume interfaces (operations consoles, control rooms, trading)
• Open-source contributions, particularly to BEAM-ecosystem projects or frontend tooling others depend on
• Experience with real-time data, event-driven UIs, or large-scale data visualisation
• Experience in greenfield or scaling-stage environments where you set patterns, not just follow them
• Exposure to logistics, supply chain tech, or integration-heavy domains (ERPs, TMSs, telematics)
• Why You'll Love Working Here
• Real Engineering, Real

Impact: You'll work on meaningful product challenges with direct line of sight to operational users — concurrency, real-time events, data orchestration, and clear UI all matter here.

• Shape What's Being Built: Our architecture is established but not rigid. There's room to grow into bigger problems as you progress, and to influence patterns as you do.
• Small Team, Big Autonomy: No bureaucracy. Direct line to product, design, and leadership. You get context, ownership, and visibility from day one.
• Growth
• With

Meaning: This is a place for builders who want to leave a mark on something real.

We use a published levels framework, so progression on craft, scope, and leadership is a real conversation — not a guessing game.

#J-18808-Ljbffr