JobCannon
Alla kompetenser

RFC Writing Requests

⬢ NIVÅ 2Mjuka färdigheter
Medel
Lönepåverkan
1 månader
Tid att lära sig
Lätt
Svårighetsgrad
—
Karriärer
I korthet

RFCs are structured design documents proposing technical decisions and soliciting feedback. Engineering leads, architects, and senior engineers use RFCs to drive consensus, document decisions, and prevent rework. Improves decision quality by 30–50% in organizations that adopt them. Typically 1–2 weeks to competency. Sits alongside technical leadership, system design, and architectural thinking.

Vad är RFC Writing Requests

An RFC (Request for Comments) is a structured technical proposal document designed to drive consensus and document decisions before implementation. Originating in internet standards (IETF RFCs), the RFC format has become standard in many tech organizations for proposing architecture changes, new services, API designs, and significant refactors. Well-written RFCs improve decision quality, reduce rework, and create organizational memory of the reasoning behind technical choices. Strong RFC writing separates good engineers from exceptional technical leaders. RFCs enable you to propose large-scale changes, gain buy-in from colleagues, and influence architecture. Organizations that use RFCs report 30–50% reduction in design rework and faster onboarding. RFC expertise is particularly valued in senior and staff engineering roles, where shaping technical direction is a key responsibility.

🔧 VERKTYG & EKOSYSTEM
Markdown / Google DocsGit / GitHub IssuesConfluence / NotionDiagram Tools (Miro, Lucidchart)Presentation Tools

💰 Lön per region

OmrådeNybörjareMidErfaren
USA$70k$120k$180k
UK£42k£75k£115k
EU€45k€80k€125k
CANADAC$65kC$110kC$165k

❓ Vanliga frågor

What is an RFC?
RFC (Request for Comments) is a formal proposal for a technical decision. It documents the problem, proposed solution, alternatives, tradeoffs, and asks for feedback before implementation. RFCs prevent costly design decisions made in isolation.
When should I write an RFC?
RFCs are for decisions with long-term impact: architecture changes, new services, significant refactors, API changes. Quick bug fixes or minor updates don't need RFCs. Threshold: decisions affecting >1 person or lasting >3 months.
What should an RFC include?
Title, motivation (problem statement), proposed solution with detailed design, alternatives considered, tradeoffs, implementation plan, risks, and success metrics. Keep RFCs 2–5 pages; longer docs indicate scope problems.
How long does RFC review take?
Typically 3–5 business days for feedback phase, then 1 week for revisions and consensus. Large, controversial RFCs may take 2–4 weeks. Set clear review timelines upfront.
Can an RFC be rejected?
Yes, absolute. RFCs are proposals, not guarantees. Feedback may invalidate assumptions or propose superior alternatives. Rejection is learning; don't take it personally. Iterate and resubmit if appropriate.

Osäker på om den här kompetensen passar dig?

Gör Career Match — vi föreslår rätt spår för dig.

Hitta mina bäst passande kompetenser →

Hitta din ideala karriärväg

Kompetensbaserad matchning mot 2 521 karriärer. Gratis, ~3 minuter.

Gör Karriärmatchningen — gratis →