You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a recruiter of Data Science and Data Engineering roles
I want user accounts on the Analytical Platform that can be used by non-MoJ users in recruitment
So that they can be used for the purposes of technical assessments
Value / Purpose
Provides a fairer and more stable environment for recruitment
Enables higher-quality recruitment exercises to be set
Resolves some information security concerns
Guest accounts would effectively resolve all the concerns in 'context' above, and would also provide an environment that accurately represents the working environment of a data professional in the MoJ, so candidates would be better informed regarding the nature of role they have applied for.
Useful Contacts
No response
User Types
MoJ job applicants, Recruitment managers
Hypothesis
If we... [do a thing]
Then... [this will happen]
Proposal
No response
Additional Information
Requirements from Feature request:
The requirements would include:
The ability to run VSCode, Jupyter Lab, and R-Studio as does any typical AP user.
For admins to be readily and frequently able to clear the NAS storage for these accounts (so a fresh image is available to each candidate without any persistence of files between interviews). During interview periods this would be daily if not several times per day, depending on how many 'guest' accounts existed for use.
Having read access to only specific named repositories in the MoJ Github organisations (ie. unable to see organisation-level repos, and only be able to see repos specifically created for recruitment exercises - or public repos).
[Maybe] for recruitment managers to have access to these accounts, or otherwise have a means to create these images when designing the technical assessment exercises. In the interests of being user-friendly, it might just be that assessors could log-in and pre-clone a repo for the candidate, but really the candidate could be talked through this process at the start of an assessment too, so this is not an essential requirement.
IAM access to S3 appears to already be adequate for these accounts (ie. there is no access by default), but it would be worth confirming information security at some stage.
Definition of Done
Investigate options available and set out proposals for delivery to be agreed by team
The text was updated successfully, but these errors were encountered:
User Story
As a recruiter of Data Science and Data Engineering roles
I want user accounts on the Analytical Platform that can be used by non-MoJ users in recruitment
So that they can be used for the purposes of technical assessments
Value / Purpose
Guest accounts would effectively resolve all the concerns in 'context' above, and would also provide an environment that accurately represents the working environment of a data professional in the MoJ, so candidates would be better informed regarding the nature of role they have applied for.
Useful Contacts
No response
User Types
MoJ job applicants, Recruitment managers
Hypothesis
If we... [do a thing]
Then... [this will happen]
Proposal
No response
Additional Information
Requirements from Feature request:
Definition of Done
The text was updated successfully, but these errors were encountered: