Welcome
Hello and welcome to Event Hub. Thanks for reading our employee introduction.
Event Hub is a modern fully cloud-based SAAS application. It has been in development for over 8 years, has been through multiple MVPs, and would be considered a "SCALE-UP".
We are an ERP that targets the Venue and Events Industry.
Think:
Shopify + Ticketmaster + Mailchimp + Event Brite.
We have had considerable success so far with many large companies using our application in Australia. As of July 23, we have begun to successfully move into overseas markets.
Formalities
Event Hub has many industry-leading innovations. For that reason, and our respect for security and data privacy, you must sign an NDA and provide a copy of your passport before working with us. We also prefer a mobile number and email address that will be validated.
Expectation
As stated above, as of Jan '23 we are a SCALE-UP. We are growing and adding new customers all the time. However, there are still many features to be built. We are on the road to success. Customers assess us based on the speed, stability, and innovation of our product. For these reasons, we do not hire Juniors....today.
Our assessment of the developer market and skill expectations are:
**The below are contract rates for short-medium-length commitments i.e. 2-3 months.
0-20$ USD - Junior: 1-3 yrs experience.
We do Not hire Juniors.
20-40$ USD Intermediate: 3-6 yrs experience. Some experience of our Stack
Onboard in 2 days.
contributing value to the code base within 2 weeks.
40-60$ USD Expert: 6 years experience. Highly experienced in our app.
onboard in 1 day,
contributing value to the code base in 1 week.
These times will be assessed against a small task that will be provided first. Examples include adding a filter, adding a search bar or adding some input forms. These will be expected to be delivered with 'SAAS context" (ie Multi tenanted data).
YES, you will come across issues that you cannot solve early on. We highly respect employees trying to work out the issues themselves - before they come to us. We all know there are many free resources available via a simple "google" search. Please utilise them.
Business process
Event Hub is a highly developed and sophisticated business application. It is essential that you understand and invest in understanding our (customers) business. For that reason, we have broken our app into 4 modules. You won't be expected to learn all modules - but you will be expected to significantly contribute to one module quickly.
Communication
Event Hub highly values "respectful and efficient communication". Some do's and don'ts:
We use SLACK over email. Scott rarely responds to emails from employees.
We use {targetted} comments in Jira. Slack should only be used for non-specific comms or personnel-related.
Do communicate through an escalation path. That means -> Team Lead -> CTO -> COO.
If you are South East Asian based, please only communicate during our standard hours 12-8 PM AEST. For other local Australians, please assume 6 pm AEST.
Do NOT ping us outside these hours. We have families and do not work 24/ 7. We are better employees and people if we DO NOT work 24/7. It is very easy for software people in a start-up to get burnt out - this is especially the case with remote teams across multiple time zones.
Never expect an immediate response unless you have booked time with us. Both the COO and CTO have bookable calendars for dedicated discussions. These are;
We do NOT use threads - we make communication open, accessible and transparent - unless, of course, it is truly "personal". Threads get lost and maintain information with single individuals.
If you do Ping us during work hours, do not expect an immediate response. Scott may be in a meeting to provide a demo to new customers, he may be asleep, or he may be having dinner with his family. (His Sydney times cross Vietnamese and Indian work time.) He will however meet all commitments through the calendar - or at least try to. Working across multiple time zones can be hard. VA may be working on a failed stack that he has to urgently rebuild. We have our own jobs and thus cannot immediately reply.
Processes should exist to enable continued workflow. If there is a gap, that is not your issue to solve, it's the management teams.
It's not about you - it's about our customer's and product vision.
We respect feedback both on our technical stack and employee processes. We guarantee to review all feedback provided. I cannot guarantee we will always agree :P
Payment Terms
We prefer to make payments directly into an Australian Bank Account. If not, then the employee would be responsible for any additional fees incurred to make the payment.
Regular monthly Invoices are to be issued at the beginning of the month for work carried out in the previous month.
Payment will then be made on the 15th of the next month or the closest business day.
(For example, for work carried out in January, the invoice should be issued on 1st February and payment will then be made on 15th February).
We can make specific agreements for team members who have been with us for more than one year.
Ad hoc invoices. For all other invoices, we process payments twice within the month. Payment processing dates are the 15th and 31st of the month.
Invoices must be received by 5pm AEST on the 13th of the month for payment to be included on the 15th and by 5pm AEST on the 29th of the month to be included in the 31st of the monthly payment run.
All invoices are to include the following:
Invoice number.
Amount.
Currency.
Bank account details (name, bank account number and/or any other relevant details required for payment).
Detailed description of work carried out for each day.
The dates of all work undertaken.
Your name, address, and email.
Due date - in line with our payment dates as above.
All invoices are to be emailed to ‘accounts@eventhub.com.au’ for action.
Accounts will make contact with you within 3 business days of receipt of the invoice if any further information is required.
What's Next?
You'll be provided technical onboarding instructions by your TEAM LEAD.
You'll be provided access to our stack code and our TRIAL-DEVELOPER-ONBOARD SLACK channel.
Once you have been onboarded you will be provided with a small task to prove your skills.
Good Luck!
APPENDIX
Behaviours we admire
Adherence to Process. That, and more sales :P solves everything
If you have a problem, you at least try to work out the issue yourself without immediately asking for help.
If you are blocked - don't just sit there - read other parts of the codebase - or try to learn the business process related to the module you are working in.
Respect our communication protocols
Respect for the need for "code" is derived from a successful business process.
Innovation.
You highlight code that might be susceptible to security or data breaches. We always treat suspected Security and privacy gaps with a high-priority
ATTENTION TO DETAIL.
ATTENTION TO DETAIL.
Behaviours we don't like
Lack of adherence to process.
LACK of ATTENTION TO DETAIL.
Ignoring our communication protocols.
Hand-balling work or issue without value - an example is forwarding an email or issue without "value review" - try to add value to every interaction.
Using someone else's work without transparency. It's fine to do - just be transparent.
Code is not the centre of the universe and by corollary - everyone is indispensable. Please do not assume you are. In a solid sustainable business, no one can be more important than the TEAM. That's why we LOVE AND RESPECT PROCESS.
You write code that only you can understand. You immediately fail the above rule.
*