> For the complete documentation index, see [llms.txt](https://docs.demos.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.demos.global/hiring-demos/applications-frontend-software-non-solidity.md).

# ⚙️Applications/Frontend/Software (non-solidity)

<mark style="color:yellow;">SKILLS:</mark>

1. architecture/strategies
2. Web development
3. Architect expertise
4. Continuous integration/deployment
5. Github / Actions / build / Deploy / CI
6. Cloudflare
7. AWS / EC2 / Load balancers /
8. Experience with smart contracts & solidity would be a welcome addition.

&#x20;

### <mark style="color:yellow;">Specific Skills:</mark>

#### a) overlapping:

• javascript

• https calls (restful apis etc…)

• testing + environments \[web3]

&#x20;

#### b) frontend:

• html (bones)

• css/scss/sass (design)

• react.js

• web3.js

• typescript

&#x20;

#### c) backend optional , nice to have:

* node.js (optional)
* &#x20;webhooks + apis
* &#x20;virtual machines + server + nginx
* &#x20;linux commands/jobs
* &#x20;AWS Lambda
* &#x20;AWS API Gateway
* &#x20;AWS S3
* AWS EC2
* MySQL
* API/Rest
* Infura

### <mark style="color:yellow;">General Requirements:</mark>

a) Cosmetic React updates: Change a text or some logic; no major changes. Simple React: mostly HTML/CSS, some testing, and Web3…

b) Continuously updating GitHub repo with standard files/components. Advanced react, understanding components, lifecycles, github, webhooks, web3

d) Track all work in Clickup to align with a scrum methodology.

e) Coordinating with teams across time zones with an understanding of deliverables and expectations.

&#x20;

#### 2) project based:

1. Understanding the requirements of the project. Planning and working to a schedule and critical path.
2. Creating, maintaining & deploying a react app
3. Fetching/handling data from various sources/requests (versatility required)
4. Being comfortable with web3 calls and how “it” works
5. Realising the importance of test envs and creating the environments accordingly
6. Insight in the deployment process. Understanding how the scripts are executed and why they are executed in this way…


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.demos.global/hiring-demos/applications-frontend-software-non-solidity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.