Amsotics builds practical technology and business systems that help teams work with greater clarity, speed and control. This role sits within a delivery environment where software is expected to be useful in production, understandable to the people who operate it, and maintainable by the teams responsible for it. The successful candidate will work on real business requirements rather than isolated technical exercises. You will be expected to understand the problem behind a request, make sensible technical or operational decisions, document important assumptions, and deliver work that can be supported after release. The role also involves close collaboration with colleagues across technology, operations, design, finance, recruitment and leadership, depending on the project.
The position is designed for someone who enjoys ownership. You will not be limited to a narrow checklist of tasks. Priorities can move as customer requirements, internal processes and delivery schedules change, so we value people who can organise their work, communicate early when something is blocked, and make progress without sacrificing quality. You should be comfortable asking precise questions, reviewing existing systems before changing them, and using evidence from logs, data, user feedback or testing rather than assumptions. Amsotics teams value clean execution: small details such as validation messages, naming, documentation, access control, responsive behaviour and reliable handover matter because they affect the people who use the final system.
In this role, you will contribute to the full lifecycle of work. That can include discovery, requirements clarification, planning, implementation, testing, release preparation, production support and continuous improvement. You may be asked to investigate an existing workflow before proposing an improvement, work with a database or API, prepare a release note, review a design, test a candidate journey, analyse operational data, or support an issue reported by a user. The exact balance will depend on the role, but the common expectation is the same: understand the objective, execute carefully, and leave the system or process better documented and easier to operate than before.
Quality is treated as part of delivery rather than a final inspection step. Candidates should therefore be comfortable with structured checking, edge cases and failure scenarios. For technology roles this means validating inputs, handling errors, protecting sensitive information, reviewing database behaviour, considering performance and checking responsive interfaces. For design, analysis, support and delivery roles it means challenging unclear requirements, checking that a process works from the user's perspective, and ensuring that decisions can be traced back to a documented business need. We expect constructive collaboration when defects are found: identify the issue clearly, establish its impact, help isolate the cause, and verify the correction.
The working environment also requires professional communication. You may work with colleagues who have different technical backgrounds, so complex subjects should be explained in a way that helps the recipient take the next action. Written communication should be concise and specific. Meetings should have a purpose, decisions should be recorded where useful, and commitments should have visible owners. When working with external stakeholders, confidentiality, accuracy and respectful communication are essential. When handling candidate, customer or business information, you must follow the access controls and data-handling practices applicable to the system.
We are looking for someone who can combine practical execution with continuous learning. You do not need to know every tool on day one. You do need to demonstrate a strong foundation, curiosity and the ability to learn a new system without repeatedly relying on others for basic investigation. Experience in a services, software, consulting, operations or technology environment is useful because it develops the discipline required to work across changing priorities. Relevant qualifications are welcome, but demonstrable capability, portfolio work, project experience and problem-solving ability are also considered.
The first phase of the role will focus on understanding Amsotics' products, internal workflows, coding or operating standards, documentation practices and current priorities. You will receive context from the team and then be expected to take ownership of clearly defined work. As you become familiar with the environment, the scope will expand to larger deliverables and more independent decision-making. Progress is evaluated through the quality of outcomes, reliability of execution, collaboration, communication and the ability to learn from feedback.
A typical week may include a mixture of focused delivery work, review, planning, investigation and coordination. Some days will be highly execution-oriented; others may require more discovery or stakeholder discussion. We do not expect every day to look identical. We do expect commitments to be managed responsibly, risks to be surfaced early, and important work to be documented so that another team member can understand it when necessary.
This opportunity is suitable for candidates who want to build a long-term professional capability rather than simply complete isolated assignments. You will have the opportunity to work with production systems, real business constraints and cross-functional teams. That exposure can strengthen your technical, analytical, design, support or delivery judgement. It also means accountability is real: changes may affect live users, internal operations or business reporting, so careful review and appropriate approval are part of the job.
If you join Amsotics, you will be expected to bring a professional standard of conduct, respect confidential information, follow security requirements, and contribute to a constructive working environment. We value direct communication without unnecessary hierarchy, thoughtful disagreement when evidence supports a different approach, and people who take responsibility for closing loops. The strongest candidates are those who can explain not only what they built or completed, but why they chose the approach, how they tested it, and what they would improve with another iteration.
This vacancy may involve additional responsibilities as the business evolves. Amsotics may adjust priorities, tools and delivery methods to meet operational requirements, while keeping the core expectations of the role clear. Candidates should therefore be comfortable with reasonable change and willing to learn adjacent skills when they improve delivery outcomes.
The recruitment process may include an initial profile review, a practical discussion or assessment relevant to the role, and structured conversations with the hiring team. Candidates should be prepared to discuss previous work in detail, including their individual contribution, decisions made, challenges encountered and the outcome. Any employment offer remains subject to the applicable verification and onboarding process. Please provide accurate information in the application because the recruitment team may use the submitted profile and supporting documents during evaluation.
Above all, this role is about dependable execution. Whether the work involves software, infrastructure, data, design, analysis, security, support or delivery, the goal is to create outcomes that people can rely on. If you enjoy solving concrete problems, learning from capable colleagues, and taking responsibility for work from initial understanding through completion, this opportunity provides a practical environment in which to grow.
You will keep delivery work organised across people, priorities and dependencies. This includes maintaining action lists, coordinating meetings, following up on owners, preparing status updates and highlighting risks. You will work closely with technical teams without needing to write every line of code, but you should understand enough of the delivery lifecycle to recognise blockers and ask useful questions.
You will work in a practical, cross-functional environment with exposure to real production requirements and measurable business outcomes. The role provides opportunities to strengthen professional judgement, collaborate with experienced colleagues and build a broader understanding of how software and business operations connect. Specific compensation, benefits and working arrangements are discussed during the recruitment process and may vary by role and experience.
ROLE OVERVIEW
• Own assigned deliverables from clarified requirement through completion, documentation and handover.
• Collaborate with relevant engineering, design, operations and business stakeholders and communicate progress clearly.
• Review existing processes, code, data or documentation before making changes that could affect production behaviour.
• Identify dependencies, edge cases and risks early and propose practical next actions.
• Participate in testing, review and release activities appropriate to the role.
• Maintain accurate working documentation so important decisions and operating steps remain understandable.
• Protect confidential business and candidate information and follow access, security and data-handling requirements.
• Contribute ideas that improve reliability, usability, efficiency or maintainability without introducing unnecessary complexity.
• Respond professionally to feedback and use it to improve future work.
• Support related tasks reasonably required to meet the objectives of the role and team.
• Project coordination, task tracking and stakeholder follow-up
• Understanding of software delivery lifecycle and agile practices
• Documentation, meeting notes, status reporting and risk tracking
• Comfort working with developers, designers and business teams
• Strong organisation, communication and attention to detail
The successful candidate should also demonstrate professional communication, ownership, willingness to learn and the ability to work responsibly with confidential information. Equivalent practical experience may be considered where it demonstrates the required capability.