KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#ai
#dsh-plugin
#deepseek-harness
#open-source
#cli
#claude-code
#codex
#developer-tools
#react
#windows
challenges
★ 86
Open GitHub ↗
Omise Code Challenges.
Download README (.md)
Explore Similar Repositories
skycloud-base
:
🔥springcloud脚手架,配置中心(apollo/nacos) 注册中心(consul/nacos) 分布式事物(seata) 调用链(skywalking) 日志(ELK)监控(prometheus与grafana) 等,适合学习与快速开发使用
angular-8-role-based-authorization-example
:
Angular 8 - Role Based Authorization Tutorial with Example
teanjs
:
:fire: TypeORM - Express - Angular 8 - NestJS Server Side Rendering (SSR) :smiley_cat:
face-engine
:
Arcsoft ArcFace for Go 虹软人脸检测SDK Go语言版
action-hero
:
Write powerful CLIs with argparse actions that pack a punch! 👊
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
challenges
?
Download (.md)
# Opn Payments Code Challenges This repository houses the code challenges for Opn Payments. These are small hands-on projects that are very relevant to the tasks you will be working on here. ### Ground Rules * We prefer well-thought-out solutions over the quick-and-dirty kind. So take your time, if you need it * Average completion time so far has been around one to two weeks * Submission is done via a [git format-patch](https://git-scm.com/docs/git-format-patch) Send your patch to the hiring team. ### What to expect We do understand that our code challenges are time intensive and not always easy to implement. We do recognize and value the time and effort applicants put into their submission. Our Code Challenges reflect some of the tasks and skills you'd need while working with us. We believe that these *take-home* challenges will give you a deeper understanding of our product, what you'd be working on in the future and what level of commitment we look for in applicants. ### What we look for Rather than a complex solution, which added a million features and is written in 10,000 lines of code, we look for: * **Clarity:** You can write clear code that any devs could read and understand in one go * **Simplicity:** You can write gimmick-free and straightforward code with no ambiguities * **Defensiveness:** You can cover edge cases and treat user inputs with care ### What happens after your submission Once you have submitted your solution by sending us the **git-format-patch**, our Engineers will review the code. Due to the number of submissions we receive, and time-intensive review process, it might take us **1 week** to give you feedback on the submission. Based on the feedback, we will invite you for a meeting to talk more about your submission and continue the recruitment process. ### Challenges Pick the one that most suites the position you wish to apply. **Omise** * Backend / Ruby on Rails - [tamboon-rails](https://github.com/omise/challenges/tree/challenge-rails) * Foundation / Ruby on Rails - [tamboon-rails](https://github.com/omise/challenges/tree/challenge-rails) * Backend / Go - [go-challenge](https://github.com/omise/challenges/tree/challenge-go) * Backend / Elixir - [elixir-challenge](https://github.com/boatkorachal/challenges/blob/challenge-elixir/README.md) * Devops / Kubernetes [challenge-devops](https://github.com/omise/challenges/tree/challenge-devops) * Frontend / React - [tamboon-react](https://github.com/omise/challenges/tree/challenge-react) * Mobile App / iOS and Android - [tamboon-mobile](https://github.com/omise/challenges/tree/challenge-mobile) * Design / UX - [design-challenge](https://github.com/omise/challenges/blob/challenge-design/design-challenge.pdf) ### Have fun and we look forward to your submission! <h2> ᕙ(⇀‸↼‶)ᕗ </h2>