# Lever + Jira integration > Automate the handoff between your recruiting pipeline and engineering project management so your teams stay in sync without the manual work. **Canonical page:** https://tray.ai/connectors/lever-jira-integrations/ **Lever connector:** https://tray.ai/connectors/lever-integrations/ **Lever documentation:** https://tray.ai/documentation/connectors/service/lever **Jira connector:** https://tray.ai/connectors/jira-integrations/ **Jira documentation:** https://tray.ai/documentation/connectors/service/jira ## Overview Lever and Jira do very different jobs — one runs your talent acquisition pipeline, the other runs software development and project tracking. But when candidates move through Lever, engineering teams often need visibility into headcount planning, onboarding tasks, and role-specific project assignments that live in Jira. Without a connection between the two, that information gets lost in handoff emails and Slack threads. Integrating Lever with Jira means hiring milestones automatically trigger the right actions in your project management workflows, and People Ops and Engineering can finally stop playing phone tag. Engineering teams live in Jira. Recruiters live in Lever. When a new hire is made or a role opens up, things fall through the cracks between handoff emails, Slack messages, and spreadsheets. By connecting Lever and Jira through tray.ai, you can automatically create Jira epics or issues when a new requisition opens, update project capacity planning boards when candidates advance through interview stages, and kick off onboarding task creation the moment an offer is accepted. Hiring managers always have up-to-date status in Jira, recruiters don't have to chase down engineer feedback, and new hires have pre-built Jira task boards waiting on day one. ## Use cases ### Automatic Onboarding Task Creation When an Offer Is Accepted When a candidate's stage in Lever moves to 'Offer Accepted,' tray.ai triggers the automatic creation of a Jira epic and a predefined set of onboarding issues assigned to the appropriate engineering team. The new hire's first-day environment, access provisioning, and ramp-up tasks are already in motion before they start. No more manually copying onboarding checklists or losing tasks in email threads. - New hire onboarding tasks are created in Jira the moment an offer is accepted in Lever - Engineering managers get instant visibility into incoming team members via their existing Jira boards - Environment setup starts days before the new hire's first day, cutting time-to-productivity ### Sync Interview Feedback from Jira to Lever for Faster Hiring Decisions Engineers and technical interviewers often track notes and scorecards in Jira tickets or linked Confluence pages during a hiring loop. With a Lever-Jira integration, structured feedback submitted in a Jira issue gets automatically posted as a note or feedback form response back in Lever, keeping the candidate record complete. Recruiters get a single source of truth without having to chase interviewers across tools. - Interview feedback flows from Jira into Lever automatically, eliminating manual data entry - Recruiters get complete candidate records without hunting down engineer availability - Consolidated, real-time feedback in Lever means faster hiring decisions ### Create Jira Epics for Open Requisitions to Support Headcount Planning When a new job requisition is created or approved in Lever, tray.ai can automatically generate a corresponding Jira epic or story tied to the hiring team's capacity planning project. Engineering leads get a real-time view of open roles that will affect their team size and sprint planning. Leaders can track requisition status directly in Jira without waiting on separate reports from HR. - Engineering leaders see open headcount needs reflected instantly in their Jira planning boards - Recruiting timelines connect directly to sprint and roadmap planning in Jira - No more manual headcount spreadsheets maintained across multiple teams ### Trigger Jira Issues for Technical Assessments and Take-Home Projects When a candidate advances to a technical assessment stage in Lever, tray.ai can automatically create a Jira issue or sub-task to notify the engineering team responsible for reviewing the submission. The issue includes the candidate's name, role, and deadline, keeping assessment review accountable and tracked. No more relying on ad-hoc Slack pings to remind engineers to review take-home assignments. - Technical review tasks are created in Jira automatically when candidates reach assessment stages in Lever - Assessment deadlines and reviewer assignments are tracked natively within Jira - Candidates wait less because submissions don't sit unreviewed in someone's inbox ### Update Engineering Teams in Jira When Candidates Are Archived or Declined When a candidate is archived or declined in Lever, tray.ai can update or close the corresponding Jira issues tied to that hiring process, keeping project boards clean and capacity forecasts accurate. Engineering teams won't plan headcount around roles that are no longer actively being filled. Jira stays in sync with Lever stage changes and avoids confusion during quarterly planning. - Jira boards stay clean and accurate when candidates are declined or archived in Lever - Engineering capacity planning reflects real-time recruiting status without manual updates - Teams don't over-plan around roles that are on hold or cancelled ### Auto-Assign Jira Tickets for Interview Scheduling Coordination When an interview is scheduled in Lever, tray.ai can create Jira sub-tasks assigned to each interviewer with relevant candidate details, interview time, and evaluation criteria. Interview logistics stay visible within Jira for teams that don't want to switch contexts, and interviewers are formally assigned and accountable. This works especially well for engineering teams running structured hiring loops with multiple panel interviewers. - Interviewers receive formal Jira task assignments when interviews are confirmed in Lever - Structured interview loops are tracked end-to-end within Jira without switching tools - Interviews surface in interviewers' existing workflow, reducing no-shows and missed prep ### Sync Lever Candidate Data to Jira for Contractor and Agency Tracking For organizations hiring contractors or agency workers, candidate data from Lever can be synced to Jira service management projects to track compliance documentation, contract status, and equipment provisioning. When a contractor's offer is accepted in Lever, a Jira service request is automatically raised for IT and legal to complete their respective workflows. The result is a clean, auditable process bridging recruiting and operations. - Contractor onboarding workflows in Jira are triggered automatically from Lever offer acceptance - IT and legal teams receive Jira service requests pre-populated with contractor details - Both recruiting and operations systems share a documented, auditable trail ## Templates ### Offer Accepted in Lever → Create Onboarding Epic in Jira Automatically creates a Jira epic with a predefined set of onboarding sub-tasks whenever a candidate's stage in Lever changes to 'Offer Accepted.' The epic is pre-populated with the new hire's name, start date, role, and hiring manager, and tasks are assigned to the relevant teams such as IT, engineering, and People Ops. Connectors used: Lever, Jira ### New Lever Requisition → Create Jira Headcount Planning Issue When a new job requisition is opened or approved in Lever, this template creates a linked Jira issue in the team's headcount planning board. Engineering managers can track the requisition's progress, expected start date, and team impact directly within their Jira project without logging into Lever. Connectors used: Lever, Jira ### Candidate Reaches Technical Interview Stage in Lever → Create Jira Assessment Review Task Monitors Lever for candidates advancing to a technical interview or take-home assessment stage and automatically creates a Jira task assigned to the designated engineering reviewer. The task includes candidate context, submission deadline, and a link to the assessment materials stored in Lever. Connectors used: Lever, Jira ### Lever Candidate Archived → Close or Update Linked Jira Issues When a candidate is archived or marked as declined in Lever, this template automatically updates the status of all linked Jira issues to 'Done' or 'Cancelled,' keeping project boards current and preventing stale open tickets from cluttering capacity planning views. Connectors used: Lever, Jira ### Interview Scheduled in Lever → Create Interviewer Tasks in Jira Each time an interview is confirmed in Lever, this template generates individual Jira sub-tasks for each assigned interviewer with candidate details, interview time, focus areas, and a link to the Lever candidate profile. Interviewers can log their readiness and feedback status directly within Jira. Connectors used: Lever, Jira ### Lever Offer Accepted → Raise Jira Service Management Request for IT Provisioning When an offer is accepted in Lever, this template raises a Jira Service Management request for the IT team to begin equipment provisioning, access setup, and software licensing. The request is auto-populated with new hire details, start date, and role-specific equipment needs pulled from Lever custom fields. Connectors used: Lever, Jira ## Challenges Tray.ai solves ### Mapping Lever Stage Changes to Meaningful Jira Actions Lever uses a flexible, customizable pipeline with stages that vary by company and role type. Translating those recruiting stages — 'Phone Screen,' 'Technical Loop,' 'Offer Extended' — into the right Jira issue types, statuses, and transitions requires careful conditional logic that's hard to maintain manually or with rigid point-to-point integrations. **How Tray.ai helps:** tray.ai's visual workflow builder lets you define conditional branching logic that maps any Lever stage name or change event to a specific Jira action. You can configure stage-to-action mappings without code, update them as your hiring process evolves, and apply different logic per job requisition type or department — all from a single workflow. ### Keeping Jira Issues in Sync as Candidates Move Backwards or Are Reinstated Recruiting pipelines are rarely linear. Candidates get moved back to earlier stages, archived candidates get reinstated, and requisitions go on hold mid-process. Without intelligent sync logic, Jira issues quickly fall out of date — closed tickets for active candidates, open tasks for paused roles. **How Tray.ai helps:** tray.ai workflows can listen for any Lever webhook event, including stage reversals, archive removals, and requisition status changes, then run the right corrective action in Jira. That means reopening issues, updating statuses, and adding audit comments so your Jira boards always reflect what's actually happening in your Lever pipeline. ### Handling Custom Fields and Metadata Across Both Platforms Both Lever and Jira support extensive custom field configurations, and every organization uses them differently. Passing custom data like compensation band, interview panel composition, or hiring urgency between the two systems without losing fidelity or breaking issue templates is a genuinely frustrating integration problem. **How Tray.ai helps:** tray.ai's data transformation tools let you map, rename, and reformat custom fields from Lever into the exact Jira field schema your team uses. The built-in JSONPath editor and transformation helpers handle nested objects, array fields, and conditional field mappings without backend code, making custom field sync something you can actually maintain. ### Managing Permissions and Data Privacy Between HR and Engineering Systems Lever holds sensitive candidate data — compensation details, personal contact information, confidential hiring notes — that shouldn't be broadly visible in Jira, where engineering team members have general access. Getting the integration right without accidentally exposing that data is a real governance problem. **How Tray.ai helps:** tray.ai lets you define exactly which fields get extracted from Lever and passed to Jira at the workflow level. Sensitive fields like salary, personal contact details, and private notes can be excluded from the data payload before it ever reaches Jira. Combined with tray.ai's secure credential management and role-based access controls, you can enforce data governance policies across the integration without manual field filtering. ### Avoiding Duplicate Jira Issues from Repeated Lever Webhook Events Lever webhooks can fire multiple times for a single stage change, particularly when bulk actions are performed or when retry logic kicks in after a temporary API timeout. Without deduplication logic, those repeated events create multiple identical Jira issues for the same candidate, cluttering boards and confusing everyone involved. **How Tray.ai helps:** tray.ai includes built-in deduplication and idempotency controls that check whether a Jira issue for a given Lever candidate or requisition already exists before creating a new one. You can configure lookups by candidate ID, requisition ID, or custom label so that repeated webhook events are handled cleanly and each candidate maps to exactly one set of Jira issues, no matter how many times the trigger fires. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/