Yes, an English Literature BA can lead to technical writing jobs in Minnesota with a plan. Swap 12–24 electives, add a minor or certificate, build a portfolio, and get internships.
Key variables for converting an English Literature BA
An English Literature BA converts to technical writing when five things align. These are targeted credits, a minor or certificate, portfolio artifacts, tool skills, and local internship experience.
Employers in Minnesota look for work products more than majors. The single most decisive factor is portfolio relevance.
Small steps add up to real career changes quickly.
Targeted credits and course swaps
Swapping 12–24 elective credits to technical-writing and tool courses raises hireability. This change is a 2024 recommendation. Keep core literature courses that show analysis and editing skills.
Add technical courses early so the portfolio starts in year three. Early projects make later internships easier to win.
A hireable portfolio should include four to six task-based artifacts with context cards and tool notes. Show Markdown, basic Git, a CMS or MadCap exposure, and basic HTML or DITA/XML overview.
Employers reject applicants who list only creative or academic writing samples. Hiring teams want task-based, audience-focused work.
Local internship and industry fit
A Minnesota internship gives domain knowledge employers value for regulated work. Target healthcare devices, medical software, manufacturing, or B2B software for internships.
Employers favor candidates who can show one employer-reviewed deliverable. That single deliverable often unlocks interviews.
Device and regulated-writing pathway
Converting a BA to device or clinical documentation needs extra domain focus and a practicum. Hiring teams at Medtronic and Mayo expect regulatory awareness and one technical sample tied to validation or procedures.
When those conditions are met, entry-level pay in regulated fields tends to be higher. The role pays more because of the added domain risk.
What regulated employers expect
Regulated employers want writing that maps to validation, traceability, and standard operating procedures. A sample procedural document should list test points, acceptance criteria, and revision control.
The error most frequent here is submitting an academic essay instead of a procedure with traceable steps.
Recommended curriculum additions for regulated writing
Add a course in technical editing and one in quality systems or regulatory writing when possible. Seek a practicum or internship in clinical or device documentation.
Consider a short certificate in regulatory writing or clinical documentation to boost credibility.
How to build domain credibility fast
Create one procedure or user-validation artifact during an internship. Label artifacts with audience, tools, and constraints so hiring managers can evaluate them quickly.
What most guides omit is the need to show how the document met a compliance or testing requirement.
Software and UX content pathway
For software roles, focus on API examples, quick-start guides, UX microcopy, and single-sourcing practices. Hiring teams expect at least one developer-facing or UX-focused artifact and some version-control familiarity.
Entry-level software-documentation offers in the Twin Cities reflect these skills when present.
Course and skills targets for software roles
Take an intro CS course to show technical literacy. Add a UX writing or content strategy elective if available.
Show Git or a public repository with Markdown-based docs.
Portfolio pieces for software jobs
Include an API example, a quick-start guide, and one UX microcopy set. Each piece must open with a three-line context card stating audience, role, and tools used.
Employers screen out portfolios lacking developer or UX artifacts.
Where Minnesota software jobs advertise
Look for openings at regional B2B firms, health-tech startups, and larger employers with developer tools. LinkedIn and company career pages list the most current openings for the Twin Cities.
The Society for Technical Communication keeps local chapters and events for networking. Society for Technical Communication.
Semester-by-semester retrofit plan
A semester plan that replaces 12–24 electives, schedules two summers for internships, and ends with a capstone portfolio reaches hireability within four years. The plan sequences technical courses early and builds project work and internships in years three and four.
This section gives semester-level swaps and deliverables.
Years 1–2: foundation and course swaps
Year 1 should preserve core literature requirements. Add Intro to Technical Writing (3 credits) and Public Speaking or Professional Communication (3 credits).
Year 2 should add Technical Editing (3 credits) and an Intro CS/HTML course (3 credits). These swaps total 12 credits in years one and two.
Years 3–4: specialization and internships
Year 3 should add UX writing or single-sourcing/DITA basics (3 credits). Add a tools lab for MadCap, CMS, or Git workshop for 1–3 credits.
Secure a summer internship that yields at least one employer-reviewed deliverable. Year 4 should include a capstone portfolio course or independent project and a final internship or practicum.
Capstone and portfolio deliverables
Capstone must produce four to six artifacts: quick-start, procedure, API or developer sample, edited longform, release notes, and a UX microcopy example. Each artifact must include a context card and a before/after edit when relevant.
The rubric below defines hire-ready thresholds.
Portfolio requirement: assemble 4–6 artifacts with context cards. Demonstrate at least two tools (Markdown and a CMS or Git). Meet 80/100 or higher on the five-criterion rubric to be considered hire-ready (2024 recommended standard).
Sample semester-by-semester roadmap (illustrative):
- Fall Year 1. Intro to Technical Writing (3 credits), Core Literature seminar, Public Speaking/Professional Communication (3 credits).
- deliverable: draft quick-start guide (1–2 pages) with a three-line context card and basic Markdown file.
- Spring Year 1. Composition elective, Elective swap to Intro CS/HTML (3 credits).
- deliverable: short procedure with numbered steps and basic version control note.
- Fall Year 2. Technical Editing (3 credits), single-sourcing/DITA overview (3 credits).
- deliverable: edited spec with before/after notes.
- Spring Year 2. Tools lab (MadCap/CMS/Git workshop, 1–2 credits), UX-writing elective.
- deliverable: UX microcopy set and a Git-tracked repo.
Summer between Years 2 and 3, get a local internship or practicum producing one employer-reviewed artifact. Years 3–4 repeat with higher project complexity and a final practicum emphasizing regulated documentation or software docs.
Common mistakes that make a Lit BA less hireable
The biggest mistake is assuming a literature degree alone qualifies one for technical-writing roles. That fails when targeted coursework or a portfolio are missing.
Another frequent error is submitting creative or academic samples instead of task-based deliverables such as procedures or API docs. Skipping local internships or industry-recognized certificates often blocks entry-level hireability.
Mistake: wrong sample types
Hiring managers screen for task completion and audience focus, not literary analysis. Submitting literary essays signals a skills mismatch and usually stops the process early.
Listing Microsoft Word only is weak for technical roles. Employers expect at least Markdown and some CMS or version-control exposure.
Many candidates lose calls because they lack basic Git or Markdown examples.
Hiring timing and expectations
Typical Twin Cities entry-level offers range $55,000 to $70,000 for candidates with portfolios and internships (2024 market ranges). The BLS median annual wage for technical writers was $78,060 in May 2022.
Target salaries vary by domain and employer; medical-device documentation tends to start higher.
BA vs BS decision table
| Criterion |
BA (English Lit) + Retrofit |
BS (Technical/Comp Sci) |
| Technical credits needed |
12–24 electives swapped |
24–36 required |
| CS/math prereqs |
Low to moderate (CS1 recommended) |
High (multiple CS/math courses) |
| Portfolio weight |
4–6 task artifacts required |
4–8 artifacts, more dev samples |
| Typical employer sectors |
Medtech, healthcare, publishing, software |
Software, engineering, dev tools |
| Time to first hire |
Often faster with cert + internship |
Longer but deeper technical fit |
| Good fit if... |
Prefers writing, will add targeted credits |
Enjoys coding and engineering contexts |
Portfolio checklist, sample pieces, and evaluation rubric
A competitive portfolio includes these artifacts and metadata. The hiring manager should find audience, role, tools, and one measurable result or constraint on each sample.
The rubric below scores clarity, audience fit, task completeness, tool use, and impact.
Include these samples:
- Quick-start/user guide (1–2 pages).
- Procedural step-by-step.
- API example or developer doc.
- Edited spec or longform with before/after edits.
- Release notes or changelog entry.
- UX microcopy set if applicable.
Each sample opens with a context card: audience, role, tools used, and one constraint or metric.
Show Markdown and a public repo or file export. Show familiarity with a CMS or MadCap Flare, basic HTML, and DITA/XML at an overview level.
One sample must show version control or change-tracking information.
Evaluation rubric
- Clarity (0–20)
- Audience match (0–20)
- Task completeness (0–20)
- Tool competence (0–20)
- Measured impact or constraint handling (0–20)
Score 80 or higher indicates a hire-ready portfolio.
This plan does not apply when the target job requires accredited STEM credentials, such as clinical trial protocol authorship or engineering design documentation that legally requires an engineering degree; those jobs need a different credential path and deeper domain training.
Schedule a transcript review with university career services to map the semester swaps below and identify internships that align with employer needs.
Concrete portfolio snippets and context cards (examples):
- Context card. Audience: field service technician.
- Role: author and editor.
- Tools: Markdown, Git, MadCap Flare.
- Constraint: 30-minute on-site repair window.
Artifact. Procedure excerpt: "Step 1: Power down device and record serial number in Maintenance Log. Step 2: Remove front bezel (Torx T10), note connector orientation. Step 3: Replace module A-3. Perform continuity check per Test Table 2. Acceptance: all LED indicators green for 60 seconds."
API documentation excerpt: "GET /v1/patients/{id} — Returns patient summary. Parameters: id (UUID). Success 200: {name, dob, status}. Sample curl: curl -H 'Authorization: Bearer ' 'https://api.example.com/v1/patients/123e4567-e89b-12d3-a456-426614174000'"
Before/after edit example (summary): Original sentence: "The user must reboot device sometimes." Edited: "Reboot the device after firmware update to apply configuration changes. Steps: 1. Save settings. 2. Reboot. 3. Confirm version via About screen."
Each snippet should include a one-line metric when available. Also include a note on tool evidence like a Git commit hash or exported Markdown file.
Frequently asked questions
Can an English major get hired as a technical writer?
Yes, an English major can get hired with targeted credits, a portfolio, and one internship. Employers evaluate samples and tools more than the major.
Follow this roadmap and candidates get interviews faster.
How long to become hire-ready from a BA baseline?
A focused retrofit reaches hire-ready status in four semesters with 12–24 elective swaps and two internships. A faster route is two semesters plus an intensive certificate and a summer internship.
Outcomes depend on internship quality.
What salary can a recent grad expect in the Twin Cities?
Entry offers in the Twin Cities commonly range $55,000 to $70,000 for candidates with portfolios and internships (2024 ranges). BLS reported a national median of $78,060 for technical writers in May 2022.
Local domain and employer size affect starting pay.
Are online certificates enough to get interviews?
Online certificates help only when they produce portfolio artifacts that show real work. Employers treat certificates as evidence of effort, not as a substitute for samples.
Certificates plus a strong portfolio lead to callbacks.
What if the student wants to work in medical documentation?
Then the student needs domain exposure, a practicum, and at least one regulatory-style artifact in the portfolio. Medical-device teams often expect validation, traceability, and controlled document practices.
Without those, entry-level hiring for regulated roles is unlikely.
What to do next
Map the 12–24 credits to your transcript, target a summer internship in year three, and build the six required portfolio artifacts during practicum. Pick a minor or certificate, enroll in Intro to Technical Writing, and apply to one internship each summer in Minnesota.
This sequence reduces labor-market risk and converts a liberal-arts BA into a practical, hireable technical-writing profile.
Which minors or certificates help most in technical writing
Technical communication, CS1, and UX or HCI minors give the largest hiring lift. Short certificates from Minnesota State or University of Minnesota extension help when paired with portfolio samples.
Employer-recognized workshops like MadCap or STC add practical signals.
