Job Description

Reapit – Who are we?

Reapit is the original, end-to-end business technology provider for estate agencies of all sizes. We’ve been helping sales and lettings agents to build relationships and grow their businesses for more than 25 years. Our technology connects property professionals in Europe, the Middle East, Australia, and New Zealand with buyers, sellers, tenants and landlords to power the relationships that change lives.

In Australia, Reapit stands as the preferred technology choice among the nation's leading estate agents and agencies. Tailored to the unique demands of the Australian property market, Reapit provides successful leaders with unparalleled tools across sales, property management, client relations, and data analytics, reinforcing their position at the pinnacle of real estate excellence.

What you’ll be doing

We’re building a new Comms Hub – a centralised service that will handle outbound (and eventually inbound) communications across Reapit’s client products: email, SMS, push notifications, and WhatsApp, with room to add further channels over time. Today, communications logic is scattered and inconsistently implemented across products; you’ll be part of the team building the platform that consolidates this into a single, reliable, well-architected service that other engineering teams integrate with. This is a foundational build rather than a migration – you’ll be helping design patterns and abstractions from scratch that other teams will depend on for years to come. The Senior Engineer will design and deliver technical solutions that meet business requirements, embodying Reapit’s core values of Trust, Collaboration, Innovation, Excellence, and People.

Platform Design & Architecture:

• Contribute to the design of a provider-agnostic comms architecture, so that email, SMS, push and WhatsApp channels aren’t tightly coupled to any single vendor – enabling fallback providers on outage, and routing rules by category, geography, or country (e.g. domestic vs. overseas SMS).

• This matters in practice, not just in theory: different business units currently use different SMS providers directly – SMS Central, SMS Broadcast (being phased out), and MessageMedia – with Yabbr used as a fallback provider by some of the products. Sinch is Reapit’s new globally-contracted provider for SMS and email, and has itself acquired most of the providers above, though Sinch’s native SMS API isn’t yet live in ANZ. You’ll help design the abstraction that lets us consolidate onto Sinch over time without a hard cutover, while keeping fallback options – including Yabbr-style patterns – available.

• Help define abstraction layers and interfaces across providers (e.g. Mailgun, Sinch, SMS Central, SMS Broadcast, MessageMedia, Yabbr, FCM/APNs) so provider swaps or additions don’t ripple through consuming products.

• Contribute to decisions on message queuing, retries, and delivery-status handling – webhooks, bounce/complaint handling, and delivery receipts – consistently across channels.

Planning and Requirement Analysis:

• Collaborate Across Departments: Work closely with product managers, quality assurance, and client product teams to refine technical requirements and contribute to solution design for a service that will be consumed by multiple downstream products.

• Requirement Analysis and Estimation: Contribute to analysing technical requirements, conducting research, and estimating effort for planned work.

System Design:

• Technical Design and Implementation: Develop technical designs that meet business requirements and architectural standards, ensuring security, scalability, performance, and maintainability across multiple communication channels and providers.

Implementation:

• Code Development and Review: Actively write code and participate in the code review process, upholding and contributing to coding standards.

• Testing and Validation: Perform rigorous testing and validation of solutions, including cross-provider and cross-channel edge cases – e.g. carrier-specific SMS quirks, email deliverability and spam scoring, or WhatsApp template approval constraints.

• Documentation: Develop and maintain accurate documentation for engineering projects, including provider integration notes and failover behaviour, ensuring materials are produced and maintained for future reference and compliance.

Project Delivery:

• Agile Participation: Actively participate in agile ceremonies, including daily stand-ups, sprint planning, retrospectives, and reviews.

• Project Delivery: Contribute to delivering projects on time and to the required quality standards through strong technical execution, collaboration, and ownership of assigned work.

Maintenance:

• Technical Guidance: Provide technical guidance and support to team members through collaboration, code reviews, and sharing best practices.

• Continuous Improvement: Identify and implement opportunities to improve performance, maintainability, and engineering effectiveness across the comms platform.

Incident Management: Contribute to incident investigation and resolution – for example diagnosing failed message delivery through a specific provider or channel – support clear stakeholder communication, and help identify follow-up improvements to reduce recurrence.

Who we're looking for

At Reapit, we prioritise hiring individuals who share our values and possess the right attitudes and behaviours for success. Whilst some of the listed requirements may be important, don’t worry if you don’t meet all of them, we’d still like to hear from you.

Qualifications and Experience:

• Bachelor’s degree in computer science, engineering, or a related field - Essential.

• 7+ years in back-end software development with .NET/C# - Essential.

• Experience designing and building RESTful APIs and backend services, ideally with ASP.NET Core - Essential.

• Hands-on experience with Mailgun for transactional email sending – Essential.

• Experience with Sinch (SMS and/or email) is beneficial – Sinch is Reapit’s new global communications provider, and we expect to bring their email service into scope alongside SMS over time.

• Experience with any of SMS Central, SMS Broadcast, MessageMedia, or Yabbr is beneficial – familiarity with more than one is a strong plus, given how much these providers vary in API design and reliability for what should be a fairly standard capability. You should be able to describe a specific integration you’ve built and a provider-specific quirk that caught you out.

• Experience working with distributed teams.

• Experience contributing to systems that integrate with multiple third-party service providers, ideally with an abstraction or fallback layer sitting between the two.

• Experience incorporating agentic AI tooling into development, ways of working, and delivery.

Technical Skills:

• Strong proficiency in .NET/C# for backend development, including experience with ASP.NET Core, Entity Framework, and MySQL.

• Strong proficiency building distributed systems, ideally microservices, event-based architecture, and message queues.

• Understanding of email protocols and deliverability considerations – SMTP, DKIM/SPF/DMARC, bounce and complaint handling, and sender reputation.

• Understanding of SMS protocols and carrier behaviour – e.g. SMPP concepts, sender ID/short code conventions, delivery receipts, and the regional or carrier variance between domestic and international routes.

• Familiarity with push notification services (APNs, FCM) and/or messaging platform APIs such as the WhatsApp Business API, including template message approval workflows.

• Direct, practical experience integrating with Mailgun – Essential.

• Exposure to Sinch, SMS Central, SMS Broadcast, MessageMedia, or Yabbr is beneficial – exposure to more than one is a strong plus, since providers vary more than you’d expect on what should be fairly standard functionality.

• Experience with testing methodologies (unit/integration/E2E testing, mocking, shift-left), including patterns for testing against third-party providers without incurring real sends or costs.

• Proficiency in CI/CD pipelines and build tools.

• Exposure to public cloud platforms (preferably AWS) and familiarity with IaC tools like CloudFormation, CDK, and Docker.

• Familiarity with agentic AI development, with an emphasis on improving developer productivity (e.g. coding assistants, agentic workflows for test generation/debugging, documentation and runbook automation, and evaluation/guardrails for safe adoption).

• Understanding of SOLID design principles, and a good instinct for designing clean abstractions over volatile third-party dependencies.

• Awareness of regulatory considerations around consent and messaging – e.g. opt-out/unsubscribe handling, spam regulations, and data protection – is beneficial, though not essential at this level.

What your impact and success looks like

We expect your success and impact in the early stages of your career with us to look something like this:

As this is a 12-month contract engagement, we’re looking for someone who can ramp quickly and deliver from early on. In addition to the milestones below, you should expect to:

• Within 2 weeks: Have a working local environment, be reading the codebase unsupported, and be asking informed technical questions in code review and planning sessions.

• Within 1 month: Be shipping production code independently on moderately complex tickets, with minimal need for senior support.

• Within 6 weeks: Be working independently on complex features end-to-end, and delivering measurable value against the engagement’s priorities without requiring extended ramp-up support.

Within 3 months:

You will have a strong command of the comms platform’s core architecture and provider abstractions, and will be able to spot where a provider-specific quirk is likely to cause silent delivery failures before it reaches production. You will be independently owning complex features end-to-end, from design through implementation and testing, with minimal senior oversight. You will be raising informed, evidence-based suggestions on provider selection, fallback strategy, or process – even if the final call sits with the Staff Engineer or Principal. You will be holding a consistently high standard in your own code, reviews, and testing – setting an example other engineers on the team notice and follow. You will be working closely with client product teams to clarify integration requirements and flag scope or sequencing risks early.

Within 6 months:

Your technical input will be shaping how new channels or providers get integrated into the platform, and other engineers will be coming to you for guidance on the trickier cross-provider issues. You will be delivering complex aspects of the platform with a high level of autonomy, including edge cases around delivery failure and fallback routing that nobody else has fully untangled yet. You will be a trusted voice in technical planning and design conversations. You will be mentoring junior engineers on the team, particularly on reasoning about third-party provider behaviour and designing resilient abstractions. You will be championing engineering quality and best practices through solution design, implementation, testing, and documentation.

We operate a Flexible Working Policy and you are free to determine where you work from, be that from home or in the Sydney or Brisbane offices, and how often but we certainly recommend a balance.

Don't tick all the boxes? Neither do we

We care about our industry and want it to become a more inclusive and diverse place to work. So, we’re driven by hiring not only by experience and relevance for the role but by sharing our values and the right attitudes and behaviours for success. We are committed to Equal Employment Opportunity through attracting and retaining a complementary team of employees and building an inclusive environment for all. We feel we have an empowering environment where everyone is supported and respected, and we want you to feel this too. We welcome new ideas, thinking and approaches, whilst listening to all our employees.

“We are a 2025 Circle Back Initiative Employer – we commit to respond to every applicant.”