Explore Lessonly's Assignments

Choose Organization Growth Framework
Exploring Lessonly's growth framework
Choose Starting Position
Starting with the position: Product Quality Engineer - 3.4 (Player/Coach) (aka Principal Product Quality Engineer) (Check out Product Quality Engineer - 3.4 (Player/Coach))
Choose Assignments
Now it is time for you to build your unique job description! Simply go through and add a checkmark next to all of the Assignments you'd want to take on.
Click to copy the URL to share this exploration

Showing only relevant Assignments

  • Lessonly

     Assignments:

    We engage in meaningful conversations on ways to help the Lessonly organization do better work.

    Full Description

    We engage in meaningful conversations on ways to help the Lessonly organization do better work.

    • For example, we may take part in the following initiatives:
      • Connections Committee
      • Diversity and Inclusion Advocates
      • Marketing Blog Blitz
    Requirements
    • Must have a position with the reach of 1.1 or higher
    • For this role, it is recommended to be milestone 1 or greater inInitiative
    • For this role, it is recommended to be milestone 1 or greater inCommunication
    Examples
      Observation created about 5 years ago

    Over the last couple of weeks, Casey and I have had some great conversation about how things are going. There are things that she was willing to tell me that i needed to hear. She also was interesting in hearing some of the things I had to say. She is interested in how I am doing as well as my opinions of our organization from a fresh perspective. This not only shares how she cares about me as a person, but about the place show works. This is an interaction that is outside her reporting structure, but she cares


    • Product & Engineering

       Assignments:

      We provide context through communication boosting productivity leading to new llama satisfaction.

      Full Description
      • We provide context through open communication to provide relevant information to the new llama and encourage a process of continued, self-directed learning.
      • We boost productivity by helping the new llama in many situations based on his/her experience and knowledge to become productive in their role quickly and to help build self-confidence allowing him/her to focus on adding value to Lessonly.
      • We help improve new llama satisfaction by reducing the initial confusion and uncertainty faced by all new llamas.
      Requirements
      • Must have a position with the reach of 2.1 or higher
      • For this role, you must be milestone 1 or greater inCommunication
      • For this role, you must be milestone 1 or greater inProduct Knowledge
      • For this role, you must be milestone 1 or greater inInitiative
      • For this role, you must be milestone 2 or greater inCollaboration
      Examples
      An observation relating to  Onboarding buddy  has not been publicly recognized yet.

      Growing the team is one of the most important things we do... and we interviewers are responsible for helping to decide on our future teammates.

      Full Description

      Success:

      • You are counted on for two things as it pertains to new llamas joining the pack:
        • Help the candidates get a clear idea of the Lessonly culture as well as the different aspect of the job they are applying for.
        • You'll also be vital in helping the hiring manager assess the candidate across a plethora of criteria

      Details:

      • Attend all on-site interviews for a single position
      • Actively work to give the candidate clarity about who we are
      • Actively work to give clarity to the hirer about your perception of the candidate
      • Understanding of the role the interviewee is interviewing for and the why behind the role
      • Prepared on the general background of the candidate
      • Prepared 2-4 questions based on the role and the candidate
      • Be an active listener. Make sure you are present to the interviewee and not thinking about your life while he or she is talking Here are a couple of thing that I try to do before and during an interview.
      • You listen to answers to see if they follow the values of Lessonly. Ask clarifying questions.
      • When preparing questions, you keep in mind the Lessonly values
      Requirements
      • Must have a position with the reach of 1.1 or higher
      • For this role, you must be milestone 1 or greater inCommunication
      Examples
        Observation created over 5 years ago

      I've been with Ashley as she's been on an interview panel for the first time this week. The cool thing is, you'd never know it was her first time!

      Ashley has been asking really thoughtful questions during the interviews that have helped unearth some great details about the candidates we've been chatting with. Not only that, but I feel like she's communicated with our candidates in a way that is super respectful, down-to-earth, and would make me feel a little more relaxed if I'd been interviewed by her.

      I also appreciate in our debriefs how thoroughly she's thought through the interviews to make sure that we hire candidates that are great culture fits.

      Thanks for being an awesome interviewer, Ashley!

      We engage in meaningful conversations on ways to help the Product and Engineering team do better work

      Full Description

      Success

      • Do Better Work Groups are a way for anyone on the product team to see something they want to see improved, propose a quest to identify the best solution, and once prioritized make that change happen.
      • You, as a member of a DBW group will be successful if you are a part of inspiring and enabling us to do better work!
      Requirements
      • Must have a position with the reach of 1.1 or higher
      • For this role, you must be milestone 1 or greater inInitiative
      • For this role, you must be milestone 1 or greater inCommunication
      Examples
      An observation relating to  P&E DBW group member  has not been publicly recognized yet.

      We have a robust understanding of the current state of escalations and prioritize the best ways to reduce them.

      Full Description

      Description

      Escalations are necessary, but expensive.

      • Expensive because of the negative impact on Experience of Lessonly’s Customer Service teams
        • Anytime a customer-facing rep cannot answer a question, resolve a problem, or make a change that enhances the value of our offering to the customer in question, it reduces the overall experience.
      • Expensive because escalations are unplanned work for those that could be otherwise improving the system
        • Every moment that is spent NOT making improvements to the system by someone with the skill, access, and knowledge to make enhancements is less than ideal.

      Key Result(s) / Outcomes

      • Observability
        • Stakeholders strongly agree or agree when asked “I know what the escalation trends are, and understand what we are doing to reduce them (so that we don’t have the same ones that are bugging us today be the same ones we are bugged by 6 months from now)”.
      • Outcomes
        • If the above is true, then we can/will have a quarter-over-quarter reduction in known escalations (as defined by any escalation type that occurs more than once per month for at least 3 contiguous months and/or takes more than a day of any tier-2+ person).
          • There will always be new escalation-needs being added, such is the physics of creating software. The purpose of this goal is that the known escalation-needs are consistently being eliminated.
        • Customer-facing team members strongly agree or agree when asked “I am continuously given ever-improving tools, knowledge, or skills from the Empower Squad and/or the other product squads that help me serve customers directly without needing to ask for help”.
      Requirements
      Examples
        Observation created over 6 years ago

      I ❤️ this message that is hidden away in a CH story. It tells the full tale of what I'm spotlighting: https://app.clubhouse.io/lessonly/story/26584/understand-escalations#activity-26619

      However, the thing that I appreciate about this, was Rick's conclusions that he put at the end of each question he referenced. That made it so I didn't have to guess at anything nor did I have to try and interpret the intent behind sharing the reports.

      Overall this was excellent.

      The only thing I was left wanting was clear next steps. But even with that need still existing I felt this was more than worthy of highlighting!


      • Engineering

         Assignments:
        --None--

        • Product Quality

           Assignments:

          We are responsible for ensuring our application is updated in a safe, effective, and communicative manner.

          Full Description

          Success:

          • You are responsible for ensuring our application is updated in a safe, effective, and communicative manner.

          Details:

          • TBD
          Requirements
          Examples
            Observation created over 5 years ago

          https://lessonly.slack.com/archives/C73ND911P/p1582829414005400?thread_ts=1582828748.005100&cid=C73ND911P

          Talk about attention to detail, operational awareness, and excellent communication!

          This was simply fantastic!!

            Observation created almost 6 years ago

          Patrick joined the team at the start of this quarter. Now that he has been here a quarter I don't know how we used to operate without him. It is not only his thoroughness when it comes to the stories themselves but he thinks about the "soul" of the ticket. What is this actually trying to solve? Is it solving for the entire problem? His attention to detail is staggering and I am grateful he is on the team.

          He was also instrumental in the xAPI testing. It is a tricky process to test xAPI in a review, staging, and production app. He was ahead of it the whole time and made me feel confident we are releasing something we can have confidence in.

          Our goal is NOT to test quality in, but instead to help the team build quality in from the start. Moving QA thinking farther left is our prime directive.

          Full Description

          Success looks like

          • Very few priority-1 and priority-2 defect escapees found in production.
          • You'll be successful at this role if the quality control process is one of collaboration and not tension between tester and coder.
          • You'll be successful at this role if the team learns how to build quality in from the start, a bit more every day.
          • We have this role because it is essential to ensuring a high-quality experience for our users. The goal is NOT zero bugs... the goal is balancing speed with risk management.

          Details

          • Measures like the number of remediations, number of written bugs, number of stories tested are all important, but none of them alone tell the story of the value of this role.
            • If there are no remediations happening, that means the engineers are perfect, or we aren't looking deep/wide enough, or maybe we've found a point where we are writing up shippable priority-3, 4, or 5 bugs but they do not need to block the stories. Alone it doesn't tell the story, but it is an indicator
            • If there are no bugs written, this could mean either the engineers are perfect, or our calibration of what constitutes a bug is off, or if remediations are through the roof maybe we have over-calibrated to what should constitute shippable. Alone it doesn't tell the story, but it is an indicator
            • If the number of stories tested is low... well, you should chat with your manager... not sure what this could mean other than bad things 🤔
          Requirements
          Examples
          An observation relating to  Quality control tester  has not been publicly recognized yet.

          We serve the function of Product QA, and those executing against its roles. Our goal is continuous improvement of the tools and processes (balancing autonomy and focusing on feedback loops).

          Full Description

          Success:

          • Those executing against the following roles have a continuously improving set of tools and processes (balancing autonomy and focusing on feedback loops).
            • Quality control tester
            • Technical investigator

          Details:

          • You'll help ensure that testability is a consideration in build, and testers know how to raise it as a concern
          • You'll help ensure that things are testable across environments
          • You'll help ensure that testers have a shared understanding of risk and coverage needs across the app, based on current best knowledge and trends
          • You'll help ensure that testers have what they need from a tooling and clarity perspective to level up at the core testing abilities:
            • Technical Investigation
            • Bug/Story Writing
            • System Modeling
            • Risk Assessment
          Requirements
          Examples
          An observation relating to  Product Quality Assurance Enablement Lead  has not been publicly recognized yet.
      • Management

         Assignments:

        Our sole goal is to help fill the top of the funnel with "Hell Yeah" candidates

        Full Description

        Key Result(s) / Outcomes

        There isn’t a formal quantitative measure, however, once you are in a leadership position, recruiting becomes at the very least a passive part of your job.

        It does not mean it is a primary responsibility, or that you are running the recruiting process. It does mean that you are making time to have conversations with people outside of Lessonly for networking purposes. It does mean that when you do have an active opening, you are helping the Talent team member and if you have time you are proactively reaching out to candidates to have discovery calls before officially putting them in the process.

        Details:

        • Work with the hiring manager to identify the ideal candidate profile
        • Coordinate with the other recruiters for the given position to ensure you are not all reaching out to the same candidates
        • Devise relatable messages to send to prospective candidates that paint a clear picture of what the opportunity is
        • Cultivate relationships with the community to ensure we have a great pipeline of candidates when positions open back up
        Requirements
        • Must have a position with the reach of 1.1 or higher
        Examples
        An observation relating to  Recruiter  has not been publicly recognized yet.

        We strive to influence those we serve to achieve their own goals as well as their work goals via clarity, trust, accountability, empowerment, and being an example of the Lessonly values and definition of an ideal team player.

        Full Description

        There are three aspects to technology management at Lessonly. The core philosophy that all Lessonly managers adhere to. Systematizing clarity with appreciative inquiry and feedback loops. Mission control, meaning a focus on outcomes in nearly all we do.

        We will end this description with some examples of measures that technology managers will be held accountable for.

        The core philosophy

        The Lessonly Management philosophy is the underlying engine behind everything else within this role. This lesson is the source of truth for this philosophy.

        Positions that require this role will be required to have achieved an early milestone of the required abilities for the craft of your domain, to help us make good decisions for our teams.

        Positions that require this role will be required to have achieved a milestone 3+ for business knowledge to help ensure we can give good context to our team goals.

        Positions that require this role will be required to be milestone 3+ for {mentorship} and {community}, given how vital it is for us to care for the person more than the employee.

        These are the most important aspects of management at Lessonly, however, there are three other keys to success for management on the technology team.

        Systematize Clarity

        Another critical aspect of Lessonly management is seeking clarity (finding out what is working) and giving clarity (ensuring folks know what matters most and why it matters).

        Within the tech team, we do that in various ways. One of those ways is seen by the fact that positions which require this role will also be required to be an enablement lead for the appropriate domain, to ensure we are continuously working through this clarity feedback loop.

        Systems with feedback loops are a great way to ensure accountability. Accountability to those we serve… being able to hold those we serve accountable, as well as accountability to our teammates. Knowing we can rely on each other.

        Balancing autonomy and alignment to make room for innovation...

        Building systems with feedback loops so that it is clear what winning is…

        Leading with the principles of appreciative inquiry…

        These are all vital for the thought work which we are responsible for. Our work product isn’t physical, and can’t be measured purely quantitatively. This means it is on us to foster an environment that embraces uncertainty… encourage a team that embraces constantly changing definitions of clarity… a culture that embraces continuous improvement.

        Mission-Control… means focus on Outcomes

        We are laser-focused on iteratively, continuously, relentlessly adding value to the vision of making continuous training possible for all customer-facing teams.

        The best way to do that is to be continuously learning and improving.

        Outcomes, as opposed to outputs or activities, ensure we are all aiming at the same target/rowing in the same direction.

        It also gives freedom to have trial and error, which is one of the most tried and true ways to have lasting growth.

        Types of managers

        The Lessonly technology team greatly values flexibility and adjusting strategy (how we organize to solve problems) based on the strengths of the individuals on the team(s) in question. Therefore, the positions which require “people management” (or the term I prefer, accountable servant leadership), will also not all look the same. Here is a non-exhaustive list of some potential types. \

        Key Result(s) / Outcomes

        • Onboarding effectiveness
          • Time from hire date to a non-apprentice (achieved all of the appropriate milestones) on all of the required roles for the position. Ideally, 3 months from hire.
        • Career journey guidance effectiveness
          • When those you serve are asked the following question, 80%+ of them (strongly) agree: “When I look back from a year ago to where I am now... what I have achieved… how I’ve grown, I am excited about the progress I’ve made”.
        • OfficeVibe 10 key drivers
          • We do not hold anyone accountable for these measures directly, because it incentivizes behaviors we don’t want to incentivize… however, managers will have access to and should be aware of the opportunities of things we could do as well as the impacts of the things we have done on these measures. So the measure here is awareness of and a plan of action around this employee engagement data.
        Requirements
        Examples
          Observation created almost 6 years ago

        I want to give a well-deserved shout out to our awesome engineering managers.

        First off, to Brea, who is making a point spending time getting to know each and every engineer on the team personally. It's really helped me to feel valued by her, and I'm sure will help her relationships with her reporting engineers start off a lot more smoothly. There are a million things she could be doing to be learning about Lessonly, our codebase, how managers here work, etc, but the fact that she has spent time getting to know us (and at more than a group level) shows me that her people are her biggest priority and that's huge. Thanks Brea!

        And then of course to Casey, who has been working tirelessly as the solo manager for months now and, even though I wasn't here for most of those months, I feel confident saying she probably never complained. In the time I've been back since being on leave, I've been impressed at how she manages to meet with all of us, answer questions, write up stories, do code reviews, lead hiring, and still manage to be her positive, happy self that we have all come to appreciate. Thanks, Casey, for being a great manager while also leading and lifting up the team in so many ways. We are glad you decided to spend your superpowers on us here at Lessonly. :)

          Observation created about 6 years ago

        This morning, Gardee reached out to me with the following message:

        Hey Hey! Each quarter I work with --name is redacted-- on gathering feedback from teammates they work with day in and day out. Given that, I wanted to see if there were any observations/feedback (I took a look in ourgruuv already but wanted to ping for any additional things) you would like for us to discuss :slightlysmilingface:

        HELL YEAH!!!

        Way to be a proactive manager and go out and gather the feedback.

        Some might wait and see... others might try and have an in-person convo, but asking in a digital forum allows the person you are asking to take their time and give thoughtful feedback.

        Also, asking for observations shows that you want things that are actionable and not judgments that we are forced to unpack.

        I love, love, love this as an example of ways a manager can help their folks grow.

          Observation created over 6 years ago

        Wow... just wow.

        First, she tried something new, and added clarity as to how the new thing should flow:
        https://lessonly.slack.com/archives/C8UPX4UPM/p1564432055022900
        https://lessonly.slack.com/archives/C97TXG1PW/p1564432252002200

        Then, the retros happened... all three of them (I wasn't there, so I can't say how they actually went, but as an outside observer, I was impressed with what happened).

        Then, she didn't let the things that were discussed die on the vine... no, she took it upon herself to write up the note for all three, with clear actions, and clear ownership of who is going to take on which actions:

        https://lessonly.slack.com/archives/C97TXG1PW/p1564675008018100
        https://lessonly.slack.com/archives/C8UPX4UPM/p1564675014002100
        https://lessonly.slack.com/archives/C97TXG1PW/p1564670582013700

        I'm damn near in tears of pride and excitement (I cry a lot, so tears of joy, sadness, and pride are relatively common, but I will say they only come when something in the world hits me in my soul).

        Here's why...

        I've tried retros of all shapes and sizes. I've hated retros of all shapes and sizes. They are often well-intentioned, but it is really difficult to get a group of adults to open up and share in such a way that useful progress can be gleaned from it.

        When looking at the result of this, I think of our value of critique, not complain. Clearly, what happened in those retros is people opened up, put themselves out there, and critiqued and not complained! I see no way clear action items like this could be found without that happening.

        This shout out is aimed at Casey, but let's be clear, I'm thrilled with the vulnerability and teamwork that had to be shown by the entire Practice and Tech Services squads. Also, I Casey got the idea for this new format from Aaron (:highfive: man!!)

        Casey, it has been amazing to work with you from day one, and every day I am a bit more in awe. Thank you for being you!!

        Let's keep it rolling... ONWARD!!

        Our goal is, by continually refining the design of the org, to give the department as a whole the best chance of success

        Full Description

        Success:

        • You'll look at each squad and it's evolving mission, combined with the organizational goals, combined with budget and current personnel status and continually work on devising plans that give each squad the best chance of success.

        Details:

        • You'll ask yourself... do squads have what they need to be successful from a policy and personnel perspective?
        • You'll propose net-new roles and positions (such as software support engineer, when the needs of tech services became clear).
        • You'll re-establish the measure of success for positions, such as changing tech services into essentially three sub-squads, with the goal of making things smoother.
        Requirements
        • Must have a position with the reach of 3.2 or higher
        Examples
        An observation relating to  Squad organizational design architect  has not been publicly recognized yet.

        Bringing new folks into our tribe is one of the most important activities any of us will do. We ensure a good candidate experience, a great interviewer experience, and ultimately a talent/opportunity fit we are excited about.

        Full Description

        Success:

        • Facilitating the hiring process such that candidates have a pleasant experience (as measured by things like Glassdoor reviews).
        • Making decisions on who we will make offers to, such that the talent/opportunity fit is high.
          • Meaning the fit is great for them and the direction they are wanting to take their career, and Lessonly and the direction we are wanting to take the squad/discipline/department/company.

        Handbook:

        • You are responsible for getting the job posted
          • Drafting the job description and working with Talent to have it posted on lessonly.com/hiring and appropriate job boards
        • You are responsible for the interview structure
          • Identifying the interview team
          • Setting the interview structure
        • You are responsible for managing candidates in the workflow and communication
          • Making the decision on which candidates will progress to which states
          • One specific communication requirement is that within the Clubhouse card representing a position you are hiring for, you are required to post a weekly update similar to the following:
            1. Applications actively being reviewed: All-time: ## | In-Progress: ##
            2. Theresa Interview: All-time: ## | In-Progress: ##
            3. Woven Work Simulation: All-time: ## | In-Progress: ##
            4. Hiring Manager Interview: All-time: ## | In-Progress: ##
            5. Final Interview: All-time: ## | In-Progress: ##
            6. Offers Sent: All-time: ## | In-Progress: ##
        • Making the final hire recommendation (making the offer by working with the P&E Talent representative as well as the {budget/comp manager} if you are not taking on that role).

        Incomplete Lesson - Hiring Manager’s Handbook

        Requirements
        • Must have a position with the reach of 3.1 or higher
        • For this role, you must be milestone 3 or greater inMentorship
        • For this role, it is recommended to be milestone 1 or greater inCommunity
        Examples
          Observation created about 5 years ago

        I'll post the original message at the bottom (can't link because it was a DM).

        This is how it should be done!!! What is it? Setting up interviewers for success. A few specifics:

        1. Brea had to turn around a hiring gameplan in hours because of a non-usual situation with a specific candidate... and did so!
        2. Brea gave clear background and context to what is happening in the interview
        3. In an effort to ensure the interview is as smooth as possible, she assigned each person with a specific value, skill, behavior, or knowledge she wanted them to check for.
        4. Finally, she was aware enough to realize that since folks probably weren't used to our new ATS, that she should give a bit of guidance/training on that as well.

        Overall an excellent way to set up an interview for success. An excellent show of adaptability given the time frame this was all put together under.

        The time crunch isn't something we will get used, to but damn does it feel good to know we can rely on each other to step up when needed to kick it into a higher gear temporarily.

        Well done!

        Good morning and Happy Thursday! We have an engineering candidate, [redacted], joining us Friday. :tada: He’s interviewing for a Senior Software Engineer position (his focus will be on SRE and data needs to start and eventually help us grow a data team). [redacted] has interviewed with Lessonly previously about a year ago and was offered a position the timing didn’t work out. Here’s some more info about him:
        Jobvite Summary: [redacted link]
        Woven Results: [redacted link]
        LinkedIn: [redacted link]
        Here’s an overview of Friday’s schedule:
        09:30 AM to 10:00 AM, Conversation with: Brea
        10:00 AM to 10:45 AM, Technical/Culture Interview with: Tyler, Kristina, and Makenzie
        10:45 AM to 11:00 AM, Break
        11:00 AM – 11:45 AM, Culture Interview with: Kim, Ashley, and John
        11:45 AM to 12:00 PM, Break
        12:00 PM to 12:30 PM, Hiring Manager interview with: Brea, Andrew, and Theresa
        Let’s take the following parts of the scorecard as our focus areas for interview questions. Feel free to ask questions that don’t focus directly on these areas after you’ve covered these areas - also feel free to swap with someone if you want. Let me know if you have any questions!
        @kim

        • Business and technical translation
        • Prioritization @Ashley
        • They work to meet deadlines, and if they can’t, they proactively communicate progress and make a plan
        • We have difficult conversations @John
        • They have strong opinions weakly held (No brilliant jerks)
        • They are willing to give and receive both critical and appreciative feedback @tyler
        • Troubleshooting/debugging
        • Technical Investigation
        • Prioritization @Kristina
        • Collaborative
        • Mentorship
        • Comfortable with change
        • Empathy @Makenzie Bontrager
        • They recognize when to ask for help and when to utilize their resources effectively
        • Self-awareness
        • Initiative A few notes on Jobvite since it’s a newer tool not widely used: Please login ahead of time by selecting the first link in the calendar invite and make sure you can see the Evaluation Form. If you have issues logging in, let’s chat. All fields on the evaluation form are required to submit it, so please select NA for those you don’t have a strong opinion on. I’ll be putting a quick debrief meeting on the calendar here shortly, and please let me know if you can’t make it Friday so we can find a replacement. Thanks! Brea
          Observation created over 6 years ago

        Hiring is hard.

        It is time-consuming, it is nerve-wracking, and it is easy to get overwhelmed with the work of shepherding candidates through the process.

        However, it is the single most important thing we can do to continue our journey to be the greatest product team so that we can help fuel the greatest organization which is here to push forward one of the greatest missions of our time :-) (couldn't help myself :-) )

        When someone comes in and finds a way to improve any part of it, I'm thrilled.

        In this case, Rick posted an update from the week of what was done, and where his head is at.

        https://app.clubhouse.io/lessonly/story/29768/hire-product-quality-engineer#activity-30491

        That is HUGE... and here's why... clarity and transparency are better work.

        We love transparency here. So, posting an update like this directly impacts folks' ability to follow along and be a part of the process. Also, anyone who is interested never has to ask "where are we with that", because it is in the right place, it is concise, and it is clear.

        :spidey-dance:

        Great job man... keep it up!

          Observation created over 6 years ago

        We're currently hiring not one but two mid-senior engineers, for which there's a lot of competition these days. I saw on Twitter yesterday that an engineer I admire had just been laid off and could could be a fantastic addition to our team. I let Casey know (she's the hiring manager for this position) and she followed up that day via Greenhouse and even replied on Twitter, referencing one of the candidate's blog posts she enjoyed for a personal touch: https://twitter.com/case_eee/status/1135723324414341127

        Compared with other teams who responded to this person with a generic "We're hiring" message, Casey's prompt and thoughtful response made me feel proud of how she represented our team. And of course the goal here—bringing folks we can all learn from and growth alongside on to our team—has a direct impact to each of us. Thanks, Casey!

        We are the trusted facilitators of some of the most sensitive data we have within the organization... the budget and salaries. Our goal is fair, consistent, responsible, and equitable decisions regarding budget management.

        Full Description

        Success:

        • You are a trusted facilitator of some of the most sensitive data we have within the organization... the budget and salaries.
        • You help ensure we live our value of having an equitable compensation strategy. Including but not limited to:
          • Base compensation
          • Bonus compensation
          • Spot bonuses (such as Llama bucks)
          • Expenses (including lunches, books, etc)
          • Work-related incentive compensation aka stipends (such as incentives for working holidays or for volunteering for on-call)
        • You are trusted to converse with and explain compensation decisions to your direct reports, and when called for to a larger audience.
        • All employees for which you are responsible (strongly) agree to the following:
          • I am paid fairly within the industry for my position
          • The incentives and stipends inspire me and show that the organization cares

        Details:

        • Must have an understanding of the budget process.
        • Must have an understanding of the basics of the Lessonly business from a financial standpoint
        • Must have experience or a strong desire to research and synthesize market data as it pertains to compensation
        Requirements
        • Must have a position with the reach of 3.1 or higher
        Examples
          Observation created over 5 years ago

        asdf

  • Explore Options
    At this step you'll be able to choose different positions or roles that will take you down different paths along your journey. It'll give you an idea of what areas to focus on next and if you do focus on them, what it may take to get to where you are going