We are having difficulties with capacity. How do we address this?

Discussions - Public
42

Good idea. Lilac fixes will be the most valuable for the community. I’ll take a look at the board and come back here.

43

Great, it sounds like we are getting to a plan :slight_smile:

I’ll schedule a task to do the follow-up work on these projects on my side next week – I’ll probably be working on this on Saturday (May 22nd), so anything you’ll have ready by Friday will allow me to move forward on my part, or review it.

@raul Could you get the developers you have in mind to fill the candidates form at https://opencraft.com/jobs/open-source-developer/ ? This way I’ll be able to get a clear picture of them, and have their info. If you could also provide more details about when that could happen, how much time they can dedicate, if you have any specific conditions, etc – this way we can lay it out all here.

1 Like
44

Asking you @Fox as the reviewer of that epic, how should we go for the budget increase in this case?

45

So would we! :grinning:

@gabor @Fox When you’re ready, you can let me know how we could contribute.

46

I started writing up how we could do this and then decided it might be better to make a new epic after all, since as I dug in I remembered we source the existing epic’s budget through the onboarding budgets of individual members. Those budgets aren’t going to suddenly have room for this work, but maintaining the results of the new epic could fall under this existing one.

I had actually created a ticket already to update the handbook and it was scheduled into this coming sprint. So what I’ll do is turn that ticket into a discovery ticket for this new epic instead. I’ll mark you as reviewer, @gabor, if that’s alright.

Edit: Discovery ticket available here: Log in - OpenCraft

47

Awesome! I can’t wait to review it :blush:

48

@Fox @gabor A couple notes about this:

  • Regarding capacity planning, please let me know how many hours would be needed for the new epic in June (and beyond). Even if Serenity ends up owning the epic, we might need to farm out some tasks to other cells, at least in the short term, to make sure we can finish the work quickly :slight_smile:
  • Regarding sustainability (CC @daniel), if we can’t take the hours for the new epic from onboarding budgets of newcomers, could we still associate the new epic and its tasks with the (non-cell) OpenCraft - Recruitment (OC-RECRUIT) account? That would be great because if we had to associate the new epic with a cell-responsibility account, sustainability might become a blocker (at least for Serenity and Bebop).
2 Likes
49

We have used the Opencraft - Recruitment account in other documentation improvements coming from newcomers (e.g. SE-2340, SE-2116, …) so I think it’s acceptable. Though I don’t have the authority to decide it, because it’s a non-cell account and we just handle the cell accounts. In any case, „recruitment“ makes perfect sense since it’s about improving recruitment.

What we usually do in those tickets is: we acknowledge that documentation improvements are unending, so we set a timebox to avoid consuming too much time.

2 Likes
50

@daniel @tikr We can use a non-cell budget for this, but it would be better to create a new dedicated one and keep the “recruitment” budget for work more directly linked to a specific recruitment, otherwise it will end up being hard to tell what goes in there. @gabriel Could you create one?

2 Likes
51

Sure, just let me know what the name should be, and I’ll create an account.

2 Likes
52

Job description

I have done another iteration over the job description, based on additional thoughts I had in the meantime, as well as feedback gathered from candidates & additional people I’ve asked advice to over the past week. See my edits in the document history - I have:

  • Tried to highlight more of what makes OpenCraft unique, for example put additional focus on open source and being good at handling remote work, about compensation, freedom, and about work-life balance
  • I have also emphasized the requirement of a contribution to a third party project as this is one of our main filters for candidatures – to encourage people without a contribution to do one before applying (since we would be filtering them out otherwise, it could increase the number of candidatures we would consider), and linking to the bounties to allow candidates to get paid for that contribution work if they can deliver it on Open edX

Since the changes are significant, I’ll wait until Monday to do the changes on all the ads, to give a chance for reviews – particularly from you @Fox since you have led that effort.

Recruitment process changes

I have also made corresponding changes on the recruitment form, and further modifications to test a change of process: adding a second interview after the technical interview, with me, for candidates who pass the first interview, and group all the contract discussions at that time (review of contract, setting the rate, answering questions about invoicing, etc.). We’ll need to see if that’s worth it, as that means that we would filter people who are out of price range later, but since that’s the step where we are losing more people than we used to currently (ie we have more applicants, but a larger proportion of them end up going for another offer), that would allow me to discuss more directly with candidates during that phase, answer their questions and address their hesitations when they have some, and also generally spend more time with them, to show that we value them.

Another benefit is that the candidatures are now immediately accessible to recruitment managers without any need for further automation, since there wouldn’t be any rate information to filter out in the initial form. CC @usman @adolfo @paulo – I’ll need to do a pass to update the recruitment process accordingly, as we are discussing with @paulo on Log in - OpenCraft

Bounties

I have also looked into bounties. @adolfo I don’t think you have provided the list of potential bugs yet, right? I looked at https://github.com/openedx/build-test-release-wg/projects/1 and spotted two potential tickets, for which I’ve created corresponding bounties on Bountysource:

I wasn’t able to credit the bounties though, as Paypal is throwing a tantrum and doesn’t let me pay – I’ll need to look into it more closely. That gives you time to confirm the tickets @adolfo , and provide an hours estimation. Also, I’m wondering if it wouldn’t be better (or at least complementary) to post the bounties on our site, and offer them to the candidates who want to apply but don’t have a merged contribution to an open source project – that’s actually a large portion of people applying, that we currently reject. We would also have more control on the assignation and awarding of the bounties, and not have to pay for them upfront without knowing if the work will actually be done.

Recruiters

I’ve reached out to a recruiter I had met a few years ago and who was a really nice and serious person – I don’t know what to expect from his work, but that could be a way to test this approach. I have a meeting scheduled with him on Monday.

Temporary contractors

@raul I’m replying to you here to keep things fully transparent here. Thanks for submitting the recruitment form for the two contractors. Looking at their profile I notice that they don’t have any contribution to a third party project listed – are there some that you could link to? I had assumed that since they do contract work for scrappinghub they would have many, but maybe I was wrong? Having existing contributions is a hard requirement for any developer joining the team, even for contractors. (Also could you respond to @Fox’ questions & remarks above, to also have this discussion here?)

Website & handbook update

Maybe something like “OpenCraft Website - Recruitment improvements”?

4 Likes
53

@antoviaque oh right sorry, yeah actually most of the scraping contributions are private because they deal with client’s data. But they do have opensource contributions, here are some from Chris and Alfred. Also looking at the bounty related tasks, I think they could take care of those before starting any work here if that’s ok with you.

I think they would be very similar to newcomers in that sense, with less onboarding time and limited access

Yeah I think a buy-out option is totally possible :+1:

1 Like
54

@raul OK - since their contributions wouldn’t qualify in our current recruitment, let’s do this:

  • Let’s start by having them work on the bounties tasks I mentioned above, after confirming with @adolfo that they are good tasks for this, and getting a timebox from him on this – if they get the work done & merged, we would then cover their time spent on this at their standard rate, up to the timebox set by @adolfo – good?
  • In the meantime, @paulo @adolfo @usman could you allocate them between your cells, based on the urgency of your respective availability requirements? I’m going to add them to the candidatures spreadsheet (they are the two with the description “Bitmaker” and no assignation), so you can then proceed to interview them normally, and we can take a decision there
  • If the decision is positive, I’ll send you a contract for each of them @raul

That’s great - what would be the terms for this? I agree with @Fox that it’s best to discuss this upfront, to make sure we don’t end up with ambiguity causing issues later on.

2 Likes
55

A post was merged into an existing topic: Recruitment boards

56

I have no experience in headhunting, and I agree most of it is simply spamming developers on LinkedIn. I’d be willing to try it if we had a few guiding rules.

(Sorry for the delay, never got the email notification)

:+1: :+1:

1 Like
57

Sounds good to me!

1 Like
58

Sure, I created the OC Website - Recruitment Improvements account :+1: cc. @daniel @tikr

2 Likes
59

:wave: Hi, long time no see! (For any newcomers, I was an OpenCraft core member for about a year in 2018 - 2019.)

I have a few thoughts about the recruiting process – take them as you like. :slight_smile: (Apologize if this is a bit messy, typing fast.)

  • Embrace the rejection process. Most candidates won’t do well at OpenCraft, so be more upfront about that and market yourself to people who are looking for an experience, not a job.

    • College students who want something impressive to put on their CVs
      • Student job fairs or college internship boards?
    • People transitioning back into the workforce after injury/illness/childbirth.
    • People who are not the primary breadwinners in their household

    Some of those people will stick around and many won’t, but as (I think) Tim pointed out, any job offer a candidate gets aside from OC will not still be there when the trial period is over. So people have to be okay with the idea of another job search a few months after joining. People who need a jumpstart to their career or just want to do something fun during their summer break will leave OC with fond memories (hopefully) but people who are already exhausted from job hunting and were expecting a full-time position will resent being let go (and complain about it on job boards, etc, thereby driving off other developers considering OC).

  • More information about rate, before people apply. (A link on the job ad to documentation would help.) The “floor” which I saw mentioned in another post is great, but even above that, not every candidate knows how to price themselves. In a perfect world, that would be the candidate’s own affair, but we don’t live in a perfect world and helping people out with figuring a number is an important part of keeping people.

    • (U.S. perspective) Many contractors assume they will be able to bill in 8 hour increments. Be very upfront: "You can only bill the hours worked. That means, for an eight hour work day, you can expect to get paid 4 - 7 hours (depending on how much work is available and how many breaks you take).
    • (U.S. perspective) Tax consequences and healthcare. :sob: If a candidate has only worked W2 positions (regular employee or “contractor” for a temp agency), the doubled tax bill and $4k - $8K per year for health insurance will come as a nasty surprise.
    • . . . workers in every country have unique considerations? Fees? Limitations in getting unemployment? Mandatory insurances? OpenCraft could share that wealth of gathered experience openly.
    • A checkbox on the application like “Contact me anyway” could take a lot of the stress out of things. Women and minorities frequently under price themselves and that’s not fair. Giving applicants who want too much but are otherwise very interesting a chance to submit a second bid could open the door to more great people, while encouraging applicants to put what they really want and think is fair.

  • Don’t lower standards. I know, it’s very tempting when recruiting is at a low ebb, but working at OpenCraft doesn’t offer many traditional workplace benefits (an office, a 9-to-5, a dental plan, departments, a boss handing out assignments, etc) so bringing in the people who are looking for that is just going to be an enormous waste of time and money and will breed resentment which hurts brand reputation. There’s a big difference between someone who is green-but-eager-to-learn (a good fit for OC) and someone who is stuck in the mindset of “I’m a Python developer, I don’t do [project planning/client communication/infrastructure/blah]” Those people will kill the culture here (and probably the company, too).

tl;dr: market to the people who want a short term position and coach them about pay rate before they join

9 Likes
60

:wave: Nice to see you stopping by @seamus_external !! And thanks for this - it’s a very helpful perspective!

I guess that the implicit point you’re making is that the idea of the trial period and potentially having to look for another job soon are a big barrier and turning lots of people away who would otherwise apply.

I had kind of assumed that wasn’t a big factor, because in the world in general demand for experienced developers has always exceeded supply. (Even now, as Xavier mentioned, we get lots of people going through our process and then taking other competing job offers at the last minute. And when we post job ads for developer roles vs. non-technical roles, we see consistently that the non-technical people put in far far more effort on their cover letter, resume, application, etc.) But if that is a big barrier that’s filtering out a lot of candidates, it would be helpful to know that.

+1 to your other points.

61

Hi @antoviaque and everyone, I hope you are having a lovely day wherever you are in the world. :slightly_smiling_face:

I first want to introduce myself. I’m Essio Colom, the COO of Bitmaker. I’m also from Peru and living in Barcelona at the moment.

Secondly I want to congratulate everyone here for the awesome job you’re doing in Opencraft. I think I have an idea as I’ve talked a lot about the company with @raul over the past.

Now I’d like to get into the topic that brings me to this forum. I’m very happy about the idea that Raul shared with you to help you out with the issue you are currently facing to confirm a new core member in the last several months, specially with OpenCraft’s growth and the urgency you have to get new talent onboard.

Still, I’d like to make it clear that this is not our usual way of work with any companies and the reason we are happily willing to do it is because Raul has a special place in his heart for OpenCraft and he truly wants to give a hand to a company he’s proud to be a part of,

I would like to give some pointers to take into account so we can actually have some common ground in which OpenCraft and Bitmaker will be happy with:

  • For any developer we would provide to OpenCraft (Alfred and Chris to start) we would need a 3 months Work Order to assure our devs are only focused on OpenCraft
  • If you would like to keep any of these developers working with you for a longer period of time we’d need a 1 month notice before the end of the 3-month Work Order. If this is not done we will immediately assume that the developer is free for other projects after the Work Order has been completed
  • Before a buy-out is possible we would need at least 4 Work Orders for the same developer (1 accumulated year of work with OpenCraft through our company)

We feel that Alfred and Chris will get a great understanding of OpenCraft during these first months working on your projects and then, with all the expertise gained, they could be critical on the onboarding of new talented developers on open source and edx experience in case you need more hands in the future.

From our side, we have some future projects coming and I was counting on Alfred and Chris, but right now and for some time there is no issue at all to help you guys out so there’s no need to worry about this. Time will show how things go.

Contributions Status

That’s all I wanted to share with you guys and I think that for the best interest of everyone all communication regarding this partnership should be done with me from now on.

Looking forward to your thoughts and wishing you all the best.

Cheers!

5 Likes