Web Developer

Let’s Data simplifies the creation and management of data and compute pipelines using AWS services. It reduces the development time, costs and supports built-in high performance, availability and elastic scale. #Let's Data eliminates these infrastructure pains - our promise is that the enterprises should "Focus on the data, we'll manage the infrastructure".

Let’s Data has built a Minimum Viable Product (MVP) where we've perfected our infrastructure code for reading / writing to AWS Services and built all the reliability, fault tolerance and diagnostics needed for a high-quality compute pipeline. #Let’s Data MVP currently support AWS S3, DynamoDB, SQS, Kinesis and Lambda.

Work Description

We are looking to work with an experienced Web Developer who will own our Console, Email, Website, Documentation and other UI, API and Front-End side of things (console and website are used interchangeably – console being logged in experience whereas website is the static non logged in website).

There are few streams of work here:

1.     Standardize the Console code according to modern web development technologies, if needed (we are Html, jQuery, CSS, Bootstrap + some off the shelf implementations). This developer will determine whether what we have is modular, agile and feature rich to support quick development and iteration of new features and support of existing features.

2.     The UI and styling as it is today is what the founder sketched for the MVP, components we are using may not be the most optimal solutions to these issues. What we’ve built doesn’t render well on mobile and tablets. We’d like the developer to look at the UI and styling aspect of the website and standardize / professionalize these aspects.

3.     The product features that we’ve built are not all available in the console today (they are in the CLI though). This offers a degraded experience when using the console. We’d like these feature gaps in the console to be filled - for example, an initialization workflow is available on the CLI but is not displayed in the console. Similar examples are redrive error tasks and deletion workflows.

4.     Support the Console, Documentation, Email and UI for the new feature developments that we’d be doing. We intend to integrate with additional AWS services and each one of these integrations require changes in the each of these components. For example, integrate Kinesis as a read connector, the UI needs to add support to create, display and manage this connector. Documentation needs updates etc.

5.     We’d like to also add tests to the existing / new functionality using the website and console that can be run continuously on the production stack to alert us of any issues that might exist.

6.     We’ve deferred a bunch of Console UI items during the MVP development that should be standard in any UI. We’d like those implemented – things such as refresh buttons to refresh the data in the tables, permalink / state management for the home page, fixing the view logs / errors page with a log files text control, implement download logs / files and upload jar, adding ‘copy to clipboard’ to code and cli samples, ajax poll on transitionary statuses (if something is initializing, poll every 30 seconds till its initialized), client side validation and error display and corrections etc.

7.     Email: We have some email templates and also some code for sending emails and schedules – this works okay but recently I’ve found the need for automating the email story with customer actions (customer journeys) and I see a bunch of CRM and email companies that do that. So this is an effort to modernize the email side of things and make it easy and automatable to add emails at different customer interaction points – it might require an integration with some CRM / Email company and designing templates according to their systems etc.

8.     Documentation: We’ve organized the documentation to be updateable and reusable (templatizing components etc). However, not being a UI person, I believe there might be smarter, more efficient ways of doing these (or not). I’d like the developer we hire to take a look at our documentation story and see if there are any improvements we can make. 

9.     Future: We’d like the website experience to be extremely easy for the customers to try via the console. We envision customers being able to write java handlers on the website that we can compile and run inline rather than having to ask them to create their own projects, build jar files and upload them to get started with #Let’s Data. I did some initial investigation on this but someone who is an expert in UI development should look into how we can get this done.

The ideal candidate would have at least 3 years experience working as a web developer and should be well versed with the modern web development stack (Html, javascript, jquery, css and the modern web dev frameworks, react, bootstrap or similar).

This job is initially looking for a 5-month contract, however, if things go well (with our MVP testing), we’d want like this to be extended.

Company

#Let’s Data is a one-person, self-funded company where the founder is from an engineering background - we'd like to test the latest MVP in the market.

We are based out of Redmond, WA. This is remote work in Islamabad / Rawalpindi, Pakistan.