We're looking to add a front-end engineer to build brand new products at AcademicWorks and help shepherd our current products as they mature.
This engineer will work closely with our lead user experience engineer (👋 from behind the 4th wall) to continue improving our experience for users, solidifying our codebase, and laying the foundation for new features and products.
Our front-end tooling mainly consists of:
- Ruby on Rails with standard ERB templating
- Sass for CSS and a loose adherence to BEM methodology
- Non-CoffeeScript ES5 with a decent dose of jQuery and friends
- Jasmine for testing our front-end
Our new front-end engineer, in addition to feature development and refactoring, will be helping us think through some of these things:
- Would using an ES6 transpiler like sprockets-es6 be worth it to us?
- Now that browser support allows it, what does a reasonable path to using more flexbox look like?
- Would it be prudent to make a couple of our more interactive pages function as single-page applications?
- What steps should we take now to be open to implementing Content Security Policy in the future?
- How can we improve our experience for mobile users?
The right candidate doesn't need experience in all of these tools and technologies to have success at AcademicWorks, but they should be comfortable with the modern front-end and eager to grow professionally.
You're kind, talented, ambitious, and responsible. We're looking for someone who:
- Stays aware of news and developments in the front-end world
- Looks to responsibly implement forward-thinking solutions
- Believes in the value of accessibility
- Has opinions around design and user experience
- Is always ready to discuss what's best for users
- Takes initiative and ownership to move the product forward
You might live in Austin, or you might live elsewhere. For the right candidate, we're open to discussing relocation assistance, but the position will be on-site here in Austin.
Send an email to careers@academicworks.com with a bit more about yourself, what attracts you to Academicworks, and any additional information you think would be relevant (a resumé, your GitHub profile, talks you've given, side projects, etc…). We'll be back in touch within a few days, and if things look bright, we'll start the interview process.
We're a 30-person, product-focused SaaS company helping schools and students manage the scholarship process. After 3 years on the market, we have helped hundreds of thousands of students find the aid they need while helping schools expand their reach to find the best and brightest applicants.
We earnestly believe we're making the world a better place by providing students the opportunity to attend college, and we have both the numbers and the anecdotes to stand behind.
We take pride in a culture that helps employees thrive at work and in their personal lives. Our offices overlook Pease Park on Lamar Boulevard, and we provide bike storage, showers, and healthy (OK, and some less healthy) snacks on-site. Work-life balance is a priority, and we all work to be flexible with our schedules to accommodate our coworkers' needs.
We're an 8-person group who work closely together and take significant pride in achieving disproportionately large goals. We have plenty of industry experience, but we're more concerned with intangibles than years-in-your-chair.
We respect one another and act accordingly—we move at a sustainable pace, take the time to refactor as we go, take initiative on solving problems, and jump in quickly to help one another. Regular one-on-ones ensure everyone's voices on the team are heard, needs are met, and careers are growing as they desire.
That doesn't stop with the engineering team, however. AcademicWorks has built a culture of excellence and respect, and our engineers regularly interact with all disciplines within the company both personally and professionally.
Outside of job requirements, we all count development among our hobbies, and we're happy to share what we've learned through reading and side projects. We attend conferences, speak at meet-ups when we can, and look for any opportunities to contribute back via open source.
And while we forgo game consoles and late nights at the office with catered dinners, we do our best to cut out early every now and then to catch up personally and play a board game, catch a movie, share a meal, or have a drink.
Interviewing can be stressful. We want to do our best to get to know one another thoroughly while being reasonable and accommodating. Not only does this help us become familiar with you, but it affords you the opportunity to determine if AcademicWorks is the right fit for you. That said, this is what we anticipate the interview process to look like:
- A 30-60 minute introductory phone call or coffee with an engineer you'll be working closely with
- A 30-60 minute follow-up call with our VP of Engineering to hear more about our team and direction
- A 2-4 hour exercise, completed at your own pace and submitted via GitHub. We'll take some time after this to discuss your code and what we can learn from one another.
- An on-site interview to meet the rest of our engineering team and at least one of our co-founders
- You'll hear back from us with a hiring decision!
AcademicWorks is an equal opportunity employer and drug-free workplace.
Hey Joshua,
I'm looking for positions in Austin close enough to South Austin driving distance. I googled you but it says the office is closed see link
Can you update the location on maps or add it to the posting?
thanks
EDIT: I updated it for you :)