A job description that blends two fields — say, 90% data engineering and 10% product management — forces a decision: do you cram everything into one dense paragraph or risk ignoring the 10% entirely? Neither works. Cramming buries your core qualifications; ignoring the 10% makes you look disinterested in a key growth area.
A 90/10 split is common in hybrid roles like technical product marketing, clinical research operations, or design-engineering hybrids. Hiring managers are evaluating two separate filters: Can this person do the main job today? And will this person stick around to develop the secondary work tomorrow? Your letter must address both, but in the right order.
Open with a sentence that states your primary field, then immediately connect it to the core 90% requirement. Example: "As a data engineer who has built scalable pipelines for three SaaS platforms, I was drawn to this role because the first priority is standardizing your existing data lake." That lands the reader in the right context without hesitation.
Use one or two specific achievements from your primary field. If the job requires Python and SQL, don't list them — show them in a result: "I reduced ad-hoc query time by 60% by refactoring a legacy ETL pipeline in Python and optimizing six stored procedures." Keep this paragraph entirely focused on the 90% skill set.
This is the only place you mention the secondary field. Frame it as a value add, not as an awkward extra. Example: "While delivering that pipeline, I also worked with product teams to prioritize two feature requests based on query cost — a skill that maps to the product-ops component of this role." If your experience in the 10% is thin, mention a short project, a course, or a stretch assignment. Do not apologize or overexplain.
Briefly restate that the role sits at the intersection of both fields, and that you are excited to bring your primary expertise while growing the secondary area.
Here is a real-world rewrite from a user who applied for a role that was 90% technical writing and 10% community management.
Before (generic): "I am a technical writer with experience in documentation and also some community management work. I ran a forum for users and helped answer questions. I think this would be useful for the role."
After (90/10 optimized): "As a technical writer who reduced support tickets by 25% by rewriting the API onboarding guide (90% match), I would bring immediate clarity to your developer docs. Separately, I produced 12 video tutorials last year that tripled forum engagement — a direct fit for the community component of this role (10% match). I view the community piece not as a side task but as the best channel to validate what users actually need documented next."
Notice: the core skill comes first and includes a metric; the secondary skill has its own small metric and is framed as strategic insight, not as a hobby. The rewrite took 30 seconds in PrismResume, a free checker that highlights weak phrasing and suggests tighter alternatives.
Most applicant tracking systems (ATS) read plain text or .docx reliably; .pdf can introduce parsing errors if the PDF is not saved as text-searchable. Use these formatting rules:
These rules are widely documented across career sites and are safe for any major ATS in 2026.
If the job description is ambiguous — say 60/40 rather than 90/10 — calculate based on required qualifications versus preferred qualifications. The required section is your 90% anchor. If even that is fuzzy, look at job titles: a "Product Manager" role that lists 40% technical architect work is still a PM role. Lead with product management, then show the technical depth.
Wondering how your own resume holds up?
Check it free — no sign-upLearn how to structure your resume after a demotion or role reduction. Use functional format, reframe responsibilities, and focus on impact to turn a career setback into a story of resilience.
Learn how to structure a resume for a lateral move into a new function: translate past achievements into the target role's language, use a hybrid skills section, and avoid common pitfalls like…
Learn how to write a resume when you were the only person doing your job. Lead with outcome verbs and solo metrics that prove impact, not isolation.
Loading…