Opus 2

Associate

• In the role of **Market Development Associate**, you will be responsible for managing and developing key client relationships and strategic partnerships across the Middle East and Africa (MEA) region, driving growth in our Hearings business and supporting the full client lifecycle from business development through to client success.
• This role combines strategic account management, business development and marketing collaboration to grow our regional footprint, deepen client relationships and support operational excellence across the MEA region.
• **What you'll be doing **
• **Client Relationship Management & Business Development **
• - Managing and developing key client relationships and strategic partnerships across the MEA region.
• - Leading strategic account planning and outreach activities, including the creation and ongoing management of the quarterly MEA Account List.
• - Identifying and pursuing upcoming hearings and opportunities to grow pipeline activity, while developing market intelligence on firm activity, trends and regional developments.
• - Serve as a visible and trusted face for the company across events, conferences, webinars, panels, round tables and industry associations.
• - Identify leads and adoption or expansion opportunities for our subscription (Cases) business.
• **Client Success & Team Management **
• - Overseeing client success activities from the post-quotation stage through to the hearing, working closely with other operational teams to ensure a high level of client satisfaction throughout the post-business development client lifecycle.
• - Work closely alongside the Commercial Operations Associate.
• - Support the Head of Client Success in relation to regional activities including feedback meetings.
• **Marketing & Events **
• - Working with the Marketing team to plan and execute quarterly marketing campaigns and regional initiatives, including projects relating to inconsistencies, DIAC partnerships, venue consultancy and hybrid hearing capabilities.
• - 'Owning' and advising on the MEA BD Budget expenditure (monthly).
• - Working with the Marketing team to organise and deliver regional events, including Dubai Arbitration Week, Riyadh Disputes Week and other ad hoc client events.
• - Collaborating with the Marketing team to strategically plan regional content delivery, such as the MEA quarterly newsletter and contributions to global and regional campaigns and initiatives.
• **Projects & Reporting **
• - Leading and coordinating regional ad hoc projects on a cross-functional basis, including initiatives such as the move to the ADGM office.
• - Owning and maintaining Salesforce and Power BI reporting, including ensuring robust and consistent Salesforce data management and hygiene practices.
• - Monitor KPIs and support the Director of AI and Market Development with reporting.

Market Development Associate – MEA

Account Executive

• Research and prioritize target accounts to identify key decision-makers and expand our CRM with high-quality prospects
• Execute multi-channel outbound prospecting (email, phone, social, events) to generate new pipeline opportunities
• Personalize outreach at scale to drive higher engagement, response rates, and meeting conversion
• Partner closely with Sales and Marketing to align on campaigns, messaging, and account strategies that improve results
• Qualify inbound and outbound prospects by assessing needs, budget, timeline, and overall fit
• Schedule and support discovery meetings and product demos in collaboration with Account Executives
• Own and consistently exceed pipeline generation targets through disciplined activity and strong follow-through
• Maintain accurate and up-to-date CRM data, including contacts, activities, and opportunity progression
• Continuously test and optimize outreach strategies, including messaging, cadences, and tools
• Stay informed on legal industry trends, competitors, and market dynamics to sharpen positioning and conversations
• Develop deep product expertise, clearly articulating value across the litigation lifecycle
• Demonstrate strong personal accountability in daily activity, follow-ups, and pipeline creation
• Adopt and leverage the sales tech stack effectively, partnering with Marketing and RevOps to improve processes and performance

Inside Sales Representative

• Build and own a pipeline of new business opportunities across top 50 UK law firms and targeted EMEA accounts, from first outreach through to close.
• Proactively prospect and cold contact senior stakeholders including partners, heads of disputes, litigation support directors, and innovation leads.
• Lead consultative enterprise sales cycles, conducting thorough discovery, tailoring the Opus 2 value proposition to each firms strategic priorities and workflow.
• Develop a deep understanding of the legal technology landscape and each target firms competitive environment to position Opus 2 effectively.
• Translate discovery insights into clear, compelling commercial proposals anchored to each clients objectives and case needs.
• Maintain deal momentum through disciplined pipeline management, defined next steps, and proactive multi-stakeholder engagement.
• Achieve and exceed defined sales targets and quota on a monthly, quarterly, and annual basis.
• Collaborate with Solutions Consulting, Customer Success, Marketing, and Hearings teams to progress and win opportunities.
• Maintain a rigorous and accurate pipeline in Salesforce, including opportunity status, forecast amounts, and projected close dates.
• Represent Opus 2 at client meetings, industry events, and marketing initiatives to build profile and source new opportunities.
• Feed client and prospect insights back into product development, marketing, and sales strategy.

QA Engineer

• Lead complex, often ambiguous quality work across teams. Discovery, risk analysis, test design, automation strategy, exploratory passes, and the production signal that tells you whether you got it right. You're not the squad's tester; you're the person who makes the squad better at being its own tester.
• Shape quality approaches that squads can adopt. What gets unit tested, what gets API tested, what gets UI tested, what gets exploratory time, what gets watched in production. You coach squads through those calls and harvest what works so other teams can pick it up.
• Identify tooling gaps and close them. Where teams keep tripping over the same problem (missing test data, slow feedback, unreliable environments, no good way to test a new kind of feature), you spot it, frame the work, and either lead it or hand it off in a state someone else can run with.
• Partner with Product and Design. Run 3 Amigos and Example Mapping. Translate user needs into well-defined acceptance criteria. Call quality and risk trade-offs early. Keep the roadmap honest about what's feasible to ship with confidence.
• Raise the bar on the team around you, and beyond. Thoughtful code and test review, pairing where it helps, mentoring mid-level and junior QEs and developers. The kind of "shows the team what good looks like" presence that compounds over time and gets noticed across squads beyond your own.
• Own automation strategy and CI/CD signal. Where tests run, how fast they run, how reliable they are, what they're telling us, what we do when they fail. Flakiness and noise are problems you fix rather than work around.
• Champion continuous quality. Shift left through workshop facilitation and specification refinement; shift right through production data, escaped-defect analysis, and feedback loops that change what we test next.
• Use AI to raise quality, speed, and productivity. You don't need to be an ML researcher, but you should be using AI tools well across the SDLC: in test design and triage, in exploratory prompts, and in helping the squad adopt them safely. You should also be sharpening your thinking on how to test GenAI features themselves.
• Help shape engineering and quality strategy with Tech Leads, Engineering Managers, and the Head of Quality Engineering. Automation foundations, performance and non-functional approach, escaped-issue triage, how we measure quality, where we invest, and how the QE enablement function operates as we scale it.

Senior Quality Engineer

Full-stack Engineer

• You've found your footing. You can build features end-to-end with timely guidance, you're starting to see how the bigger systems fit together, and you're getting a feel for which technical choices will hold up. That's the moment we want you in. You'll join a squad doing real engineering on a platform that legal teams across the world rely on, and the AI shift in software is something you'll be living and shaping, not just reading about.
• You can grow toward Senior and beyond. Internal progression is the default at Opus 2, and we hire externally only when there's no internal alternative.
• What you'll do
• - **Deliver well-scoped features end-to-end.** Small to mid-size pieces of work with timely guidance. You break down tasks, ship in slices, and see them land for users.
• - **Partner with Product and Design.** Translate intent into pragmatic, well-scoped technical work. Ask the questions that surface tradeoffs early.
• - **Pull others up while you grow.** Help juniors. Review their code well. The mentoring habit starts here, not at senior.
• - **Use AI tools well across the SDLC.** Daily workflow, exploration, knowledge-sharing. Bring back what you find to the team.
• - **Improve the system.** Documentation that was missing, a flaky test, observability you wish you'd had. You leave things better than you found them.

Software Engineer

• Lead initiatives that span teams or systems. Domain-level work that's large, ambiguous, and business-critical. You break it into actionable pieces and mobilise teams to deliver.
• Set technical direction across teams. Architecture, technology choices, system shape. You make calls that hold up over years and explain them so others can carry them forward.
• Resolve systemic issues. The recurring incidents, the duplication, the integration cracks. The things that affect multiple teams and that no single team owns alone.
• Coach senior engineers into broader contributors. The next generation of staff engineers grows because you invest in them.
• Champion pragmatic engineering across the organisation. Simple, testable, data informed. You set the standard for how decisions get made, not just what gets built.
• Shape how we adopt AI. In product, in tooling, in how teams work. You make the calls that turn fast change into capability rather than chaos.

Staff Software Engineer

• Lead complex, often ambiguous features and projects end-to-end. Discovery, breakdown, shipping in slices, and seeing it land for customers.
• Partner with Product and Design to translate user needs into pragmatic, well-scoped technical work. Call tradeoffs early. Keep the roadmap honest about what's feasible.
• Raise the bar on the team around you, and beyond. Thoughtful code review, pairing where it helps, mentoring mid-level and junior engineers.
• Own quality and operability. CI/CD, test automation, observability, post-incident learning. Part of the work, not someone else's job.
• Make architectural and tech-stack calls that hold up. Favour maintainable, scalable, simple solutions over clever ones.
• Use AI to raise quality, speed, and productivity. You don't need to be an ML researcher, but you should be using AI tools well across the SDLC.
• Help shape engineering strategy with Tech Leads and Engineering Managers.

Senior Software Engineer

• Build foundational skills on real production work. Well-defined tasks with senior engineers supervising. The work is small in scope but real, and your code ships and serves customers.
• Learn the craft deliberately. Code review feedback, pairing, documentation, tests. These are the fundamentals that compound, and we protect time for them.
• Use the tools well. Source control, your dev environment, CI, observability, and AI tooling, which we treat as part of the workflow. Try things and bring back what you find.
• Communicate clearly. Tell your team what you're working on, why, how it's going, and where you're stuck. Asking for help is part of the job.
• Improve the docs. Whenever something tripped you up, write the explanation that would have helped. The codebase improves, and so do you.