Legal Counsel Interview Questions

I use a triage system based on two factors: deadline and risk exposure. Anything with a court date, regulatory filing deadline, or an imminent contract signing goes to the top regardless of which team is asking. Below that I assess potential liability: a contract clause that could expose the organisation to uncapped damages ranks above a policy review that can wait two weeks. I keep a live priority list updated at the start of each day and share it weekly with my manager so there are no surprises. I also batch similar work where possible: reviewing three NDAs in a row is more efficient than switching between contract review, regulatory advice, and an employment matter. When volume genuinely exceeds capacity, I flag it early rather than letting timelines slip silently. Under-resourcing a legal team is a risk decision that belongs with leadership.

I translate legal risk into business impact. Instead of citing the clause and the statute, I tell the stakeholder: if this deal goes ahead as drafted, the worst-case outcome is X, the probability is roughly Y, and the cost to fix it today is Z. That framing gives them what they need to make an informed decision. I avoid jargon and never use risk as a veto without giving options. In most situations there is a path forward: amended language, a warranty, an indemnity cap, a pricing adjustment. My job is to map those options and their trade-offs, not to block progress. If a stakeholder proceeds after I have explained the risk clearly and they have accepted it in writing, that is a business decision and I document it accordingly. What I will not do is stay silent about a material risk to avoid an uncomfortable conversation.

I focus on the risk profile of each clause rather than trying to win every point. When the counterparty has more leverage, I identify the three or four provisions that would genuinely damage the organisation if conceded: liability caps, indemnities, data ownership, termination for convenience. I hold firm on those and give ground more readily on drafting preferences and low-risk positions. I look for creative trade-offs: if they will not move on liability, perhaps they will accept a shorter contract term, which reduces exposure through time rather than through capped damages. I research the counterparty's standard positions before negotiations start so I am not surprised. And I keep the business stakeholder briefed throughout so they can reinforce key positions in their own commercial conversations.

During due diligence for an acquisition, I reviewed the target's supplier contracts and noticed that several key agreements contained change-of-control clauses allowing the supplier to terminate immediately on deal close. The deal team had focused on financial statements and customer contracts and had not flagged these provisions. I raised it immediately with the lead partner and the integration team. We contacted the three most critical suppliers before signing to negotiate waivers, which two granted. The third required a renegotiation of commercial terms as a condition. That added two weeks to the timeline but avoided what could have been a serious operational disruption post-closing. The lesson was that supplier contracts often receive less attention than customer contracts in due diligence, which is precisely where risk tends to hide.

A commercial team wanted to launch a campaign offering a guaranteed return on a financial product. Marketing had approved the creative and a launch date was set. When I reviewed the materials, the language would have required us to be registered as an investment adviser under applicable regulations, which we were not. I flagged this to the CMO and CFO in writing, explained the regulatory exposure in plain terms, and proposed two alternatives: a compliant version with adjusted language, or a six-week delay to obtain the necessary registration. I was direct that launching as planned was not an option I could support. The team pushed back initially because of the timeline, but once they understood that the breach could result in enforcement action and fines, they accepted the compliant version. The campaign launched three weeks later.

On a Friday afternoon, a business development director told me a partnership contract needed to be signed by Monday morning or the counterparty would walk. I had not seen the contract. I cleared my weekend plans and started reading immediately. The document was 60 pages with several unusual provisions, including a broad IP assignment clause that would have transferred ownership of certain product developments to the counterparty. I prepared a summary of five issues that needed resolution before signing, with proposed alternative language for each, and sent it to both sides at 9pm. We negotiated by email through Saturday. By Sunday afternoon three issues were resolved and two remained. The director made a commercial decision to accept the residual risk on those two points, documented in writing. The contract signed Monday morning. Not every legal review can be thorough, but every risk decision must be documented.

I maintain standing alerts through legal databases and regulatory body publications for the jurisdictions and sectors I cover. Each week I review a curated digest from two or three sources rather than trying to read everything. For major changes I go deeper: I read the primary legislation and guidance notes, not just secondary commentary, because summaries can miss nuances that matter in practice. I attend two or three practitioner roundtables a year where regulators and industry counsel discuss forthcoming changes. When a change is material to the business, I prepare a one-page briefing for the relevant team rather than waiting for them to ask. The goal is to surface regulatory change before it creates a problem. I also cross-check with external counsel quarterly to ensure my reading of the regulatory landscape matches theirs.

I treat data protection as a product design constraint, not a legal review step at the end of development. That means being involved in privacy impact assessments before features ship. My framework starts with data minimisation: what do we actually need, for how long, and for what purpose? I work with engineering and product to map data flows so we have an accurate picture of what we collect, where it goes, and who has access. For consent flows I review the language against regulatory guidance to ensure it is specific and unambiguous. I maintain a record of processing activities and update it when new features launch. For third-party processors I review their data processing agreements and, for higher-risk processors, ask for their technical and organisational measures. The hardest part is keeping documentation current as the product evolves, which requires an ongoing relationship with the product team.

I start by reading the entire document before making a single comment. Jumping straight to redlines means missing how provisions interact. After a first read I have a clear picture of the deal structure, the risk allocation, and the provisions that need attention. I then work through the document in three passes. The first focuses on high-risk provisions: liability cap, indemnities, IP ownership, termination rights, and exclusivity. The second addresses drafting ambiguity: clauses that are vague or internally inconsistent. The third checks consistency: defined terms used correctly, cross-references that actually work, schedules that match the body of the agreement. I produce a summary of issues with a recommended position for each, flagging which are must-haves and which are negotiating positions. That summary is what I share with the business stakeholder, not a track-changes document they cannot interpret.