...
The Drupal Developer I at Axelerant could progress to a Drupal Developer II role within two years.
Expectations
Support designing and building Drupal applications with trivial content structure and functionality
Support technical discussions with both technical and non-technical audiences
Responsible for Drupal development tasks including custom module using agile, collaborative, and continuous integration methodologies
Responsible for solving problems effectively by collaborating with peers
Responsible for identifying, analyzing, and solving problems systematically rather than solely by gut
Support being coached and mentored
Responsible for documenting incidents and issues for communication and reference purposes
Requirements
Demonstrated Drupal experience
Experience using Git source code versioning and Pull Requests
Experience with Drupal development technologies such as Drush, Configuration Management, and Composer
Nice to Have
Actively contributing to Drupal or other open-source projects
Coachable leadership and presentation skills
Experience with agile methodologies for teams
Experience with other content management systems and open-source technologies
Knowledge of Drupal-adjunct techniques such as the LAMP platform, HTML5, CSS3, SASS, and JavaScript
...
Questionnaire
S000 KO
Do you have experience with Drupal’s Drush, Configuration Management, or Composer?
S190 Interest & Competency Check
As per https://www.axelerant.com/about , which is the second of our three values?
Within this test’s email, we had sent you a ‘Principles and Values’ document. From that attachment, which of the following options is a sub-trait of our value, Kindness?What are your thoughts about working at Axelerant?
Tell us about the last article, podcast, talk, or video that intrigued you.
Why did you get into engineering?
How have you overcome team collaboration challenges?
Given a development requirement, how do you typically plan, build, test, and deploy it?
Create a custom Drupal 8 module. # Background Information: When logged in as the administrator, the "Site Information" form can be found at the path /admin/config/system/site-information. #
Requirements: This module needs to alter the existing Drupal "Site Information" form. Specifics: * A new form text field named "Site API Key" needs to be added to the "Site Information" form with the default value of “No API Key yet”. * When this form is submitted, the value that the user entered for this field should be saved as the system variable named "siteapikey".
* A Drupal message should inform the user that the Site API Key has been saved with that value. * When this form is visited after the "Site API Key" is saved, the field should be populated with the correct value. * The text of the "Save configuration" button should change to "Update Configuration". * This module also provides a URL that responds with a JSON representation of a given node with the content type "page" only if the previously submitted API Key and a node id (nid) of an appropriate node are present, otherwise it will respond with "access denied". # Example URL: http://localhost/page_json/FOOBAR12345/17 # Test Evaluation: * Meeting above requirements * Utilising Drupal-specific solutions (hooks, APIs, etc.)) * Readability of code * Clear, concise commenting * List of resources used if any (Internet sites, books, previous knowledge) Total time to complete task # Test Submission: * Set up your http://github.com account if you don't already have one. * Push the module as a public repo in GitHub and submit the link to it below. *
...