Opus 2

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.

Junior Software Engineer

Performance Marketing

• Grow new lead and sales qualified opportunity volume through the execution of an integrated marketing plan for the North America software business.
• Organize and lead execution of an outbound marketing plan that drives performance and meets goals, employing a variety of marketing strategies and vehicles to engage our target account list.
• Lead ABM execution to ensure coverage across target accounts, aligning with sales.
• Collaborate with content and design to develop engaging content relevant to the target audience.
• Lead team in planning and scheduling marketing campaigns with a variety of tactics including trade shows, round tables, webinars, email, social, conferences, digital ads, content and other activities.
• Deploy marketing strategy to accelerate in-pipeline opportunities to customer conversion.
• Represent Opus 2 with industry agencies, associations and special interest groups.
• Monitor and report on marketing programs regularly to evaluate their efficiency and effectiveness.

Senior Quality Engineer

Software Engineer

Staff Software Engineer

Senior Software Engineer

Junior Software Engineer

Marketing Campaign Manager