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 25 · sorted by freshness
processes. - Develop solutions to strengthen the security in and around applications. - Leverage application metrics to inform technical and business decisions. - Analyze industry specific requirements/technologies and p…
newsletter lands in inboxes every week — and it needs to be the kind of email people actually look forward to opening. As our Newsletter Writer, you'll research, write, and produce a weekly newsletter that keeps our audi…
existed, and we hire people who actually get it. THE ROLE Words drive traffic — and traffic drives everything. As an SEO Content Writer at NoGigiddy, you'll create articles, guides, and landing pages that rank on Google…
DARCARS of Baltimore is now seeking an Automotive Service Advisor / Writer As the Automotive Service Advisor / Writer you are responsible for presenting, consulting and selling automotive warranty products and repair ser…
We are looking for an experienced Medical Grant Writer (Freelance, Remote) to support a nonprofit organization dedicated to improving the lives of individuals and families affected by Barth syndrome, an ultra-rare diseas…
meet AGS standards for instructional design, brand, accessibility, quality, and content development. ~ Provide design feedback, technical guidance, and mentoring to instructional designers and learning partners. ~ Explor…
support analytics and operational use cases. The engineer will contribute across the software development lifecycle including technical design coding testing deployment and production support with a strong emphasis on Sn…
Job Title: Content Manager Posting Date: November 2026 Job Department: Marketing Schedule: Full Time Job Type: On-site/Hybrid Location: Candler 111 Market Pl Suite 800 Baltimore MD 21202 JOB SUMMARY: The National Aquariu…
Senior Technical Writer Employment Type: Full-Time, Experienced Department: Technology Support CGS is seeking an experienced Senior Technical Writer to provide consultative, analytical, and documentation support for a la…
layers. The developer will translate business and user needs into secure reliable and accessible solutions while contributing across technical design implementation testing deployment and production support. RESPONSIBILI…
mentorship and coaching of more junior developers. Strong communications skills are required. The customer is very mission-focused technically knowledgeable and provides excellent support. This is a challenging stimulati…
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.