Key details
Job Description
The eDiscovery Specialist is responsible for assisting attorneys and client teams by providing technical support throughout the litigation life cycle. This position acts as a technical liaison between attorneys and clients on electronic discovery matters. This position requires an understanding of legal practices, the Electronic Discovery Reference Model (EDRM), and Nixon Peabody’s business direction. A hybrid work schedule is available for this position. A career at Nixon Peabody is the opportunity to do work that matters. It’s the chance to use your knowledge to shape what’s ahead. To share, to innovate, to learn at a firm that taps the power of collective thinking.We’ve created a dynamic, energizing environment that promotes success for our clients and each other. We offer fast growth, connectedness and training in business as well as law. And our rigorous standards assure you are part of a diverse team of top talent at every turn.If you’re someone who’s looking toward the future, we’d love to hear from you.Location: Boston, MAResponsibilities: Work with firm attorneys and client’s IT department to execute plans for the preservation, collection, review and production of potentially relevant electronic data.Establish and manage discovery databases for the review, analysis, and production of electronic data.Conduct non-forensic collections of electronic data.Coordinate third-party vendors providing services such as paper document scanning, backup tape restoration, forensic collection/analysis and collection of web-hosted data repositories.Provide tactical support of all legal applications.Conducting training/orientation to attorneys and paralegals related to the firm’s current legal applications.Troubleshooting database errors in Relativity.Ability to meet or exceed billable hour requirement.
Audit details(provenance, verification trail, raw fields)
Core fields
nixon-peabody:lawcruit-4684Provenance
nixonpeabodyVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
