closely with modeling and simulation engineers, embedded developers, hardware engineers, and systems engineers to translate complex technical workflows into usable software. The ideal candidate combines strong modern fro…
Technical Writer jobs in Baltimore, MD
Technical writers turn complex products into documentation people can actually use — API references, user guides, and internal docs — working closely with engineers to get the details right.
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
Open technical writer roles
12 shown of 17 · sorted by freshness
do not currently possess this level of clearance. ---------- Telework: None Basic Requirements: ~ Bachelor’s degree in a technical field. ~8 years of applicable professional experience. Job Description: ~ As part of the…
integrate, transform, and operationalize enterprise dataCollaborating with cross-functional teams to define requirements, resolve technical issues, and deliver scalable solutionsApplying DevOps and statistical programmin…
seeking a highly motivated, detail-oriented, and certified Proposal Writer Analyst to join our team in a remote, full-time capacity.... ...pipeline opportunities, track competitor positioning, synthesize technical inputs…
stronger. For more information, visit or follow MMS on LinkedIn . Responsibilities Under minimal supervision, the Medical Writer will critically evaluate, analyze, and interpret the medical literature to select primary r…
solutions. You will closely support the client’s Training Division to meet a continuously changing security environment, utilizing your technical expertise to seamlessly apply the ADDIE model across a variety of instruct…
integration performance to ensure seamless and reliable operation. Mentorship & Guidance: Mentor junior developers and provide technical guidance to the team (as needed). Continuous Improvement: Stay up to date with the…
Technical Editor and Writer 3 Specialized IETM Technical Writer Our client is seeking a specialized IETM Technical Writer. The successful candidates will join our high-performing team in developing technical manual conte…
communications across a variety of ongoing initiatives, including regulatory and compliance-driven updates. The ideal candidate is a strong writer who can take an established brief or assignment and turn it into an effec…
Kratos Defense & Rocket Support Services is seeking a Proposal/ Technical Writer to support our team. The Proposal/Technical Writer will support the Business Development and Program Management teams in drafting proposal…
implementation hypercare. Investigate and resolve data defects, integration issues, and production support incidents. Develop technical documentation including data mappings, transformation logic, and validation procedur…
experience What You'll Be Part Of We are seeking a UX Strategic Writer and Content Designer to shape and drive cohesive product... ...multiple platforms and touchpoints. Your work will simplify complex technical concepts…
What technical writers earn in Baltimore
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $28–$38 | $58k–$79k |
| Mid level | $38–$50 | $79k–$105k |
| Senior | $50–$65 | $103k–$136k |
Adjusted for the Baltimore market from national ranges.
What employers ask for
The skills these listings keep naming
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Walk me through your process for documenting a feature you know nothing about.
Show the sequence: use the product yourself, interview the engineers, draft, and validate with real users or support tickets. Trying the product firsthand is the key beat.
How do you decide what not to include in documentation?
Anchor on audience and task: what does this reader need to succeed right now. Cutting is the craft — show you treat concision as a feature.
An engineer gives you inaccurate or incomplete information. How do you handle it?
Verify against the product, ask precise follow-ups, and build review loops into your process. Show persistence without friction.
How do you keep documentation from going stale?
Talk about docs-as-code tied to release workflows, ownership models, feedback channels, and auditing high-traffic pages. Staleness is the industry's chronic disease — show a system.
How do you measure whether documentation is working?
Page analytics, search terms, support-ticket deflection, and user feedback. Connecting docs to reduced support load is the strongest business case.
Tell me about a doc set you restructured. What drove the changes?
Describe the user problem — findability, task mismatch — and the information architecture you moved to. Evidence of user thinking beats aesthetic preference.
Resume tips that move the needle
For technical writers specifically — generic advice costs you here
Link writing samples matched to the job: API docs for API roles, user guides for product roles — the portfolio is the interview.
Quantify impact where possible: support tickets deflected, onboarding time cut, docs traffic and satisfaction scores.
List your toolchain (Markdown, Git, Docusaurus, OpenAPI) because docs-as-code fluency is now a standard screen.
Show technical depth honestly — languages you can read, APIs you have called yourself — since it defines which roles fit.
Mention style guide ownership or editing responsibilities; they signal you raise a whole team's quality, not just your own pages.
Where this role goes
Typical progression
Applying for technical writer jobs in Baltimore?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.