Bradley Lehman * Technical Writer
Dayton VA 22821 (not able to relocate)
540-879-3576 (h), 540-405-9686 (m) * bpl@umich.edu
Seeking a 3/4 to full time position, remote (telecommuting)
This resume is current as of 17 June 2019. * Source: http://www-personal.umich.edu/~bpl/resume-w.html
The full range of technical writing: documentation, spec writing, prototyping, research, testing, product design:
27 years of technical background in IVR industry, SQL applications, and self-service user interfaces.
I am a generalist who can pick up anything quickly: unfamiliar topics, new tools.
There are millions of things I don't know, but I trust and value other people's expertise as I learn and integrate the material. I boil down whatever the subject matter is into plain and well-organized language, so all the stakeholders in a project can understand what they need to.
Proficient user of MS Office365 and all the previous versions, plus MS Visio, LibreOffice Draw, yEd graph creator, and proprietary design tools. Audio editing for podcasts and speech modules. Have access to university libraries to research assigned topics.
Other computer and business skills aiding design and project delivery:
Asking the important questions to help clients identify and clarify their firm requirements. Writing and revising project specs with clear version control. Managing expectations to prevent scope creep. Clear paper trails of the stakeholders' agreements. Facilitation of team discussions.
Non-computer skills and interests: Harpsichord performance, organ, clavichord, piano, classical recording production,
music arrangement and editing, composition,
basso continuo improvisation, tuning harpsichords by ear.
Discovered a tuning method for Bach's music,
and wrote internationally-known papers about it.
Staff writer for a bimonthly journal
reviewing classical music recordings (more than 250 published reviews), to exercise my
public writing skills.
Conversational in Spanish and German, and able to read French. 1/4 time church organist.
Objective
Role: As a technical writer I ask probing questions on things I don't know, and then I work and rework the material (facilitating discussions) until all the stakeholders are satisfied. I leave every piece of documentation, specifications, or Help in a better state than it was: better clarity, completeness, and usability. I make sure that all the important problems and questions get brought to the table and dealt with, whether or not somebody else thought of them.
In short, I catalyze the entire team's best work and effective messaging. My role is to bridge the gaps between technical material and people's understanding. I bring 50+ years of interdisciplinary insights and experience, plus diligence in getting it right. I have strong intuitive sense when something is wrong.
My objective is to find another professional position of 3/4 to full time where I can do that: working on something that is important, socially responsible, and that was not getting done well enough (or at all) without me.
Location: I live in Dayton Virginia, about 125 miles from either Washington DC or Richmond, and 65 miles from Charlottesville or Winchester. I have an office in my house. We can work by phone or video discussions, and e-mailing designs and files. Occasional in-person meetings are OK if there is not much travel.
My recent titles:
- Senior Systems Architect (with emphasis on research and technical writing)
- Senior Client Services Consultant (IVR industry)
- Organist
Experience and education
Details of my education and work history are in a 2017 MS Word version of my IVR resume. They are also in my LinkedIn profile, https://www.linkedin.com/in/bradleylehman/
- Education (1982-1994): University of Michigan, Goshen College.
- Employers (1986-): IKON (2018-19), Genesys & Angel.com (2008-17), Tier Technologies & EPOS (1999-2008), CMDS (1996-9), University of Michigan, Goshen College. I was an IVR specialist for all of the companies from CMDS to Genesys, 1999-2017. For IKON (2018-19 layoff) I designed business logic for web-based applications and did technical writing (including assigned subject-matter research).