Senior Back End Engineer

tekFinder; Sydney; On-site; AUD 140,000 - 190,000; Full time

Job summary

tekFinder is building the integration layer for AI inside a fintech's collaboration platform in Sydney. A brand-new team of four engineers will own the MCP servers, agents, and the pipelines that let tools reach real domain objects.

You will focus on deep Java, clean integration, and a discovery-first approach to design. This role emphasizes practical, scalable engineering over vendor-specific stacks.

Qualifications

• Strong Java depth, not exposure — depth in a Java system.
• Experience integrating with third-party systems (HubSpot, Salesforce, Atlassian not required).
• Disciplined, structured design mindset with a discovery-first approach.

Responsibilities

• Own MCP servers exposed by the collaboration stack to bridge agents with real domain objects.
• Build bots that act as agents, capable of tool-calling and knowledge-grounded operations.
• Define the pipelines and domain-object boundaries that the larger AI platform relies on.

Skills

Java depth

Integration instinct

Discovery before code

AI fluency

Job description

We're building the integration layer for AI inside a fintech's collaboration platform.

Four engineers. Brand new team. First crack at wiring collaboration tooling into an AI SDLC - not a legacy system to patch, a layer to define.

What you own

• MCP servers, exposed by the collaboration stack, that let agents reach real domain objects instead of just talking.
• Bots that are actually agents - tool-calling, knowledge-grounded, wired into internal systems that matter.
• The pipelines and domain-object boundaries a much larger AI platform team builds on top of.

What you bring

• Java depth. Not exposure - depth. You make the right call on a Java system without being taught its intricacies.
• Integration instinct. HubSpot, Salesforce, Atlassian - the vendor doesn't matter. Knowing how to integrate cleanly with a third-party system does.
• Discovery before code. You ask what needs to be built before you build it, and you design it structured, not sprawling.
• Enough AI fluency to grow fast into MCPs, skills, and agents. You don't need to be there yet. You need to actually want to be.

No Jira or Atlassian background required here. A strong generalist with real integration judgment beats a specialist in one vendor's stack.