TeamOhana integrates with Lever so anyone on the team can track hiring progress in real-time – not in spreadsheets. Lever connects seamlessly with TeamOhana to make planning and hiring easier than ever.
Contact Sales
Lever is a leading Talent Acquisition Suite that makes it easy for talent teams to reach their hiring goals and to connect companies with top talent. The integration enables reporting that flags discrepancies between planned vs. actual, and predicts your Talent team's velocity based on historical data.
Customers using this integration
Give visibility into hiring
You won't need to answer the question, "How's hiring going?" anymore. TeamOhana automates hiring status updates in a collaborative system so everyone has visibility.
Trust the offer details
When offers are made in Lever, you can bring the offer details directly into TeamOhana, giving you a real-time view of your budgets vs actuals.
Give visibility into hiring
You won't need to answer the question, "How's hiring going?" anymore. TeamOhana automates hiring status updates in a collaborative system so everyone has visibility.
Trust the offer details
When offers are made in Lever, you can bring the offer details directly into TeamOhana, giving you a real-time view of your budgets vs actuals.
Visualize current and future team
Utilize a Dynamic Org Chart with all relevant people data.
Visualize current and future team
Utilize a Dynamic Org Chart with all relevant people data.
Streamline approvals
Simplify and centralize headcount requests and make better approval decisions with an audit trail for visibility.
Tags
The Tag object is used to represent a tag for a candidate.
Scorecards
The Scorecard object is used to represent an interviewer's candidate recommendation based on a particular interview.
Interviews
The ScheduledInterview object is used to represent a scheduled interview for a given candidate’s application to a job. An Application can have multiple ScheduledInterviews depending on the particular hiring process.
Users
The RemoteUser object is used to represent a user with a login to the ATS system.
Reject Reasons
The RejectReason object is used to represent a reason for rejecting an application. These can typically be configured within an ATS system.
Offices
The Office object is used to represent an office within a company. A given Job has the Office ID in its offices field.
Offers
The Offer object is used to represent an offer for a candidate's application specific to a job.
Job Interview Stages
The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.
Jobs
The Job object can be used to track any jobs that are currently or will be open/closed for applications.
Eeocs
The EEOC object is used to represent the Equal Employment Opportunity Commission information for a candidate (race, gender, veteran status, disability status).
Departments
The Department object is used to represent a department within a company.
Candidates
The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.
Attachments
The Attachment object is used to represent a file attached to a candidate.
Applications
The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.
Activities
The Activity object is used to represent an activity for a candidate performed by a user.
Integration FAQ
Q: Do I need to keep using the approval flows in Lever once I start using TeamOhana?
A: No you don't, as TeamOhana has approval workflows that can be set up for net new headcount requests, backfill requests, and change requests.
- Step 1: Add the first step
- Step 2: Continue with the second step
- Step 3: Don’t forget the third step
- Step 4: Continue with the forth stepStep 5: After that continue with the fifth stepStep 6: Finally ends with this step
