We’re hiring a premium English-speaking technical assistant to support a software engineer who moves fast, builds constantly, and has a classic “developer brain” (high output, lots of parallel ideas). Your job is to act as the external brain: capture ideas, organize them, create clarity, and keep execution moving—without needing hand-holding. You’ll live in Jira (and related tools), help break work into well-written tasks, keep priorities visible, and proactively handle the small technical and operational things that slow engineers down. You should genuinely enjoy tinkering: clicking around in tools, testing settings, reproducing bugs, documenting steps, and figuring out the “how” on technical problems. We encourage our team to utilize Ai, while verifying all output. What you’ll do (core responsibilities) • Translate voice notes / Teams messages / quick calls into clean Jira tickets (clear title, description, acceptance criteria, priority, dependencies). • Backlog grooming & sprint support: keep Jira organized, reduce clutter, archive/label appropriately, keep work flowing. • Clarify requirements: ask smart questions, identify missing info, define edge cases, and document assumptions. • Bug triage support: reproduce issues, collect logs/screenshots, write clean repro steps, confirm expected vs actual behavior. • Technical research & tinkering: investigate plugins, APIs, automations, integration options; summarize findings with recommendations. • Documentation: maintain lightweight SOPs, setup notes, “how we do it” pages, and release/change logs when needed. • Communication & follow-through: track blockers, ping the right people, keep threads from dying, and provide concise updates. • Tool hygiene: help manage/optimize Jira workflows, templates, boards, filters, labels, and dashboards. • General execution support: scheduling coordination, meeting notes (action-focused), reminders, and “don’t let this drop” tracking. AI-friendly workflow (required) We embrace AI and you may use it as much as you’d like to move faster—draft tickets, summarize threads, create SOPs, research tools, write outlines, etc. Non-negotiable: you must be able to QC (quality check) AI output like a professional: • Verify technical claims before sharing them • Catch missing steps, wrong assumptions, and hallucinations • Rewrite for clarity, correctness, and native-level English • Ensure Jira tickets and docs are accurate, actionable, and aligned with our standards If you lean on AI but can’t reliably validate the output, this role will be a bad fit. What “good” looks like in this role • The developer stays in flow because you are the external brain: organized, calm, relentless about clarity. • Jira is clean: tickets are well-written, prioritized, and actually usable. • Bugs are actionable: devs get repro steps and evidence, not vague descriptions. • You move fast with AI, but deliver work that is clean, correct, and ready to execute. • You bring solutions, not just questions. Required skills / must-haves • Premium English fluency (written and spoken). You write tickets and documentation that sound native, crisp, and professional. • Solid understanding of software development workflows (Agile-ish, sprints, backlog, QA basics). • Strong writing ability: • clear ticket descriptions • acceptance criteria • concise summaries • step-by-step instructions • Comfortable with technical concepts (you don’t need to code, but you must understand the environment): • APIs and web apps (conceptually) • basic QA/repro mindset • integrations/automation tools • Strong Jira competency (boards, workflows, filters, labels, fields, dashboards). • Proactive ownership: you spot problems early and keep work moving. Nice-to-haves (big plus) • Experience with: Jira, N8N, AWS, Google Cloud, Bitbucket, GitHub/GitLab, Zapier/Make, Postman • Light technical ability: basic scripting, SQL, or simple API calls • Experience supporting a founder/engineer or fast-moving startup team Working style • Remote • Responsive during agreed overlap hours • Comfortable with ambiguity, but not sloppy—your job is to turn ambiguity into a plan Include this in applications: “QC matters.”