The role

You will build and maintain backend services, integrations and internal tooling, primarily in Rust. This is not a greenfield role where every difficult component can be replaced or rewritten. You will work within an established shared codebase, understand existing behaviour and make safe, incremental improvements.

Your responsibilities will include:

• Developing and maintaining backend services in Rust.
• Building and supporting REST APIs and third-party integrations.
• Working with asynchronous processes, queues and background services.
• Reviewing code and responding constructively to reviews of your own work.
• Diagnosing defects and production issues.
• Writing automated tests and maintaining backward compatibility.
• Working with relational databases, SQL and schema migrations.
• Documenting technical decisions and operational behaviour.
• Working with deadlines and competing priorities.
• Opening clear, reviewable pull requests for approval by the EU engineering team.
• Taking ownership of your work when something does not behave as expected.

Required experience

You must have:

• At least five years of professional software-development experience.
• Demonstrable experience building production software in Rust.
• Professional experience with at least one other backend language, such as Python, Go, Java, C#, C++ or TypeScript/Node.js.
• Strong SQL and relational-database experience.
• Experience building and consuming REST APIs.
• Experience working within an established engineering team.
• Experience maintaining a shared production codebase.
• Experience both reviewing code and receiving detailed code review.
• Experience supporting systems used by real customers.
• Experience diagnosing incidents and contributing to their resolution.
• Experience working with deadlines and conflicting priorities.
• Experience completing safe database or schema migrations involving production data.
• An understanding of backward compatibility and controlled releases.
• Experience working with security and access controls, ideally within a regulated organisation.
• Clear written and spoken English.

Personal projects are welcome as additional evidence, but they do not replace the required professional production experience.

Useful experience

Experience in any of the following would be beneficial:

• Tokio, SeaORM, Axum, Serde or the wider Rust asynchronous ecosystem.
• PostgreSQL, Microsoft SQL Server or MySQL.
• RabbitMQ, Kafka, NATS or another message broker.
• Docker and Kubernetes.
• Azure or another major cloud platform.
• OpenTelemetry, structured logging and production monitoring.
• Keycloak, OAuth 2.0 or OpenID Connect.
• SOAP, XML, HL7 or healthcare integrations.
• CI/CD pipelines and controlled deployment processes.
• Working in healthcare, financial services, government or another regulated sector.

Healthcare experience is useful but not required. We can teach the domain; we need you to bring sound engineering judgement and proven production experience.

Security and access model

MedoSync processes sensitive healthcare information, so international contractors work within a deliberately restricted security model.

You will:

• Work with synthetic, anonymised or non-production data.
• Have no direct access to real customer personally identifiable information.
• Receive access only to the repositories and systems required for your work.
• Work through feature branches and pull requests.
• Have your changes reviewed, approved and released by authorised EU-based engineers.
• Be expected to follow MedoSync’s security, confidentiality and development procedures.

These controls protect our customers while allowing international engineers to contribute meaningfully to the product.

Contract terms

• This is a business-to-business contractor engagement.
• The maximum rate is €250 per working day.
• Contractors are responsible for their own taxes, insurance, equipment and local legal obligations.
• The contract does not include paid annual leave, sick leave, pension contributions or employee benefits.
• The engagement is subject to identity, professional-reference, right-to-contract and security verification.
• You must be legally permitted to provide services from your country of residence.
• Recruitment agencies and third-party candidate representatives will not be considered.

Contract rate

MedoSync engages international contractors using location-adjusted rates. Your rate will reflect:

• Your country of permanent residence.
• The local market for an experienced backend software engineer.
• Your professional Rust and production engineering experience.
• The proposed contract structure and working arrangements.

The maximum rate for this position is €250 per working day. This is an upper ceiling and should not be interpreted as the standard rate in every country.

The agreed rate will be confirmed before the technical interview, so neither party is asked to complete a lengthy recruitment process without knowing whether the commercial terms are workable.

How to apply

Please provide the following to [email protected]

1. Your CV.
2. Your LinkedIn profile.
3. Your GitHub profile or other relevant code samples.
4. Your country of permanent residence and time zone.
5. Your expected daily rate in euro.
6. Your availability and notice period.
7. A short description of the most substantial Rust system you have worked on professionally.

Your expected rate must be appropriate to your experience, country of residence and the local software-engineering market. Applications requesting more than €250 per day cannot be considered.

Applications that provide only personal or recently created demonstration projects, without evidence of professional production experience, will not progress.

Company description:

Based in Dublin, Ireland and Founded in 2019, MedoSync is on a mission to eliminate waste from the medical billing so that hospitals resources are freed up to focus on great patient care; insurers can concentrate on activities with maximum benefit for their members health; and doctors can spend more of their working time with their patients. We are guided by two values, growth and accountability.

Growth:

“Someone with a growth mindset views intelligence, abilities, and talents as learnable and capable of improvement through effort. On the other hand, someone with a fixed mindset views those same traits as inherently stable and unchangeable over time.” What does this mean for our stakeholders? Company: We are in the business of change. We are moving the healthcare industry from paper based systems to web based systems. We must believe in the capacity for change and improvement. Growth doesn’t happen alone and by definition it means we don’t have all the answers. We believe in the power of being open to change and improvement. We seek opinion, we seek expertise and we make informed decisions based on what we learn. Learning from experience and integrating experience is a key component of how we run the business. People: We value people who don’t think they are done. They are looking to improve themselves, learn new things, try new things and benefit learning gives you – experience. Customers: Our customers are moving to a new way of doing things. They are asking their staff to learn new skills, to do things they haven’t done before and to embrace the chaos of change. We seek these customers out as ideal partners.

Accountability:

“Accountability at work. It means showing up and setting out to accomplish the things you’d said you’d do. It’s about taking personal responsibility for your work. It’s also trusting in your teammates and knowing you can count on each other to get things done.” What does this mean for our stakeholders? Company: Achieving accountability means setting clear objectives for the company and communicating this path to everyone who is part of achieving the objectives. Everyone is working to the shared objective and can see their part to play in it. Accountability means honesty and transparency. Accountability allows for failure. People: We value people who take responsibility for their work and complete this work to the best of their abilities. They don’t mind being held to account or holding their team to account in order to achieve better outcomes. This is done in a respectful and collaborative context. Customers: We have obligations to our customers and we must make sure we deliver a product that delivers exactly what we is promised.