Operations Engineer

Owned by Eric Butz
May 12, 2022
6 min read

Job description and onboarding tasks for FIO Core development Operations Engineer

See: https://fioprotocol.atlassian.net/browse/BD-3478

 

Pay:

170k base

Incentive

One time grant of FIO token in the amount of 300k FIO will be given at 1 year. 1/2 of these tokens will be locked, they will be unlocked at 4% every 30 days.

compensation structure is flexible and negotiable.

The FIO protocol is looking for a principle level engineer who desires to learn and master aspects of fintech, the crypto space, FIO protocol, c++ smart contract development, c++ FIO Core development and more as a leader on the FIO Core technology team. This position will work closely with the VP of engineering, team mates, and FIO community members in the following areas and activities: architecture, process development, blockchain engineering, and research. The objective is to assist and help the core tech team in addressing these areas and activities as they relate to the operations and chain health initiatives of the FIO protocol.

 

Role:

This role will be a principle engineer who will help the core technology team by delivering, code, research findings, and documentation for the FIO protocol and its supporting processes and tools. This role will assist the core technology team by researching various aspects of the FIO protocols function, and performance. This role will aide the VP of technology to clarify the details of projects and initiatives the FIO protocol must address. This role will execute a variety of analysis, coding, documentation, and communications skills to flexibly help the core technology team achieve its objectives.

 

Responsibilities:

This position will be a key influencer for the efforts of the core tech team with respect to maintenance, chain health and other operations critical areas.

This resource will track and provide status for assigned core tech team projects and issues using tools provided by the core technology team.

This resource will perform research in support of chain performance in the following areas: FIO Transaction processing time, FIO CPU usage, FIO memory usage of state and more.

This resource will research and analyze upgrades of the FIO protocol to new versions of EOSIO technology.

This resource will personally deliver some of the critical projects facing the core tech team.

This resource will be committed to learn the processes, technologies and tools used by core technology team.

This resource will collaborate with the VP of technology and fellow team members to understand the initiatives, projects and work tasks that require their attention.

This resource will analyze the scope and structure for some of the more complex projects that the core team will complete to try to provide clearly scoped projects and epics.

This resource will deliver projects, findings and documentation on the core tech team using agreed processes and technologies.

This resource will research various performance aspects of the FIO protocol and its' operational environment.

This resource will troubleshoot operational bugs in the FIO protocol.

This resource will cooperate with team mates to evolve the core tech team processes and tools.

 

 

Tools you will use:

IOS or ubuntu computer system – for development of the fio chain.

Discord – for team communications and remote meetings

Jira – create manage and update issues, epics and stories.

Wiki – create manage and update project artifacts for assigned projects.

Telegram – monitor and participate on fio fio.mainnet fio.testnet fio.token and other channels relating to fio.

Clion,Visual studio, other IDE or editors – for modification of c++ smart contracts and FIO Core code.

Postman – http interactions with chain.

Github – manage development branches for all dev efforts.

zoom – for block producer and community based remote meetings

 

 

Day in the life of the operations and chain health principle engineer

 

 

Any Day 1 (project inception).

Meet with the team for an informal standup meeting. This happens several times a week.

you are working on a well defined epic that has just been assigned to you.

you setup the project Epic and project artifacts for the project.

begin doing some analysis work on the project

rough out design approaches for the project.

collaborate with product, or community members to discuss aspects of the project.

you notice a question on discord, you have an offline with another core team member on the topic at hand, helping and learning more about what was posted.

you make stories for the initial design and development phases of the project. you begin engaging on the project and making traction to deliver a finished design document within the next week or two.

you close out your day my updating assigned epics with present status.

catch up with a team mate and see what they are up to lately.

 

Any Day 2 (operational bug).

Meet with the VP of technology, he called on discord to bring a bug to your attention that one of our wallet partners is having.

discuss the priority of the issue, and brainstorm possible causes verbally.

you and the VP call up fellow team mates into the discord meeting as necessary to explore the issue and gain any necessary information.

you help to establish how best to communicate with the integrator to gain more information and provide feedback.

you create a story for this issue in Jira since the issue is blockchain focused and will require a hot fix.

you set up dev local environment with the necessary branches for placement of a hot fix.

you collaborate with QA or VP as needed to understand tests that might work for this bug.

you post on discord to the core tech team private channel some questions and thoughts you have on the bug.

OR make javascript tests to reproduce this bug.

you troubleshoot the bug document the root cause in your story, and commit your changes into GitHub, and make a PR for the Changes using GitHub.

you contact the VP of tech tostrategize the release testing for this fix.

you update your Epics and stories in Jira to close out the day so that status is accurate considering this interruption.

you collaborate with the team on discord to keep them in the loop.

 

 

Any Day 3. (research)

you have been thinking about chain performance,

you have some tinker time available since your latest big fix is in QA and being tested.

you want to better understand how the chain performs when there are lots of transactions of a certain type.

you do some independent tinker time on this topic and think of a way you can investigate this further. you want to go deeper into this.

you talk to the VP of technology and together you decide to make an epic for this since the information will be beneficial for the protocol and the community.

you make an epic and associated stories for this

you post on discord on tinker time channel what you are up to along with the links to the Jira epic and stories you made.

some discussion spins off on discord.

you begin to work this along with other assigned tasking on the team.

you end the day by updating your assigned epics and stories on jira.

you colloborate alittle extra via discord with the team and the vp of tech to keep everyone in the loop

 

Any Day 4 (project scoping and analysis)

a new strategic initiative has come into the team.

the VP of tech contacts you and asks you to take a look at it.

you spend time understanding the initiative, you collaborate with product and vp of technology and get a high level understanding of the initiative.

you open a Epic in Jira for this initiative.

you set up the the epic with one story, “investigate approaches for initiative and publish findings”

you begin investigating the design approaches for this initiative that might work for this project. all the while updating a document on the wiki that captures “initiative investigation findings” you begin to flush out the phases of the project and you publish a preliminary design document summarizing the design approaches that might be used.

you will look deeper into the initiative later and continue to clarify the project.

you close out the day updating your epics and projects on jira

you collaborate with the team about this project on discord and ask a few questions you have about the project.

the next day in standup you will talk briefly about this since you think it will help the team to gain increased awareness of this project.

 

 

 

theres lots of variety in the types of days you will have, alot of it is up to you!!!