J. Ayo Akinyele
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

Your note will be visible on your profile and discoverable by anyone.
Your note is now live.
This note is visible on your profile and discoverable online.
Everyone on the web can find and read all notes of this public team.
See published notes
Unpublish note
Please check the box to agree to the Community Guidelines.
View profile
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
1
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
Junior Rust Engineer (Remote, USA only) === **At [Bolt Labs](https://boltlabs.tech), our mission is to empower everyone with the tools they need to realize financial privacy**. To achieve this, we're building zkChannels: a scalable and usable privacy-preserving payment infrastructure that integrates with existing payment networks, including but not limited to public blockchains. We believe zkChannels will set a new standard for secure payments in online services, giving merchants a seamless way to comply with emerging privacy regulations and moreover, delight their customers with cryptographically rigorous respect for their privacy. [You can learn more about our work on zkChannels here.](https://github.com/boltlabs-inc/libzkchannels) Why work at [Bolt Labs](https://boltlabs.tech)? --- * **Values**: We care about building technology that makes a positive difference for the privacy of people everywhere. Our goal is to create an inclusive and supportive work environment, where we all have the resources to learn, grow, and work collaboratively to improve the state of privacy today. * **Mentorship**: We believe in investing in your growth as an engineer. Especially as you begin, you will be collaborating closely with several members of our small team, and we'll work together to help you gain the domain knowledge you need to grow into increasing independence in the role. * **Open source**: You'll have an opportunity to contribute significantly to the open-source Rust ecosystem, from which we both substantially benefit and to which we give back. * **Flexibility**: We are a small, fully remote, focused team, offering maximum flexibility and minimum bureaucracy. If you're able to attend meetings, collaborate effectively, and do your work, when and where you work are up to you. Want to take a walk in the middle of the day? Want to turn your phone off after work and not respond to messages until after breakfast? We encourage you to value your life’s balance. * **Benefits**: We offer a competitive full-time salary (USD $80k–$110k range) and benefits that include fully subsidized health, dental, and vision insurance for you (50% subsidized for your partner and family), equity in the company, a funded bring-your-own-device (BYOD) policy, and 4 weeks of paid vacation time per year, not including sick days and holidays. * **Research**: You will be working to solve meaningful, never-before-solved challenges with a world-class team of scientists and engineers in the fields of applied cryptography, distributed systems, programming languages, and more... and we're excited to learn from the unique insights that you will bring. You might be a great fit for the role of Junior Rust Engineer if… --- ### You have solid Rust experience You will be working in Rust from day one. You don't need to come in as a Rust wizard (though you might become one while you're working here!), but you should have a solid Rust background so you can begin meaningfully contributing to a medium-sized project within the first month or two of joining us. ### You’re confident balancing independent and collaborative learning Implementing a production-ready cryptographic protocol is difficult interdisciplinary work. We’re seeking someone who’s not afraid to ask a lot of questions: you should know how to notice when you're confused and say so when you are. At the same time, you should have the drive and the organizational skills to take charge of your own learning. We'll work together to help you strike a healthy balance between collaboration and independence. ### You have strong skills for asynchronous communication and remote work Work at Bolt Labs has always been asynchronous and fully remote, and will continue to be so after the COVID-19 pandemic's travel restrictions are over. We're looking for an empathetic person who doesn't mind collaborating asynchronously, with the excellent verbal and written communication skills necessary to thrive in that environment. After it is safe to travel, we plan to bring the team together in person approximately once per quarter (but we won’t be doing that until it *really* is safe). ### You have any of many different professional or academic backgrounds Please consider applying even if you don’t have: * a college degree in computer science or engineering, * `X` years of professional experience in Rust, or `Y` years of work experience as a programmer, or * experience with cryptography, cryptocurrencies, distributed systems, privacy-preserving computation, anonymity-preserving network protocols, or any of the other specific domain details of our work: none of us came in knowing everything, either. ### You have current work authorization in the United States Although this is a fully remote position, we are only able to extend an offer to applicants who are living and working in the USA. **No exceptions.** How to apply and what to expect --- 1. **Apply by emailing careers@boltlabs.io**: * your **name** and **pronouns**, * your **resume** or **CV** (no page limit), * a **brief cover letter** describing your interest in the role, and * a **sample or description of your technical work**. Your work sample can be one or more public links to code you’ve written, or if your best work has happened behind closed doors, it can be a description of the work you did in enough detail for us to understand it. If the best example of your skill as an engineer is in a language other than Rust, please show it to us or tell us about it—but in this case, please also include at least one sample or description of something you’ve done in Rust as well. 2. **Initial interview**: We’ll chat with you about your background, prior experience with Rust, motivation for working at Bolt Labs, and other introductory things. We’ll also ask you to tell us more about the work sample(s) or description(s) you submitted with your application. There won’t be any surprise pop-quizzes during this interview; this is about getting to know you on your terms. 3. **Short take-home preparation for technical interview**: If we want to move forward to a more focused technical interview, we’ll specify in advance an open-source Rust crate and ask you to familiarize yourself with it before your second interview so we can discuss it together. You can do this by reading through its documentation, source code, or other materials, and/or by playing around with it by writing some code. We don’t expect you to spend more than a few hours preparing, just enough to have a meaningful conversation and show us your insights. 4. **Zero-whiteboard technical interview**: In this technical interview, we’ll have an open-ended discussion about how the crate is designed, why you think it works the way it does, and how it might be improved. We’ll also ask more detailed questions about your knowledge of Rust and of software development in general, with the intent of filling in our understanding of your technical background. We don’t expect you to know the answer to every question we might ask—an impressive technical interview might just as much mean that you asked insightful questions as that you had insightful answers. 5. **Final team interview**: After the technical interview, we'll let you know whether we're interested in moving forward to a final interview where you'll get an opportunity to talk to the entire team at Bolt. You'll be able to ask any questions you still have about our culture, our future plans, our upcoming technical challenges, and whatever else comes to your mind. 6. **Offer**: After the final interview, we'll let you know whether we're interested in extending an offer. If we extend an offer, our team members will continue to be available for you to ask anyone any questions that might have come up for you since the last interview. All of our interviews will be conducted over video chat. We want you to be comfortably able to show yourself off in the best possible light. If there are any accommodations we can make during the interview process to make things easier for you, please let us know. At any point, please feel free to email any questions to careers@boltlabs.io. We look forward to meeting you! --- Bolt Labs is an equal opportunity employer and we value diversity at our company. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status.

Import from clipboard

Paste your markdown or webpage here...

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template has been removed or transferred.
Upgrade
All
  • All
  • Team
No template.

Create a template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

Slide Example

API Docs

Edit in VSCode

Install browser extension

Contacts

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Get Full History Access

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

Note content is identical to the latest version.
Compare
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully