Senior Accountant - SEC Reporting and Technical Accounting

We need to output HTML fragment with sections: About the role? The posting includes a summary paragraph after title. That could be "About the role". Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID/requisition numbers as headings; can fold into short

  or drop. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove lines like "Please visit our website... for more information... to apply for this position; reference requisition #IONIS003733". Also remove "Ionis offers an excellent benefits package! Follow this link for more details: Ionis Benefits Full Benefits Link: ...". Also remove "NO PHONE CALLS PLEASE. PRINCIPALS ONLY." Also remove EEO line. We need to preserve all substantive information: company description, summary, responsibilities, requirements, preferred experience, work location, pay scale, maybe benefits? Benefits section only if posting actually states them. The posting mentions "Ionis offers an excellent benefits package!" and provides a link. That is substantive? It mentions benefits exist but not details. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits exist, but not details. Should we include a Benefits section? It says "Ionis offers an excellent benefits package!" That's a statement about benefits. Could be considered stating benefits exist, but not specifics. The rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Benefits section with just a statement that they offer benefits might be considered filler? Not sure. Safer to include a Benefits section with a short paragraph describing that they offer an excellent benefits package and link? But we removed the link as application instruction? The link is to benefits page; it's not application instruction per se, but it's a link for more details. Might be considered okay to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The benefits link is not exactly application instruction, but it's a link for more details. Might be considered part of benefits info. I'd keep a Benefits section with a paragraph: "Ionis offers an excellent benefits package. See the benefits page for details." But we need to avoid invented details. We can keep the statement as is. Pay scale: The posting explicitly states "The pay scale for this position is $90,000 to $119,180". So we must include Pay section. Schedule: Not mentioned besides work location (Onsite/hybrid). No explicit schedule like full-time, part-time. So we should not create Schedule section. Work location: Could be included in a section? Not listed as a heading option. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work location could go under About the role or maybe as a short paragraph in About the role. We'll include location in About the role paragraph. We need to preserve all substantive information: company description at start, summary, responsibilities list, requirements list, preferred experience list, work location, pay scale, benefits statement. We must not invent or summarize away detail. So we need to keep each bullet. Let's extract: Company description paragraph: "Headquartered in Carlsbad, California, and with offices in Boston, Massachusetts, and Dublin, Ireland, Ionis has been at work for more than three decades discovering medical breakthroughs that have redefined life for people with serious diseases. We’re pioneers in RNA-targeted medicines, and our platform continues to revolutionize drug discovery and transform lives for patients with unmet needs. With multiple marketed medicines and a leading pipeline in neurology, cardiology and select areas of high patient needs, we continue to drive innovation in RNA therapies in addition to advancing new approaches in gene editing to provide greater value to patients and are well positioned financially to deliver on our strategic goals. At Ionis, we pride ourselves on cultivating a challenging, motivating and rewarding environment that fosters innovation and scientific excellence. We know that our success is a direct result of the exceptional talents and dedication of our employees. With an unprecedented opportunity to change the course of human health, we look to add diverse individuals, skill sets and perspectives to our exceptional team. We continue to invest time, money and energy into making our onsite, hybrid and remote work environments a place where solid and lasting relationships are built and where our culture and employees can thrive. We’re building on our rich history, and we believe our greatest achievements are ahead of us. If you’re passionate about the opportunity to have meaningful impact on patients in need, we invite you to apply and join us. Experience and contribute to our unique culture while you develop and expand your career!" That's a lot; we keep it as prose under About the role. Then "SENIOR ACCOUNTANT – SEC REPORTING & TECHNICAL ACCOUNTING Summary The Senior Accountant for SEC Reporting and Technical Accounting will report to the Associate Director, SEC Reporting & Technical Accounting. This team member will support Ionis’ external financial reporting and financial statement close processes, including preparing audit deliverables and performing internal controls for certain business processes. In addition, this team member will be responsible for researching and applying technical accounting guidance, preparing memoranda, and supporting special projects across the organization. The ideal candidate has at least five years of relevant experience including multiple years of public accounting experience, strong understanding of U.S. GAAP, the ability to effectively self-lead, excellent communication and time management skills and strong attention to detail." That's the summary; we can include under About the role as well, or maybe separate About the role includes summary. We'll keep it as part of About the role. Then "WORK LOCATION: Onsite/hybrid in Carlsbad, CA". We'll include that in About the role paragraph. Then Responsibilities list: bullet points: - Support quarterly and year-end financial reporting and audit deliverables, including preparation of Ionis’ quarterly earnings releases and Forms 10-Q and 10-K, related tie-outs, and XBRL review - Support the financial statement close process by preparing journal entries and account reconciliations for investments, leases, debt, equity (including stock-based compensation), and other assigned areas - Prepare quarterly consolidated financial statements, including statements of equity and cash flows - Play an integral role in ensuring that internal controls in assigned areas operate as designed and support Sarbanes-Oxley (SOX) compliance activities - Monitor, research and analyze current, new, and pending technical accounting guidance as needed - Prepare technical accounting memoranda for specific transactions and the adoption of new accounting guidance - Assist in overseeing accounting policies, including drafting any new policies upon adoption of new accounting principles - Identify opportunities to optimize accounting processes and procedures - Perform other duties and special projects as assigned We'll put under

  Responsibilities

  with
  • . Then Requirements list: - Bachelor’s degree in Accounting - CPA certification (or in-process) - At least five years of relevant accounting experience, including at least two years at a public accounting firm - Strong understanding of U.S. GAAP and the ability to research and interpret accounting guidance - Proficiency in Microsoft Office programs - Self-motivated and goal-oriented, with the ability to adapt and work efficiently and effectively in a dynamic environment - Strong written and oral communication skills - Excellent attention to detail and commitment to accuracy and completeness of working papers - Strong analytical and problem-solving skills, with the ability to take ownership of projects and processes - Collaborative and comfortable asking questions, engaging in constructive debate, and addressing challenging issues - Excellent time-management and prioritization skills, with the ability to manage multiple time-sensitive deadlines We'll put under

    Requirements

    (or Qualifications? The allowed headings include Requirements, Qualifications, Skills. We have both requirements and maybe skills. We'll use Requirements for the list; maybe Skills for some like proficiency in Microsoft Office, communication skills, etc. But we can keep all under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one Requirements section. We'll just use Requirements. Then Preferred Experience list (maybe under Preferred Experience but not a standard heading; we could put under Requirements as "Preferred" but better to have a separate section? Not in allowed headings. Could fold into Requirements as a paragraph. But we could create a "Preferred Experience" heading? Not allowed. So we should incorporate into Requirements or maybe under Skills. Since it's not a standard heading, we should avoid creating new headings. So we can add a paragraph after Requirements: "Preferred experience includes..." but that would be a

    . That's okay. Preferred experience items: - Experience at a Big Four public accounting firm strongly preferred - Broadridge or other SEC filing software - SAP or another enterprise resource planning (ERP) system - BlackLine - Equity Edge Online - Clearwater - OneStream We'll put as a

    with list? Could be a

    but it's still a list; we can use
    • under a

      ? Actually we need to use

      • for any list of duties/requirements/benefits. So we can make a
        for preferred experience, but we need a heading? Not required; we can just have a
        directly after a

        intro. But the instruction: Use

        • for any list of duties/requirements/benefits. So we can do that. We'll add a

          Preferred experience (strongly preferred):

          then
          . Pay scale: we need a Pay section with the pay range. Use

          Pay

          then

          The pay scale for this position is $90,000 to $119,180.

          Benefits: we have statement "Ionis offers an excellent benefits package!" plus link. We'll create Benefits section with

          Benefits

          then

          Ionis offers an excellent benefits package. See the benefits page for details: https://www.ionis.com/careers/working-at-ionis/#:~:text=our%20employee%20spotlight-,Benefits,-Employees%20are%20rewarded

          . But we need to check if that link is considered application instruction? It's a benefits link, not application. Probably okay. We must not include duplicated lines. Ensure we don't repeat the job title as heading. Now produce HTML fragment: start with maybe

          About the role

          then

          ... company description + summary + work location ...

          . Then

          Responsibilities

          ...
          . Then

          Requirements

          ...
          . Then maybe

          Preferred experience (strongly preferred):

          ...
          . Then

          Benefits

          ...

          . Then

          Pay

          ...

          . Make sure no extra whitespace? It's fine. Let's craft the About the role paragraph: combine company description and summary and work location. Company description paragraph (first big block). Then summary block. Then work location. We'll produce one

          containing all that text, but it's long; okay. We need to ensure we don't include any boilerplate like "Please visit our website..." etc. Remove that. Also remove "Ionis offers an excellent benefits package! Follow this link for more details: Ionis Benefits Full Benefits Link: ..." We'll keep benefits statement but not the "Follow this link for more details: Ionis Benefits Full Benefits Link:" part. We'll just keep "Ionis