Software Engineer & Developer

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Explain a technical decision in a way peers can learn from. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Write a post about one architecture or tooling decision. Structure: context, options considered, trade-offs, final decision, and outcome. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Share open-source progress and invite contributors. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Generate a post that shares an open-source improvement, why it matters, and specific ways developers can contribute. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Reply to recruiter outreach with clarity and boundaries. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Create reply templates for recruiter DMs: interested, maybe later, and not a fit. Include preference on role scope and tech stack. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Generate 5 post angles that build authority without sounding salesy. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Act as a LinkedIn® strategist for a Software Engineer & Developer. Create 5 post angles using this focus: Network with fellow developers, find opportunities, and share technical knowledge. Each angle must include: hook, core insight, and CTA to invite thoughtful comments. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Turn one real-world experience into an engaging story post. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: I am a Software Engineer & Developer. Turn my rough bullet notes into a LinkedIn® post with this format: setup, tension, turning point, takeaway, CTA. Keep examples relevant to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Package one result into a concise case study post. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Write a case study style LinkedIn® post for a Software Engineer & Developer. Structure: client context, challenge, action steps, measurable outcome, key lesson. Context to anchor: Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Turn any post into a thoughtful comment in my voice. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: I am a Software Engineer & Developer. I want to comment on a LinkedIn® post in a way that feels useful and specific. Build a 3-part comment formula (acknowledge, insight, follow-up question) aligned with this context: Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Create response variants for common comment types. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Create a comment-reply matrix for a Software Engineer & Developer. Give replies for: agreement, skepticism, question, objection, and praise. Keep every reply practical and tied to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Write short connection requests that feel genuine. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Write 6 personalized connection request messages for a Software Engineer & Developer. Keep each under 280 characters and avoid generic intros. Tie each variant to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Draft a short 3-message sequence to start relevant conversations. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Write a 3-step LinkedIn® DM sequence for a Software Engineer & Developer. Keep it low-pressure and personalized. Goal: open a genuine conversation connected to Network with fellow developers, find opportunities, and share technical knowledge. Include Message 1, follow-up, and value-add nudge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Write follow-up messages that re-open stalled conversations. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Write 3 follow-up LinkedIn® messages for a Software Engineer & Developer to revive inactive conversations. Tone: helpful, concise, confident. Each follow-up should reference a prior discussion and connect to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Handle common objections without sounding defensive. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Generate objection-handling snippets for a Software Engineer & Developer. Include responses for "too expensive", "not now", "already working with someone", and "unclear ROI". Keep messaging relevant to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Create a 6-slide carousel outline from one core insight. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Create a 6-slide LinkedIn® carousel outline for Software Engineer & Developer. Start from one core idea related to Network with fellow developers, find opportunities, and share technical knowledge. Include slide title + 2 concise bullets per slide and a final CTA slide. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Produce a full week of content angles in one pass. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Create a 7-day LinkedIn® content sprint for a Software Engineer & Developer. For each day provide: format, hook, 3 bullet talking points, CTA, and suggested engagement action. Anchor topics to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Upgrade headline + about section messaging. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Rewrite my LinkedIn® headline and about section as a Software Engineer & Developer. Keep it clear, human, and outcome-focused. Ensure it reflects this positioning: Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.

Role: You are an expert LinkedIn® writing copilot for a Software Engineer & Developer. Outcome: Draft a short collaboration pitch for potential partners. Context: Network with fellow developers, find opportunities, and share technical knowledge Task: Draft a collaboration pitch message for a Software Engineer & Developer. Include context, why this partnership fits, and a simple next step. Keep it specific to Network with fellow developers, find opportunities, and share technical knowledge. Constraints: - Keep the writing concrete, human, and specific (no generic AI phrasing). - Prefer short paragraphs and clear language. - Include at least one practical detail that makes the content believable. Output format: 1) Final draft 2) 3 hook variants 3) 2 CTA variants Self-check before final answer: - Verify the draft matches the outcome and context. - Verify tone sounds natural and not templated. - Verify there are no vague claims without context.